Closed (fixed)
Project:
Guestbook
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Jun 2011 at 18:01 UTC
Updated:
13 Jan 2012 at 01:30 UTC
Jump to comment: Most recent file
Hello!
When using full html to write in the users guestbooks, the HTML tags are posted along with the contents of the message. :-)
Best regards,
Ao
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | interdiff.patch | 449 bytes | eric_a |
| #6 | guestbook-1192778-text_format-6.patch | 5.28 KB | eric_a |
| #4 | interdiff.patch | 880 bytes | eric_a |
| #4 | guestbook-1192778-text_format-4.patch | 5.18 KB | eric_a |
| #3 | interdiff.patch | 1.04 KB | eric_a |
Comments
Comment #1
eric_a commentedCurrently, the fallback format will be used when displaying messages. The vanilla Plain Text - the default Drupal fallback format - happens to be a text format that escapes all HTML tags, so they will be visible instead of being effective.
Storing and using a text format for a message/ a comment (and the D6/D7 upgrade path) is on the todo list.
Comment #2
eric_a commentedA completely untested starting point and no upgrade path whatsoever. If you've already installed 7.x-2x you'll have to fix the schema yourself or re-install.
Comment #3
eric_a commentedFixed schema declaration...
Comment #4
eric_a commentedAdded upgrade path.
Please test.
Comment #5
eric_a commentedwhen creating a new comment the patch in #4 results in setting the old global text format, instead of the current user default. Most probably we can do better, so back to needs work.
Comment #6
eric_a commentedThis one only sets the old global format on comments in the database if the comment is not the empty string.
Please test.
Comment #7
andypostThis makes a lot of sense
Comment #8
sunWhy is there no initial value for 'comment_format'?
If that's not an oversight, then we might want to add a short inline comment explaining why.
Comment #9
eric_a commentedI'll try to come up with a decent comment. In the meantime: do you think that apart from the upgrade path the code is ready to commit? Wouldn't it be a good idea to split this up in two parts, then? That would give your user base a nice dev release to work with.
Comment #10
sunI think I get it now; somehow didn't look at the following db_update().
Thanks for reporting, reviewing, and testing! Committed to 7.x-2.x.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.