TinyMCE TV doesn't work when moved to tab

72 Posts

paramaniac Reply #1, 15 years, 11 months ago

I don’t like the way in Revo that all the TVs you create now come under their own "TV" tab instead of underneath the default fields on the "Create/edit" tab.
So I tend to use the built-in Form Customisation and move all my TVs to the "Create/edit" tab.

One of these TVs is a TinyMCE (4.0.5pl) editor, and when moved to the "Create/edit" tab, it stops working. You cannot place the cursor in the field and none of the buttons work when clicked.

Other types of TVs (text, image, file) all work fine when moved to the "Create/edit" tab.

I have Revo 2.0.4-pl2 Traditional, TinyMCE 4.0.5pl, PHP 5.2.12, MySQL 5.0.67-community, Apache 2.2.14, Firefox 3.6.10.

38 Posts

sebwebdev Reply #2, 15 years, 11 months ago

This also happens in my case in Firefox 3.6.11, Revo 2.0.3pl and TinyMCE 4.1.1.
But only sometimes!
Most of the time the content is filled in correctly.

In IE8 64bit TinyMCE does not show up at all due to an JS error:
Message: Invalid argument.
Row: 1
Charachter: 131399
Code: 0
URI: http://www.gfd-hp.dev.mainag.net/assets/components/tinymce/jscripts/tiny_mce/tiny_mce.js?v=203pl

3 Posts

jaysin Reply #3, 15 years, 10 months ago

Yes, this has just happened to me as well. Hoping for a solution.

72 Posts

paramaniac Reply #4, 15 years, 10 months ago

I submitted it as a bug and it seems to have been fixed, although I haven’t had chance to try the fix yet. Can anyone else have a go and let me know if it works?

See: https://github.com/modxcms/revolution/commit/81d67feee42e13cd156d4f056f44d7caddbcd518

I have noticed a bug whereby when I move a custom richtext (TinyMCE) TV from the TV tab, to the main Edit tab, the TinyMCE editor does not work.
The TinyMCE editor is visible but you cannot put the cursor or type into the editor, and none of the buttons in the toolbar work.

History

Updated by Shaun McCormick 18 days ago

    * Priority changed from Major to Minor


Updated by Shaun McCormick 5 days ago

    * Status changed from Open to Resolved
    * Assignee set to Shaun McCormick
    * Resolution changed from Unresolved to Fixed

Comment

Fixed in https://github.com/modxcms/revolution/commit/81d67feee42e13cd156d4f056f44d7caddbcd518

Updated by Shaun McCormick 5 days ago

    * Status changed from Resolved to Closed

132 Posts

motoxer4533 Reply #5, 15 years, 10 months ago

I went into the 2 files that were changed and manually updated the code. I’m not sure if this is the correct way to do it, but I didn’t want to go through the entire MODx upgrade process. However, changing these 2 files did not fix the problem.

I’m experiencing the problem in Chrome 7.05xxx