Multiple RichText TVs not showing TInyMCE with NewsPublisher

I'm not sure what to suggest. It worked fine for me with MODX 2.1.3 and TinyMCE 4.3.0. I'm using FF 3.6.12, which could make a difference.

Confirm the problem.
Modx 2.1.5, TinyMCE 4.3.0, Firefox 3.6.24 and Firefox 8 on different PCs.
Can give access to the test site to you BobRay if you wish [ed. note: ztztss last edited this post 14 years, 11 months ago.]

Sorry, I'm completely unable to reproduce this on my site. I believe that it's a problem, but I can't fix it unless I can make it happen.

Do any of you have front-end contexts other than 'web' ?

Does your template have a DOCTYPE, and is the page valid HTML?

When you do a view source on the NP page, are both TVs textareas with class="modx-richtext" ?

Quote from: dezignerjen at Oct 15, 2011, 05:36 PM

My snippet tag looks like this:

[[!NewsPublisher? &initrte=`1` &show=`topNav,Team,Footer` &require=`topNav,Footer` ]]

I'm afraid I've duplicated this exact tag and it works perfectly for me with the current versions of NP and TinyMCE in both FF and Chrome.


BTW, the &require property won't do anything. It has to be &required.
[ed. note: BobRay last edited this post 14 years, 11 months ago.]

BobRay, i PMed you logins to my test site where you can see the problem.
there are only default contexts in the system.

the page has html5 doctype.

the page isn't valid due to the form newspublisher makes
validator says

The for attribute of the label element must refer to a form control.

<label for="content" title="The main content field of the resource.">Resource Content</label>

Here's how textareas look in html. If I put content textearea after a TV textarea it also loses TinyMCE. Only one TinyMCE per page.

And I believe it doesn't concern TVs, it concerns TinyMCE calls. Probably they've changed something in the last version of TinyMCE.

Here is an example of my call wich shows the problem:
[ed. note: ztztss last edited this post 14 years, 11 months ago.]

I'm thinking this may be a problem with either TinyMCE or browser support for HTML5.

See if using another DOCTYPE makes it go away.

Are others with this problem using HTML5?

Hi Bob thanks for reply.

It definitely has nothing to do with doctype and is not a browser issue.
To confirm it I retested with xhtml and html 4.01 doctypes in firefox, opera and ie8.

It is definitely an TinyMCE init problem it probably have changed an algorithm. (Maybe there is a difference whether you update tinymce package or fresh install it on fresh modx? It seems that everyone reporting the issue have fresh installations of modx and tinymce 4.3.0)

Thanks for all the testing.

I think this has been tried already, but it's worth a shot. Right-click on TinyMCE in Package Manager and select 'Remove package'. Repeat that if older versions show up until it's gone. Then re-download and re-install TinyMCE.

You could also try installing an older version of TinyMCE and then updating it -- that would test your theory about new installs.

If that doesn't work, you might try adding this around line 430 of newspublisher.class.php:




Another thing to try is adding this instead:




Replace MyTv# with the actual names of your TVs (as shown in the 'name="something"' code in the source of the page).

[ed. note: BobRay last edited this post 14 years, 11 months ago.]

Thanks for help BobRay.
I am surprised but adding direct calls of elements does not work ((((
i've tried both

Neither does reinstalling TinyMCE 4.3.0 or 4.3.1
What does work is downgrading to TinyMCE 4.2.4 (btw check for updates is not present in the right click menu for it so i couldnt check the update theory)
I'm fine with 4.2.4. But still curious about the bug and ready for tests. Just cannot imagine what else to check. [ed. note: ztztss last edited this post 14 years, 11 months ago.]