Home → Bug Reports →

WYSIWYG not rendering HTML Entities properly

• Edit

espanae

15 Aug, 2012 08:06 PM

When pasting rich text into a WYSIWYG editor, occasionally we'll find tags in the HTML source, both at the top and bottom of the field.

<system-xml></system-xml> .... <system-xml></system-xml>

This causes a "null" error when saving the page, so we have to delete the tags using the HTML source. But if the WYSIWYG field had any HTML entities (e.g. curvy apostrophes, curvy quotes, etc.) prior to editing the HTML source, they get rendered as their entity numbers after the WYSIWYG editor refreshes itself. The HTML entity issue also happens after clicking the "Back" button on the Spell Check screen.

We're using Cascade Server 7.02. Attached is a screen shot of the HTML entity bug in Firefox 14.01. It also happens in IE 9.

• WYSIWYG-HTML-Entities.jpg 593 KB

1. 1 Posted by Ryan Griffith on 16 Aug, 2012 01:25 PM

   

   Hi espanae,

   Could you also attach a text file containing the rich text you are pasting into the WYSIWYG?

   Just to clarify the steps to recreate:

   1. Edit page
   2. Paste rich text in editor
   3. Submit page
   4. Receive "null" error
   5. Edit page
   6. HTML converted to entities
   • Edit

2. 2 Posted by espanae on 16 Aug, 2012 02:35 PM

   

   Hi Ryan,

   Try this text file, which includes one curvy apostrophe. I haven't been able to recreate the "null" error but here's what you should see:

   1. New page
   2. Paste text into editor
   3. Submit page
   4. Spell Check ("Hannon", "Cassies")
   5. Back button
   6. HTML entities converted to entity numbers and <system-xml></system-xml> are added.

   • Vote-for-2012-Cassies-Awards.txt 98 Bytes
   • Edit

3. 3 Posted by Ryan Griffith on 16 Aug, 2012 03:27 PM

   

   I was not able to reproduce this on my local instance of Cascade 6.10.9. Could you also provide the XML of your Data Definition so I can try to reproduce your setup a bit more?

   Thanks!

   • Edit

4. 4 Posted by espanae on 16 Aug, 2012 04:25 PM

   

   Ryan, thanks for looking into this. We started noticing the bug after upgrading to Cascade 7.02. The data definition we're using is attached. I'd recommend changing all the fields to "optional" for easier testing.

   • data-definition-news-story.xml 1.86 KB
   • Edit

5. 5 Posted by Ryan Griffith on 16 Aug, 2012 06:12 PM

   

   Hi espanae,

   Thank you for your patience. This sounds like a known defect in which returning to the Page creation from a secondary step (ie spell check, link check, accessibility check, etc.) causes <system-xml> tags and numerical entities to be inserted into the WYSIWYG. Feel free to track the progress of this issue using the link I have provided to see if it has been resolved in a future version of Cascade.

   In the meantime, I was not able to reproduce the "null" error you mentioned, this could very well have been some invalid data entered within the WYSIWYG. Once the page is created, the <system-xml> tags should be removed and the numerical entities should be corrected when you edit the Page again. If this is not the case, let us know.

   Please let us know if you have any questions.

   Thanks.

   • Edit

6. 6 Posted by espanae on 17 Aug, 2012 08:20 PM

   

   Ryan, the known defect also occurs after updating the HTML source of a WYSIWYG field.

   -Erik Espana

   • Edit

7. 7 Posted by Ryan Griffith on 23 Aug, 2012 08:41 PM

   

   Hi Erik,

   Just wanted to follow up to see if you have encountered the null error again since your last posting.

   Thanks!

   • Edit

8. 8 Posted by espanae on 04 Sep, 2012 08:20 PM

   

   Hi Ryan,
   I encountered the null error again. Here was the sequence:

   1. New page
   2. Copy text from Notepad
   3. Paste into WYSIWYG editor
   4. Submit page
   5. Spell Check warning screen
   6. Submit (ignore warnings)
   7. Null "XML" error message (red) appears
   • Edit

9. 9 Posted by Ryan Griffith on 05 Sep, 2012 01:28 PM

   

   Hi Erik,

   Thank you for the follow up. Would you be abe to provide the text you are pasting into the editor from Notepad? This way I can try it locally.

   Thanks.

   • Edit

10. 10 Posted by espanae on 05 Sep, 2012 08:41 PM

    

    Hi Ryan,
    Here's the Word Doc that was copied into Notepad and, from NotePad, copied into Cascade's WYSIWYG editor.

    The error showed up in Cascade 7.02 / IE 8 / Windows XP / Word 2003.

    -Erik

    • convocation2012.doc 30.5 KB
    • Edit

11. 11 Posted by Ryan Griffith on 06 Sep, 2012 03:53 PM

    

    Hm, I wasn't able to reproduce the error locally in Cascade 7.0.2 using IE8. The steps I used were:

    1. Copy/Paste contents from Word to Notepad
    2. Copy/Paste from Notepad to WYSIWYG
    3. Submit with Spellcheck, ignore suggestions

    Can you take a screenshot of the error message, the WYSIWYG, and the HTML Source editor of the WSYIWYG (similar to the screenshots in your original post)? Perhaps something might stand out.

    • Edit

12. 12 Posted by espanae on 07 Sep, 2012 03:39 PM

    

    I don't have a computer with Windows XP and IE8 but I was able to reproduce the error in Cascade 7.0.2 and Safari 5 on a Mac using a different Word docx. The steps I used were:

    1. Copy/Paste article from Word to TextEdit
    2. Copy/Paste from TextEdit to WYSIWYG
    3. Submit with Spellcheck, ignore suggestions
    4. Null error

    However, as I write this, I tried reproducing the error a second time but to no avail.

    • Null-error-Safari.tiff 330 KB
    • Null-error-HTML-source.tiff 308 KB
    • starformation.docx 63.2 KB
    • Edit

13. 13 Posted by Ryan Griffith on 07 Sep, 2012 04:48 PM

    

    Erik,

    When you have a chance, could you attach your cascade.log file from around the time of that error? I'm curious if there is anything out of the ordinary in there.

    Thanks!

    • Edit

14. 14 Posted by espanae on 07 Sep, 2012 05:37 PM

    

    Here's today's cascade.log file.

    • cascade.log 315 KB
    • Edit

15. 15 Posted by Ryan Griffith on 07 Sep, 2012 06:52 PM

    

    Erik,

    I believe you are running into the following known defect in which Content Type Index Block caches are not properly cleared when attempting to create a new Page using the same Content Type as the Index Block.

    Can you confirm that you have caching enabled and there is a news story Content Type and at least one Content Type Index Block indexing that Content Type?

    The link I provided explains in a little more information on the issue, provides the steps to reproduce, and offers a workaround. To sum things up, if you have 2 Index Blocks for that Content Type, you need to hit submit 2 times to clear each cache and create the new asset.

    Please let me know if you have any questions.

    Thanks!

    • Edit

16. 16 Posted by espanae on 07 Sep, 2012 07:57 PM

    

    Yes, I can confirm that:
    1. In Preferences > General, we have "Index Block Rendering Cache" enabled.
    2. We have a "News Story" content type.
    3. We have 3 content type index blocks indexing that content type.

    That explains why one person got by the error by hitting submit twice.

    So it sounds like the workaround is to consolidate the two content type index blocks into a single index block?

    • Edit

17. 17 Posted by Ryan Griffith on 10 Sep, 2012 12:15 PM

    

    Great, glad to hear we narrowed that down.

    Until there is a fix, you could either instruct your users to disregard the error message and click Submit 3 times, or as you indicated, consolidate down to one Content Type.

    Please let me know if you have any questions.

    Thanks.

    • Edit

18. 18 Posted by espanae on 11 Sep, 2012 01:38 PM

    

    Prior to Cascade 7.0, I was told index blocks could reasonably index 200-300 assets. With the new index block caching, are index blocks capable of indexing more assets?

    • Edit

19. 19 Posted by Ryan Griffith on 11 Sep, 2012 02:39 PM

    

    If you are not including page content (ie Render page XML inline), you could certainly go well over 200-300. Once you include page content; however, the size of the Index Block will increase quite a bit.

    That being said, with the introduction of caching, you should be able to go over 200-300 because the Index Block won't take nearly as long to render. I'm not sure of an exact number, it really depends on what you are including within your block.

    • Edit

20. Ryan Griffith closed this discussion on 18 Oct, 2012 07:19 PM.