[Resolved] I can not translate with the automatic translator anymore

Hi there.

Before this ticket gets assigned to one of my colleagues, I will try to help.

I think either you have selected to use the default WordPress Editor for translations instead of using the WPML translation editors, by setting the settings up like it is shown here in this documentation URL below:

https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/#how-to-use-manual-translation

Or maybe inside the WPML > Settings, for the "Products" post type, the "automatic translate" check is not "YES" like you see in the example from the screenshot that I attached below.

Please let me know how that goes.

Mihai Apetrei

Hi Rani.

In one of the screenshots that you attached, I can't see the "Products" post type. That one needs to be set to "YES", too. I can only see "Pages", "Posts" and other post types.

Mihai

Hi there.

The box I am referring to should be found in WPML > Settings > Post Types Translation > Products row - the last line as you see in my screenshot below.

Is that same box checked for "Products", too?

Thank you for all the info!

I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

**IMPORTANT**

- Please make a backup of the site files and database before providing us access.

- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.

The private box looks like this: hidden link

I will be waiting for your response.

Mihai

Hi there and thank you for your amazing patience!

This helped me take the proper time to investigate on this matter and understand what happened in the backend of the site that caused this situation.

Also, sorry for the delayed response but I don't work on the weekends.

So:

1. If we go to the English backend > Products (hidden link)

2. Hover our mouse over any product (let's take "Påskskum" as an example for now) and click "Edit" (the first option)

3. We will be taken to the default EN backend area of the product: hidden link

4. Here, if we look on the right side, in the "Translations" area (as you will see in my screenshot below), we can see that the "WordPress Editor" is being used instead of the WPML Advanced Translation Editor. If you hover over that area to try to activate our editor, you will also see the reason why this change happened.

5. So, if you go here (hidden link), inside ACF > Field Grups, you will see the settings that are selected for the "filter" group: "Different fields accross languages".

I'm also attaching 2 extra screenshots below.

I'm also attaching the ACF documentation below for the option that you have selected now ("Different fields in different languages"):
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#using-different-fields-across-languages

I hope that things are clearer now.

I had no idea this was related to ACF until I was able to properly take the time to dig inside the backend to understand how things were built. Otherwise, I would have been able to figure this out faster 🙂

Mihai

Hi Rani and welcome back.

1. The site-crashing type of errors (Internal Server Errors - blank pages) are usually related to the server configuration or server limitations being reached.

You can check our documentation to see if you meet all the WPML minimum requirements here: https://wpml.org/home/minimum-requirements/

2. Also, please take a look here:
https://wpml.org/faq/500-error

3. Next time when you get 500 errors, you can also activate the WordPress debug to find out more about what is actually happening when you receive that 500 error (usually the error messages are a bit generic / not very descriptive):
https://wpml.org/documentation/support/debugging-wpml/

4. If WordPress is selected as the default editor, there's no possible way you can use the WPML editors. You need to use one of the other options:

- https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#using-same-fields-across-languages

- https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/

I recommend that you create a full website backup first and then, after you have that, you can play with the options without the risk of losing anything.

I hope that you will find all that information helpful. 🙂

Mihai

Hi Rani.

No worries, you don't need to be a developer.

So, from what I shared above at point 4, practically if you want to translate using the WPML editor, you need to select ANY of the other 2 options EXCEPT the current one that you have selected which DOESN'T support the WPML translation editors.

1. You need to go here:
hidden link

2. Click: "Change option" button as you see in my screenshot below.

3. And select the first or the last option (select the first if you don't want to do any customization) - I sent above documentation that explains what each of these other 2 options do if you want to learn more.

4. Click "Save Changes" once, then wait for the page to save > and then click "Save changes" once more".

Then, you might need to make a small change in the default language version of a product and then you can try to send it for translation and you should be able to use the WPML Editor.

So these steps will resolve the issue reported in this ticket - that you can't use the WPML Editor for translating.

I hope that you will find all this information helpful 🙂

Mihai