I am assuming that at the moment your site is using Classic Translation Editor as the editor of choice or at some point it was for majority of translations, correct?
When a translation is created with CTE, if you switch to ATE, you will notice that now you will need to re add the translation all over again or vice versa.
--------------------
WPML has a feature that if enabled it prevents a page from switching to ATE if prior CTE was used.
Go to WPML->Settings->Translation Editor->Advanced Translation Editor-> enable"Use also for old translations created with the classic editor"
However, do note that what I discussed above will take effect.
Once that is done you should be able to send and pull translations from the Translation Service and use the ATE editor.
I tried again by selecting these options, deleting the translated page, and sending it to an external agency. However, after I received the translation back from my external provider, the ATE was still unable to upload the translated text.” What can I do?
Did you try to pull the translation from within WPML or manually importing it?
I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)
**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **
I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.
NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.
I have reviewed the site as well as run some troubleshooting actions.
The latest pull from Wordbee I can see is coming through OK.
Also, it works if I download the XLIFF file.
Vegalsa
View original
Página ES » GL Wordbee Beebox TP ID: 2463839 2026-03-27 Completed
After careful consideration and discussion with our team I can verify that
Translation done via translation service will not be visible in ATE WPML editor, you either need to disable WPML editor and do this manually or use Classic Translation editor from WPML.
You can specifically choose to do this with certain pages only if you wish to use ATE with other pages.
However, the 2 will not communicate -- this is because ATE editor pulls the translations from the Cloud and not the database, therefore the translations provided via the Translation Service would not be available to it to download.
The extraction from Wordbee is working correctly. However, when I want to make any changes in the Advanced Translation Editor (ATE), the translations I received from Wordbee do not appear in the editor.
So although the XLIFF file can be downloaded and the latest pull from Wordbee comes through correctly, the imported translations are not being displayed inside ATE.
Could you please check why the translations pulled from Wordbee are not visible in the Advanced Translation Editor?
Unfortunately I have verified that this is not possible at the moment.
This is because the two operate in different ways.
The ATE editor pulls data from the cloud and not the database, therefore it would not be able to recognize and display the content pulled via Translation Services.
"Translation done via translation service will not be visible in ATE WPML editor, you either need to disable WPML editor and do this manually or use Classic Translation editor from WPML."
The topic ‘[Closed] Compatibility between External Translation Provider (Wordbee) and Advanced Translation Editor with D…’ is closed to new replies.
