Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 -
- 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 -

Supporter timezone: Europe/Vienna (GMT+02:00)

This topic contains 7 replies, has 1 voice.

Last updated by annaG-48 6 hours, 53 minutes ago.

Assisted by: Bigul.

Author Posts
July 16, 2025 at 2:04 pm #17241165

annaG-48

Background of the issue:
I am trying to set up the WPML Plugin for auto-translation of the pages we already have on the site hidden link.

Symptoms:
Unable to set up WPML.

Questions:
How do I set up the WPML Plugin for auto-translation?

July 16, 2025 at 2:36 pm #17242732

annaG-48

hi

July 16, 2025 at 3:47 pm #17242963

Marcel
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: Europe/Madrid (GMT+02:00)

Hi,

before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.

The automatic translation feature is enabled by default. You can find a detailed overview, including a short video, here:
https://wpml.org/documentation/automatic-translation/

To better understand the issue, could you please provide more details about what exactly isn't working? Are you seeing any warnings or error messages?

Looking forward to your response.

Best regards,
Marcel

July 16, 2025 at 3:49 pm #17242965

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

Hi,

This is our getting started guide.

https://wpml.org/documentation/getting-started-guide/

You can also do this:
https://wpml.org/documentation/automatic-translation/#sending-content-to-automatic-translation

And after this enable translate everything mode. Let me know if unsure how to set this up.

July 24, 2025 at 4:52 pm #17268769

annaG-48

We keep having issues with our site ciistaging.wpengine.com in relation to the plugin: We keep having 500 errors on the website that appear to be random throught navigating the site both in the frontend and in the backend, and the error contains the same message

PHP Fatal error: Allowed memory size of XXXXX bytes exhausted" on different php files on the sitepress-multilingual-cms/ folder which is the plugin's main folder on the wp-content/plugins/ directory. Our site is currently on php 7.4, and we've already implemented the recommended configuration of WPEngine as described here: hidden link to increase the allowed memory but the problem remains.

We've contacted support about the issue and the support team told us the problem is with a memory leak issue within the plugin itself and that we should contact you for further assistance.

July 24, 2025 at 4:55 pm #17268775

annaG-48

One more note, we deactivated the plugin the other day to test and the 500 error went away. This confirms that the error is coming from the plugin.

July 24, 2025 at 7:32 pm #17269147

Bigul
WPML Supporter since 01/2013

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. Could you please confirm whether you are still facing issues with Automatic Translation?

It is possible that the PHP Fatal error: Allowed memory size exhausted issue is related to a compatibility conflict. To help rule this out, please update WordPress to the latest version (6.8.2) and WPML to the latest 4.7.6 series, after taking a full site backup.

Once updated, check again to see if the issue persists and let us know your findings.

Please note that you may have to visit Plugins >> Add Plugin >> Commercial tab and click on the *Check for updates* button to get the WPML automatic upgrade links of the latest version. This step will help us refresh the installer caches.

--
Thanks!

Bigul

July 25, 2025 at 2:12 pm #17271476

annaG-48

Hi Bigul, the plugin was already on 4.7.6. The website was updated from 6.8.1 to 6.8.2 but we're still seeing the same issue.