events made easy and tinymce

[liedekef]

Hi,

the plugin is working fine with the combo qtranslate-x and EME, but there seems to be an issue with tinymce:
https://wordpress.org/support/topic/bug-when-switch-languages-on-visual-editor
I tried it on my local install and it seems to be the case for me too. Although in the generated html output I see some qtranxs-translatable class being added to the content div, the language switch only works for the text-mode. Maybe the sequence of loading the javascript is wrong (just a thought)?

Franky

[johnclause]

@liedekef Franky: this is indeed strange, it all looks very similar to standard post page, but somehow it does not work. Can you think of a difference why event page could behave differently? Do you do anything non-wp-standard to load TinyMCE? I believe, if everything is done in the same way as on a standard post page '/wp-admin/post.php', it will work.

[liedekef]

I haven't changed the code to add tinymce in quite a while. I use the standard wp call wp_editor in eme_events.php:

wp_editor($event['event_notes'],"content");

[johnclause]

Hi Franky, would you have time to try the latest beta https://github.com/qTranslate-Team/qtranslate-x/releases/tag/3.3.2 ? I think this issue has disappeared, could you confirm?

[liedekef]

That version seems to be working. May I ask what it is that is special for the EME tinymce editor?

[johnclause]

I did not specifically worked on this issue, decided to take a look after the last round of changes to implement Integration Framework, and when I tried eme again, it worked. It is kind of hard to trace back now what was wrong, and maybe it is not important at this point, the only thing that comes in mind is that I moved line "qtx.addContentHooksTinyMCE();" to be executed always and not only on post.php. Ah, that is it, yes, you use admin.php to edit events, so that line was not fired for you before, which means it never worked, we missed it ;) Yes, normally, plugins would use post.php for any kind of posts, and "event" is one of them, but I guess you implemented your own framework.

I am closing it now, we can still write to a closed issue or may reopen it if needed.