No Translate To section in WP editor

[herrvigg]

Issue by ruudio Friday Oct 02, 2015 at 12:35 GMT Originally opened as https://github.com/qTranslate-Team/qtranslate-x/issues/276

---

Thank you for this wonderful plugin, it works out of the box, except that I cannot do the translation in the WP editor, the Translate to buttons do not show anywhere, neither in pages nor posts. They should be on the right hand side in the editor as in the screen shots.

I can do manual translations, but no auto translations as supposed to, because of the missing buttons. I am on the latest WP version and also latest qTranslate version.

[herrvigg]

Comment by ruudio Friday Oct 02, 2015 at 12:39 GMT

---

Oh, here is a screen shot to illustrate this behavior.

[herrvigg]

Comment by Grafcom Friday Oct 02, 2015 at 13:19 GMT

---

@ruudio read this https://qtranslatexteam.wordpress.com/troubleshooting/

Try to reproduce the problem under a simpler configuration with as many plugins off as possible and with one of the standard themes, like “Twenty Fifteen”, “StoreFront”, etc. This may help you to figure out which plugin is in conflict.

[herrvigg]

Comment by Grafcom Friday Oct 02, 2015 at 13:21 GMT

---

you use Fusion Page Builder ? See also this: https://qtranslatexteam.wordpress.com/known-issues/ and this https://qtranslatexteam.wordpress.com/incompatible/

[herrvigg]

Comment by ruudio Friday Oct 02, 2015 at 14:32 GMT

---

On the qTranslate web site the to translate section looks like this for auto translation - Ido not have that...

[herrvigg]

Comment by ruudio Friday Oct 02, 2015 at 14:33 GMT

---

I deactivated Fusion Page Builder, that is not it, will try some more. I need the Divi builder though...

[herrvigg]

Comment by ruudio Friday Oct 02, 2015 at 14:34 GMT

---

there are quite a few Spanish speaking videos on youtube that do the translation manually and their interface looked like mine while using qTranslator, strange.

[herrvigg]

Comment by Grafcom Friday Oct 02, 2015 at 15:09 GMT

---

section in Known Issues

If other plugin installs a custom TinyMCE editor on a translatable field served by qTranslate-X, then all kind of problems start to happen. Please, review the list of known incompatible plugins. We are looking into possibilities to enable integration with those plugins. Workaround since 3.3: use ‘Single Language Mode’ or do not switch language during editing session, read release notes for more information. Release notes: https://qtranslatexteam.wordpress.com/2015/03/30/release-notes-3-3/

Does the workaround works? qTranslate X is NOT the same as qTranslate

[herrvigg]

Comment by ruudio Friday Oct 02, 2015 at 16:06 GMT

---

it is qTranslate-X

I will check your suggestions. Thank you so much!

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 13:59 GMT

---

I deactivated many of the plugins, none of them have Tiny MCE as far as I know, except, I left the Divi theme, because there is a lot of content with it. I still do not get the translate to section. So, I did a fresh install for another site, but even there it is not working. On a local site I did another blank install, on WordPress version 4.3.1, theme twenty fifteen, not working there either. Is it the new WordPress version, or the theme twenty fifteen. If this does not work, I will have to do the translation outside the browser editor...

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 13:59 GMT

---

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 14:03 GMT

---

On clean install not working:

[herrvigg]

Comment by Grafcom Saturday Oct 03, 2015 at 14:33 GMT

---

what does not work? I see the Language Switching Buttons, maybe you must read this first: https://qtranslatexteam.wordpress.com/startup-guide/

[herrvigg]

Comment by Grafcom Saturday Oct 03, 2015 at 15:09 GMT

---

Reading again your posts here

I can do manual translations, but no auto translations as supposed to

auto translations is not supposed .....

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 15:21 GMT

---

The Auto Translate to section as in my previpu as email is missing, see the image. I just updated a section under the German tab, for whatever reason the English tab also got updated to German... Op 3 okt. 2015 16:33 schreef "Gunu" notifications@github.com:

what does not work? I see the Language Switching Buttons, maybe you must read this first: https://qtranslatexteam.wordpress.com/startup-guide/

— Reply to this email directly or view it on GitHub https://github.com/qTranslate-Team/qtranslate-x/issues/276#issuecomment-145253522 .

[herrvigg]

Comment by Grafcom Saturday Oct 03, 2015 at 15:26 GMT

---

I just updated a section under the German tab, for whatever reason the English tab also got updated to German...

explain to me more clearly what you mean... Automaticly translate this plugin does not .... English tab shows the page section where you can put your English text, German tab shows the page section where you can put your German text. Am I missing something?

[herrvigg]

Comment by Grafcom Saturday Oct 03, 2015 at 15:36 GMT

---

How it works:

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 15:37 GMT

---

Yes, maybe I am... In your screenshot on the plugin Directory it shows "Translate to" German, English and Chinese. I assumed that there is an in-dashboard, in -browser translation. Am I mistaken? So why does this translate to section appear in the screen shot and not my dashboard? Maybe that is an old version screen shot, my dashboard does not look that way. Anyway, I am inputting manually the translated texts, but after the update the manually input German text is overwriting the other language sections. What to do? Op 3 okt. 2015 17:26 schreef "Gunu" notifications@github.com:

I just updated a section under the German tab, for whatever reason the English tab also got updated to German...

explain to me more clearly what you mean... Automaticly translate this plugin does not .... English tab shows the page section where you can put your English text, German tab shows the page section where you can put your German text. Am I missing something?

— Reply to this email directly or view it on GitHub https://github.com/qTranslate-Team/qtranslate-x/issues/276#issuecomment-145256376 .

[herrvigg]

Comment by Grafcom Saturday Oct 03, 2015 at 15:39 GMT

---

So why does this translate to section appear in the screen shot and not my dashboard?

You are right about that, we must make an actual picture

but after the update the manually input German text is overwriting the other language sections.

Can you give me temporary admin access to your site so I can see what's wrong?

mail me: gunu at marius - siroen d com

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 16:29 GMT

---

yes I can, it is just in testing, it seems the Divi theme may not make it work, I read about compatibility issues on the site

https://wordpress.org/support/topic/qtranslate-x-does-not-support-divi-theme

I am trying to use dashboard language, but now the divi theme editor is gone after the following:

Choice “Single Language Mode” for option “Editor Mode” – provides unbounded compatibility with other plugins and themes. There are no LSB in this mode, and the edit language is the same as admin one. You have to change admin language, if you wish to edit content in other languages

and turning on the compatibility function.

On Sat, Oct 3, 2015 at 5:39 PM, Gunu notifications@github.com wrote:

So why does this translate to section appear in the screen shot and not my dashboard?

You are right about that, we must make a actual picture

but after the update the manually input German text is overwriting the other language sections.

Can you give me temporary admin access to your site so I can see what's wrong?

mail me: gunu at marius - siroen d com

— Reply to this email directly or view it on GitHub https://github.com/qTranslate-Team/qtranslate-x/issues/276#issuecomment-145258975 .

Ruud Straat Drs.- Dipl.-Kfm.

rstraat@gmail.com International Venture

Consulting Business Planning & Optimization - iMarketing

[herrvigg]

Comment by ruudio Saturday Oct 03, 2015 at 16:41 GMT

---

I sent you the login, it is a bit messy now, since the Divi page editor does not show anymore after turning the compatibility function and the single language mode, very strange. I cannot go w/o the Divi editor, because it would destory the theme setup - I am told by Divi...

On Sat, Oct 3, 2015 at 6:29 PM, Ruud Straat rstraat@gmail.com wrote:

yes I can, it is just in testing, it seems the Divi theme may not make it work, I read about compatibility issues on the site

https://wordpress.org/support/topic/qtranslate-x-does-not-support-divi-theme

I am trying to use dashboard language, but now the divi theme editor is gone after the following:

Choice “Single Language Mode” for option “Editor Mode” – provides unbounded compatibility with other plugins and themes. There are no LSB in this mode, and the edit language is the same as admin one. You have to change admin language, if you wish to edit content in other languages

and turning on the compatibility function.

On Sat, Oct 3, 2015 at 5:39 PM, Gunu notifications@github.com wrote:

So why does this translate to section appear in the screen shot and not my dashboard?

You are right about that, we must make a actual picture

but after the update the manually input German text is overwriting the other language sections.

Can you give me temporary admin access to your site so I can see what's wrong?

mail me: gunu at marius - siroen d com

— Reply to this email directly or view it on GitHub https://github.com/qTranslate-Team/qtranslate-x/issues/276#issuecomment-145258975 .

Ruud Straat Drs.- Dipl.-Kfm.

rstraat@gmail.com International Venture

Consulting Business Planning & Optimization - iMarketing

Ruud Straat Drs.- Dipl.-Kfm.

rstraat@gmail.com International Venture

Consulting Business Planning & Optimization - iMarketing

[herrvigg]

Comment by Grafcom Sunday Oct 04, 2015 at 08:46 GMT

---

changed the Editor Mode to:Use Language Switching Buttons (LSB). Made a test page with the name Gunu. Everything works as expected using the Language Switching Buttons.

[herrvigg]

Comment by ruudio Sunday Oct 04, 2015 at 10:24 GMT

---

Yes, it does look good, I will test it when I get home. You guys are great, this us rare you know. Op 4 okt. 2015 10:46 schreef "Gunu" notifications@github.com:

changed the Editor Mode to:Use Language Switching Buttons (LSB). Made a test page with the name Gunu. Everything works as expected using the Language Switching Buttons. [image: ruud] https://cloud.githubusercontent.com/assets/11356362/10267101/bb58cff8-6a7c-11e5-8fd5-db71550df376.jpg

— Reply to this email directly or view it on GitHub https://github.com/qTranslate-Team/qtranslate-x/issues/276#issuecomment-145328352 .

[herrvigg]

Comment by ruudio Monday Oct 05, 2015 at 20:41 GMT

---

Yes you are right, but I cannot make edits using Divi, or can I? If I want to use Divi I get the following message, telling I may destroy all Divi edits, that would be awful...

[herrvigg]

Comment by ruudio Monday Oct 05, 2015 at 20:44 GMT

---

Basically, when I edit German, Divi has the English for example, I enter the German, upon update all the Divi content changes, irrespective of the language tab settings of qTranslate. I do not think I will be able to make edits using the default editor, because it destroys all the edits.

[herrvigg]

Comment by Grafcom Monday Oct 05, 2015 at 20:58 GMT

---

See my test pages (second one I believe) on your site.... there is one with text in Divi modus made. Otherwise, you should use the alternative way:

Workaround since 3.3: use ‘Single Language Mode’ or do not switch language during editing session. Choice “Single Language Mode” for option “Editor Mode” – provides unbounded compatibility with other plugins and themes. There are no LSB in this mode, and the edit language is the same as admin one. You have to change admin language, if you wish to edit content in other languages. This mode introduces certain inconvenience, which is supposed to be outweighed by the compatibility benefits, if compatibility issue is a problem for a particular plugin and theme set. However, this essentially works the same way as normal LSB in case a user consciously decides not to switch the edit language during one editing session. This is why the advanced users may still use the default LSB mode, while taking special care of translatable fields at trouble. If you do not switch edit language during a session of editing of incompatible translatable field, then after pressing “Update” button your changes will be saved. If you switch language with LSB after editing an incompatible field and before pressing “Update” button, the changes may be lost. Conscious not switching the edit language on certain fields allows you to still use LSB mode, which bring convenience back for all other well-behaving fields.

[herrvigg]

Comment by ruudio Monday Oct 05, 2015 at 22:48 GMT

---

Thank you!!! "Choice “Single Language Mode” for option “Editor Mode” – provides unbounded compatibility with other plugins and themes. There are no LSB in this mode, and the edit language is the same as admin one.": After switching to single language mode, the Divi builder does not show up on your second test page. It does show up again when I try to create a new page or your first test page, at least the icon, but clicking on the Divi editor icon does not let me into the Divi editor, it is non-responsive. I will not be able to use Divi then to finish the site, or what do you think?

[herrvigg]

Comment by jcnavamorffe Wednesday Dec 07, 2016 at 15:19 GMT

---

i instaled vc-mega-menu, a plugins for Visual Composer, also, the compatibility plugins for VC Bakery for qtranslate-x, and work fine, but with that plugin (vc-mega-menu) no. :(

help Please

[herrvigg]

Old issue but certainly not solved for Divi yet. See #769 for more recent updates.