Topic: Bugs
kaputtnik Topic Opener |
Posted at: 2016-06-20, 17:25
Open bugsSolved
Edited: 2016-06-24, 23:18
Top Quote |
einstein13 |
Posted at: 2016-06-21, 01:18
BUG: the strings here are changed while saving to database/ loading from it. When you want to write a special character (f.e.: greater than sign) you have strange results (pure html text) TEST: EDIT: Yesterday I could see polish letters. Today they are question marks. Is this a system-browser problem? (Windows - Linux) ? ? ? ? ? ? ? ? ? ? ó Ó ? ? ? ? ? ? Also let's try star1 star2 star3 under1 under2 under3 Edited: 2016-06-21, 14:26
Hey, this is my wrong signature :P Top Quote |
kaputtnik Topic Opener |
Posted at: 2016-06-21, 09:32
Ah, special characters.... lets try german: Ä ä Ü ü Ö ö ß Top Quote |
einstein13 |
Posted at: 2016-06-21, 14:27
I guess that there is a problem with database encoding, but I am not sure! Hey, this is my wrong signature :P Top Quote |
kaputtnik Topic Opener |
Posted at: 2016-06-21, 20:23
Indeed, thanks for the hint on that. The current set is for the database and for the related pybb table: latin1 | latin1_swedish_ci I have changed that so special characters should be saved correctly now: polish charset: ą Ą ć Ć ę Ę ł Ł ń Ń ó Ó ś Ś ż Ż ź Ź But this wouldn't solve the problem with the "greater/lesser than" sign (>) and the ampersand (&) Top Quote |
einstein13 |
Posted at: 2016-06-22, 01:09
Messages in other parts are shown well (see my comment under poll) Is this a valid code?: http://bazaar.launchpad.net/~widelands-dev/widelands-website/django1_8/files My first guess:
But the line here is OK. Second guess was database (before saving the message, signs are changed), but when I quoted your message, in textarea correct signs appeared. Another strange thing is that only 3 of 5 signs are changed (django can change also other signs). Why? Don't know! EDIT: another quess about "preview" button (when editing & creating posts): http://bazaar.launchpad.net/~widelands-dev/widelands-website/django1_8/view/head:/pybb/views.py#L354 (LINE 354) Edited: 2016-06-22, 01:29
Hey, this is my wrong signature :P Top Quote |
kaputtnik Topic Opener |
Posted at: 2016-06-22, 08:36
Displaying the posts use already the filter "|safe", so thats not the problem. The problem is that I look into it this evening again. Thanks for your replys, they are helping a lot Edited: 2016-06-22, 08:42
Top Quote |
kaputtnik Topic Opener |
Posted at: 2016-06-22, 08:49
Edit: Edit2 for testing Edited: 2016-06-22, 18:21
Top Quote |
einstein13 |
Posted at: 2016-06-22, 19:27
Another bug (probably it is both here and on official page) is about making Wiki links. If you write GunChleoc nickname in maps comment, you will raise this bug. See my comments under first uploaded map. Hey, this is my wrong signature :P Top Quote |
kaputtnik Topic Opener |
Posted at: 2016-06-22, 20:29
This is not a bug it's a feature No, not really Once the wiki was programmed the decision was made to create "easy" wikilinks: Wikiarticles should be named with at least two upper case letters in one word. Such words (like "WikiHelp" or "GameHelp" or, in this case, "GunChleoc") could be easily matched with a regular expression and if some writes it (only the word) in a Wiki article the Word get transformed to a wikipage url. For the forum (and only there) this "wikiwordification" is disabled. The consensus is now to get rid of this function in future and instead use the markdown wikilinks syntax. This is another big task and i don't want to work on this until we have updated Django. The same goes for all the other website related bugs. Working on bugs with an outdated codebasis is imho useless. But thanks for pointing this out, i will create a bug report for this as a reminder Top Quote |