HTML Edit Window is Blank

john forsyth's Avatar

john forsyth

12 Dec, 2013 01:21 AM

When I click on the HTML button on an edit page the HTML edit window opens but is blank. Previously I have seen the NTML code there and been able to edit it. Has this feature been elimiated?

  1. 1 Posted by Ryan Griffith on 13 Dec, 2013 09:17 PM

    Ryan Griffith's Avatar

    Hi John,

    Apologies for the delayed response.

    The HTML editor feature for the WYSIWYG has not been removed. There is an option at the Group level to disable the HTML button, but that would remove it entirely as opposed to showing you a blank window.

    I have a few questions to see if we can narrow things down a bit:

    • What version of Cascade Server are you experiencing this behavior in?
    • If you view your browser's developer console, do you see any JavaScript errors? If so, please paste them or attach a screenshot to this discussion.
    • When you say blank, is the entire popup window blank, or is the textarea where the HTML should be blank?

    Also, when you have a moment, would you be able to attach/paste the HTML contents of the WYSIWYG? This can be accomplished by previewing the page, right-clicking within the preview area, and viewing the frame source (Chrome: View Frame Source; Firefox: This Frame->View Source).

    Please let me know if you have any questions.

    Thanks!

  2. 2 Posted by John Forsyth on 15 Dec, 2013 07:29 PM

    John Forsyth's Avatar

    Ryan, Cascade Server v7.4.1

    I see no JavaScript errors The frame of the popup window is complete and the buttons at the top and bottom are present and work, at least Cancel works. The area inside the window is empty where the text should be.

    I am using Internet Explorer 11 version 11.0.2 on Windows 8.1 and Windows 7 machines. I went to an old WindowsXP machine and was still able to use the HTML source editor.

     

    WYSIWYG is attached.

     

    John

  3. 3 Posted by Ryan Griffith on 16 Dec, 2013 04:33 PM

    Ryan Griffith's Avatar

    Hi John,

    Thank you for the additional information. Looking over your description of the problem, it sounds as though you are running into this known defect with TinyMCE (the library used for the WYSIWYG). It appears the version of TinyMCE we are currently using as of Cascade Server 7.8.1 (v3.5.8) does not fully support IE11.

    Also, I wanted to note that IE11 is not yet officially supported as of Cascade Server 7.8.1.

    I do see we have an internal improvement logged for IE11 support in general, which also includes testing TinyMCE support, as well as an improvement for upgrading TinyMCE. Unfortunately, I do not have a timeline for either of these, but I can say they are relatively high on our timeline. In the meantime, a workaround would be to either use a supported version of IE or another supported browser.

    Please let me know if you have any questions.

    Thanks!

  4. 4 Posted by Ryan Griffith on 23 Dec, 2013 01:14 PM

    Ryan Griffith's Avatar

    Hi John,

    Just wanted to follow up to see if you had a chance to view my recent comment. My apologies for any inconvenience this may be causing.

    Please let us know if you have any questions.

    Thanks.

  5. Ryan Griffith closed this discussion on 03 Jan, 2014 03:56 PM.

  6. Ryan Griffith re-opened this discussion on 09 Jan, 2014 02:29 PM

  7. 5 Posted by Ryan Griffith on 09 Jan, 2014 02:29 PM

    Ryan Griffith's Avatar

    Hi John,

    I wanted to follow up with you regarding the TinyMCE HTML source editor issue in IE11. After some investigating, it appears we were able to identify the issue is related to our TinyMCE configuration and the source editor plugin that is bundled with TinyMCE. It appears that if a specific parameter is not present, IE11 will throw a JavaScript error when the popup attempts to load.

    Although I do not have an official timeline, I wanted to let you know this issue is very high on our timeline and should be resolved in the near future.

    Note: there are additional issues relating to IE11 and our version of TinyMCE, but at least we can address the source editor issue.

    Please let me know if you have any questions.

    Thanks!

  8. Ryan Griffith closed this discussion on 09 Jan, 2014 02:30 PM.

  9. John Forsyth re-opened this discussion on 10 Jan, 2014 03:30 PM

  10. 6 Posted by John Forsyth on 10 Jan, 2014 03:30 PM

    John Forsyth's Avatar

    Thank you for keeping me informed. I have not put a TinyMCE patch in my code because I don’t like things hidden that might bypass the Cascade Server features. I can still do HTML editing with Firefox and Windows XP, but IE 11 is more convenient. Thanks again. John Forsyth

  11. 7 Posted by Ryan Griffith on 10 Jan, 2014 07:18 PM

    Ryan Griffith's Avatar

    Hi John,

    Thank you for following up. If you would like, I can provide you with instructions on applying the additional parameter to our TinyMCE configuration I was referring to until the official fix has been released (it's a one liner). Let me know if you would be interested.

    Thanks!

  12. Ryan Griffith closed this discussion on 21 Jan, 2014 07:00 PM.

  13. John Forsyth re-opened this discussion on 13 Feb, 2014 07:03 PM

  14. 8 Posted by John Forsyth on 13 Feb, 2014 07:03 PM

    John Forsyth's Avatar

    Ryan, the upgrade to version 7.8 corrected the problem of using HTYML editing under IE 11. Thank you.

  15. 9 Posted by tthomas on 13 Feb, 2014 07:13 PM

    tthomas's Avatar

    Sweet!

    We will try to get our test instance upgraded asap and confirm.

    Thanks!

  16. 10 Posted by Ryan Griffith on 13 Feb, 2014 07:43 PM

    Ryan Griffith's Avatar

    Thank you for following up, John.

    That is correct, the fix was incorporated as part of the Cascade Server 7.8.4 release.

    I'm going to go ahead and close this discussion, please feel free to comment or reply to re-open if you have any additional questions.

    Have a great day!

  17. Ryan Griffith closed this discussion on 13 Feb, 2014 07:43 PM.

Discussions are closed to public comments.
If you need help with Cascade CMS please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

 

26 Aug, 2016 01:19 PM
25 Aug, 2016 03:02 PM
25 Aug, 2016 12:50 PM
24 Aug, 2016 08:43 PM
24 Aug, 2016 07:20 PM
21 Aug, 2016 01:20 PM