NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1
|Anonymous | Login | Signup for a new account||29-03-17 06:26 BST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0011585||phplist application||Message Management||public||23-09-07 20:26||25-05-12 02:51|
|Target Version||4.0.x||Fixed in Version||2.11.7|
|Summary||0011585: Custom Placeholders / Attributes with special characters in HTML-area|
|Description||Use of attribute / Custom Placeholders in a new message HTML-area work fine with letter a-z, but not with swedish signs as "å", "ä" and "ö" (special character).|
In my case i use an attribute called "Företag" as custom placeholder "[FÖRETAG]" in the HTML-area.
Unfortunately the HTML-area converts the "Ö" in the placeholder "[FÖRETAG]" to its HTML-code equivalent.
I tried to use [ATTRIBUTE23] as Custom Placeholder - the attribute ID equivalent of attribute "Företag", without success.
|Additional Information||A suggestion to make attribute/placeholders with special characters work in HTML-area regardless of special characters conversion to its HTML-code equivalent could be to make it possible to use the attribute ID instead, due to its use of only letters within a-z and numbers 0-9.|
Temporarily i am testing to use this attribute [FÖRETAG] in a plain text message, where a HTML-conversion does not take place. After 1 test it did not seem to work with this method (plain text message) either.
My temporary solution right now will be to change the name of the attribute and thereby make the Placeholder use no special characters and because of that hopefully work fine. In example: "[FORETAG]".
Many thanks for other suggestions! Or maybe a fix on this one for future PHPList versions?
|Tags||No tags attached.|
I'm hitting this bug too.
First report of it is 3 YEARS ago! Status is still new and the bug is open...
Are you serious?
Is this normal for PHPList bugs?
Btw.: This is not meant as a flame. I just want to know if it's time to slowly move to the exits...
I've recently noticed that all my phpLIST databases, even though the phpMyAdmin front screen show utf8_unicode_ci or utf8_general_ci collations, have in the tables, a great many rows that are utf8_swedish_ci collation.
This is causing a lot of character corruption across different languages, and unnecessary alphabetic switching to unicode characterisation.
This is only happening with phpLIST. Other scripts on the same servers are not having this issue.
Is there something in the initial build or upgrade that is causing this?
Why is phpLIST not respecting the collation choices of installers and upgraders?
3 years, in the meantime already 5. That's what happens when you have only one developer. If you can provide a patch against the latest SVN, that would help.
I'd say, there's a work around, which is not using UTF characters in attributes. Google gives me quite a few options for other words, without special characters.
No idea of course if any of them are any use. Main issue is, there are often different solutions to the same problem.
Handling UTF in placeholders will be tricky but going down the [ATTRIBUTE23] route is an interesting one.
|working on placeholder stuff, so will try to incorporate this.|
|Copyright © 2000 - 2017 MantisBT Team|