Problem: You want to know the estimated cost for translating specific posts/pages or your entire site before processing the automatic translation. Solution: We recommend checking the response in an existing ticket that discusses how to estimate the number of credits needed for translating your entire website. You can find the detailed explanation here: Estimate Translation Credits.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem: The client was experiencing issues with automatic translation breaking sentences in Elementor and had a previous ticket closed due to not responding in time.
Solution: We recommended the client to: 1) Update Elementor plugins to the latest version. 2) Increase the WP Memory Limit to 256 MB, as per our minimum requirements. 3) Increase the MaxInputVars in PHP settings to 10000, and provided a guide on how to do this which can be found here.
Additionally, our ATE Development Team was already addressing the issue, and we were following up with them for a resolution. We asked the client to update the original content, save it, and apply the translation again to see if the issue persists.
If the solution provided here is not relevant due to being outdated or not applicable to your case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should the problem continue, please do not hesitate to open a new support ticket. You can reach our support forum here.
Problem: The client wanted to translate a page and maintain the same URL structure as the original English URL when using automated translation. The expectation was to have the translated URL slug remain the same as the original English slug, but the translated URL was different.
Solution: 1. Navigate to WPML → Settings. Scroll down to Translated documents options. 2. Select the option
"Copy from original language if translation language uses encoded URLs"
. 3. Click the Save button. 4. Go to WPML → Languages → Site Languages, and click the 'Edit languages' link. 5. In the 'Encode URLs' column on the languages' table, set the translated language to
'Yes'
and click the Save button.
This process should ensure that after automatically translating the pages, the slug will be the same as the original language.
For the original language (English), there is no need to change the setting to "Yes"; it is only necessary for the translated languages.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client needs to export and import WPML content for translations and is asking how to access the WPML Export and Import addon. Solution: If you're looking to download the WPML Export and Import addon, we recommend that you visit our downloads page. Here's how you can find it:
Click on "Download WPML manually".
Scroll down to the bottom of the page to find the addon.
Please note: WPML Export and Import is currently in its alpha stage. Only install this version on a test site, not a live one. If this solution doesn't seem relevant to your situation, please feel free to open a new support ticket in our support forum.
