Gutenberg Support

[rogerburkhard]

With WP 5.0. WordPress plans to change to the Gutenberg Editor. Today I tested some pages where I used Q-Translate-X with the Gutenberg Plugin and unfortunately I couldn’t even switch the language or save any content in the Backend. Are you planning to add support for Gutenberg or not? If not it would be good to have alternatives. Thanks a lot!

[mrfoxtalbot]

I´m not sure this will fix your problem with Gutenberg, but you can try changing the language interface in: Settings > Languages > Advanced > Editor Mode and choose "Single Language Mode" www.yoursite.com/wp-admin/options-general.php?page=qtranslate-x#option_editor_mode

[mrfoxtalbot]

Follow up comment: I tried it and it does not work, Guteberg gets rid of qTranslate-X´s shortcodes :(

[rogerburkhard]

Thanks a lot for looking into this. Currently I have a lot of problems with many different Plugins + Gutenberg, so I really hope they add the possibility to opt out of Gutenberg.

[X-Raym]

+1 for Gutenberg support ! 👍 Currently, the edit page is completely messed up if you edit with Guteberg (v1.8) and I think some things have to be done from qTranslate side to make it work (but I don't know the details about how Gutenberg plan to be backward compatible with some older features). But I understand that this could be a very difficult task, and for those who want to use Gutenberg, I'm afraid they will have to change their translation plugin... or to deactivate Gutenberg (I'm sure they're will be a way, plugin or whatever).

[k9t9]

@X-Raym

and for those who want to use Gutenberg, I'm afraid they will have to change their translation plugin..or to deactivate Gutenberg

This is not really a long term solution. If WP really will migrate to Gutenberg as a permanent editor - all the plugins will have to adapt - or die .

[colinloretz]

@k9t9 WordPress intends to have Gutenberg shipped as the standard editor in WP version 5.0 with an optional plugin that can disable it.

[k9t9]

@colinloretz - that was exactly my point.

[rogerburkhard]

I think a short Term Solution is the Classic Editor Plugin to deactivate Gutenberg. Long term I think I will switch to Polylang as I made some tests with WPML and Polylang.

[colinloretz]

I'm working on adding QTranslate to Gutenberg, it is necessary for our site to stay up to date with what comes standard in WordPress instead of opting out of the new editor.

[marciomarim]

I would really appreciate if QtranslateX could work with Gutenberg! I have many websites running multilanguage with Qtranslate X, and migrate all of them to another plugin would be really painfull... Any updates?

[chrilleferna]

SO. WP 5.0 is now upon us. I just installed and tested qtranslateX and (as expected) it does not work with the default Gutenberg editor. Does anybody know if anybody is working on an update to qtranslateX, which I really like and use on several sites??

[arvineslami86]

qTranslate-X is discontinued since 2016, qTranslate-XT took over: https://github.com/qtranslate/qtranslate-xt .

There's one decent workaround to continue using qTranslate- alongside Gutenberg. So, you made your post (or page, project, .. whatever) with Gutenberg and qTranslate- and Classic Editor plugins are active. Now go to the "All posts" page and open your post through the "Classic Editor" sub-option below the name of the post. Translate the post as you always did before having Gutenberg, but be careful not to change the structure, only substitute texts. Update it. You'll see that all functionalities of Gutenberg are still affecting the post and translations are there. There is a little incompatibility with newlines, to solve this just be sure to delete double newlines once for each language right before updating the post.

[chrilleferna]

Thanks Arvin. Since I wrote my comment an hour ago, I have already found, installed and tested qtranslate-xt and it works fine with WP5.0 - using the plugin for the classic editor, and it all seems to work. I don't know if/when I'll switch to Gutenberg (don't really see the advantage). I was aware that the new team stared to think about taking over qtranslate-x, but wasn't aware that there already is a version available to use. This is really GREAT news