After editing a book hierarchy, the titles of some bookpages are blanked out.
It doesn't matter if anything is changed, just saving is enough.
The page locations are also changed to the root of the book. There they remain grouped but in random locations (top/bottom of hierarchy). [see pic 1]
This only occurred with 3 out of the 40 book items. The only difference is the presence of double quotations (basic, i.e. non-tilted) in the title. After removing them, or replacing them with single quotations, the page doesn't suffer from the bug. When adding double quotations the title blanks however.
In revisions the change registers as if the current user changed the title to nothing. [image 2]
The only solution is to revise and change the book location from the page itself.
Pages with single or, 'tilted' double quotation do not suffer the problem. [attachment #3, the top quotes give problems but not the other type]
Best regards,
ps. Running drupal 6.2, with simplenews/lightbox/image (alpha2)/img. Editing with FF3
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | book-double-quotes-bug.patch | 832 bytes | maartenvg |
| problem3.png | 510 bytes | w8461 | |
| problem2.png | 2.84 KB | w8461 | |
| problem.png | 2.32 KB | w8461 |
Comments
Comment #1
gpk commentedMarked #317614: Bug: Enter Double Quote in Book's Title to replicate this bug as duplicate.
Also clarified title/updated version.
Comment #2
maartenvg commentedMarked #321113: Re-ordering book causes nodes to lose title as duplicate.
I'll research this a bit more and see if there's a solution.
Comment #3
maartenvg commentedFound the culprit. The form IDs of the fields are based on the title. If that title contains a " it breaks the input field
compare,
<input id="title without quotes" />and
<input id="title with " a quote." />The last one will not work as expected.
There are several solutions: either escape the slashes, use a different key or replace the quote by its htmlentity.
Attached patch uses a key based not on the title, but on the node-id.
BTW, this is also broken in HEAD, but not in D5 (as far I can tell).
Comment #4
mike_r1977 commentedThe bug doesn't happen to me anymore after I installed the patch in #3. I'm not sure if I'm allowed to change the status of the patch since I'm the only one who seems to have tested it so far, so I apologize in advance if I shouldn't have.
Comment #5
maartenvg commentedA few more people need to review this before it's RTBC. No hard feelings though.
BTW, I recommend that someone with more core experience look at my solution. I'm not entirely sure that my solution is conform the coding standards.
Comment #6
maartenvg commentedThis has been fixed in the latest security update, 6.6.
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.