whaus

same here, wysiwyg-enabled Front-end Editor does not work with Contact Form 7 activated. With CF7 activaed and wysiwyg enabled for Front-end editor, I get “Aloha.jQuery is not a function”

same here. quite a fresh install. with both the “responsive” theme and twentyten as suggested here: https://www.ads-software.com/support/topic/front-end-editor-stopped-working-after-recent-upgrade

I can confirm that the wysiwyg-enabled frontend editor does NOT work with Contact Form 7 activated (the non-wysiwyg works), and that it works once CF7 is deactivated. That applies not only to actual contact form pages, but to all pages (and probably posts).

note that the site is not public yet.

+1!

you can also try this modified version of qtranslate, make sure to read the comments: https://gist.github.com/warenhaus/10990386

as for migration, I think mqtranslate supports migration: https://www.ads-software.com/support/topic/migration-from-qtranslate-to-mqtranslate-description?replies=18

you can also try this modified qtranslate version, make sure to read the comments: https://gist.github.com/warenhaus/10990386

you might try mqtranslate, because the qtranslate version available here does not work with the current wordpress version: https://www.ads-software.com/plugins/mqtranslate/

as for “existing translated sites”, I’m not sure what you mean by that. If you mean that content you translated with polylang should be imported to qtranslate, I don’t think that works, because I presume both plugins work quite differently. I never used Polylang though, so I’m not sure.

eiter try the plugin mqtranslate, which is based on qtranslate, but currently updated, or see here:
https://www.ads-software.com/support/topic/qtranslate-and-wordpress-39/page/2?replies=66#post-5468144

eiter try the plugin mqtranslate, which is based on qtranslate, but currently updated, or see here: https://www.ads-software.com/support/topic/qtranslate-and-wordpress-39/page/2?replies=66#post-5468144

hi,
presuming you updated WP to 3.9,
see here: https://www.ads-software.com/support/topic/qtranslate-and-wordpress-39

@contramare: oops, sorry. thank you for putting up the files in a zip. you can also download or copy&paste them from here (that’s the view without all the changes highlighted):
https://gist.github.com/warenhaus/10990386

thanks akirk. and thank you arctablet for introducing me to mqtranslate.

I checked what chsxf changed in the last update that makes it compatible with the new visual editor and incorporated the changes in the current qtranslate version.

here’s the result:
https://gist.github.com/warenhaus/10990386/revisions

in total, you need to change 5 files:
the 3 in my gist revision.
qtranslate.php for the QT_SUPPORTED_WP_VERSION number.
and qtranslate_core.php with akirk’s fix.

@sgross: did you use your ftp program to make the changes, or did you use the plugin editor built into WordPress?
I suggest you use the builtin editor, and you need to apply both changes.

glad I could help.

Note: as some mentioned already, the Visual editor will not work. qtranslate will work in the text editor, but as WP 3.9 introduces a new version of the visual editor (as lakilevi noted), this will require more changes in how qTranslate replaces that editor.

same goes for the next WordPress (4.0): changing the version number in qtranslate will enable it in text editor mode, but will not make the visual editor work.

please note, re-enabling qtranslate might be a bit trickier with the upcoming WP 3.9 release:
https://www.ads-software.com/support/topic/qtranslate-and-wordpress-39

well, that was fast!
thank you!