MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#637 — Nested TV values incorrectly encoded
Attached to Project —
MODx
Opened by Kevin Yank (kyank) - Thursday, 02 November 2006, 03:22PM
Last edited by Jason Coward (opengeek) - Thursday, 17 May 2007, 03:49PM
Opened by Kevin Yank (kyank) - Thursday, 02 November 2006, 03:22PM
Last edited by Jason Coward (opengeek) - Thursday, 17 May 2007, 03:49PM
| Task Type | Bug Report |
|---|---|
| Category | Core Distribution |
| Status | Closed |
| Assigned To | No-one |
| Operating System | All |
| Severity | Medium |
|---|---|
| Priority | Normal |
| Reported Version | 0.9.5 beta5 |
| Due in Version | Undecided |
| Due Date | Undecided |
| Percent Complete |
|
Details
A template is configured with two TVs: exampleTV and nestedTV.exampleTV is included in the page template as follows: [*exampleTV*]
exampleTV is configured to display using the Image widget, and the Alternate Text property is set to: [*nestedTV*]
Now, if [*nestedTV*] is assigned a value containing characters outside ISO-8859-1 (Latin-1) (for example, ™), those characters are not correctly encoded in the page output.
MODX is configured with UTF-8 character encoding and multi-byte UTF-8 characters are displayed correctly in all other circumstances.
This task depends upon
This task blocks these from closing
Closed by Garry Nutting (garryn)
Wednesday, 21 November 2007, 11:40PM
Reason for closing: None
Additional comments about closing: Closing as per original poster's request - please reopen this if you are still experiencing problems.
Wednesday, 21 November 2007, 11:40PM
Reason for closing: None
Additional comments about closing: Closing as per original poster's request - please reopen this if you are still experiencing problems.
- Field changed: Status (New → Unconfirmed)
- Field changed: Due in Version (0.9.5 → Undecided)
- Field changed: Severity (High → Medium)
Can anyone reproduce this? I am not able to with the 0.9.6 trunk as of revision 32...