Problem: You are working on a site under development and trying to translate the FAQ section using WPML, but the FAQ section is not translated. Solution: We recommend checking your WPML settings for Custom XML Configurations. You might need to add the following XML configuration to ensure the FAQ section translates correctly:
Compare this XML with what is currently set under WPML > Settings > Custom XML Configurations. If this solution does not resolve your issue or seems outdated, we 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. If the problem persists, please open a new support ticket.
Problem: You are working on a site under development and are unable to update the WPML plugin. Solution: If you're experiencing issues with updating the WPML plugin, we recommend you try the following steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key by clicking the little trash icon. 3. Log in to your site and go to the Dashboard >> Plugins >> Add new > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Then click the Register WPML link. 5. Click the Get a key for this site link. 6. It will generate a new key for your site. 7. Copy the key, and paste it back into the input box, and press the Register button. 8. Take a backup of your site and try to update the WPML plugins again.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the translation process keeps looping and does not complete. Solution: If you're experiencing this issue, we recommend you first ensure you have a full backup of your website. Then, follow these steps: 1. Temporarily change the title of the problematic page by adding "test" at the end and save the changes. 2. Clear all caches on your website, including those from caching plugins like Perfmatters and WP Rocket. 3. Open the translation editor and verify that all fields are translated.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if there's a permanent fix available. Ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: The client is working on a site under development and needs to stop two ACF fields from being automatically translated, which are currently locked. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to ACF >> Field Groups. 2. Edit the field group containing the fields you wish to update. 3. Set the “Expert” translation option for that field group. 4. Individually edit each field and set the “Translation preferences” to “Copy” if you want the same default language value to appear in secondary languages. If you prefer not to display anything in a secondary language, select the “Don't translate” option. 5. Click the Save Changes button. 6. Re-save the default language pages to apply the updated settings. For more detailed guidance, check the documentation here: Recommended Custom Fields Translation Preferences for ACF and WPML.
Please note that this solution might be outdated or not applicable to your specific case. We 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. If the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is working on a site and trying to translate content using a Google API map but encountered a syntax error in the console for the Italian page, indicating a potential issue with the translation of the map code. Solution: We recommend checking the Translation Editor to ensure that the Google Map code is correctly copied over to the translations. You can do this by accessing your pages list and clicking on the pencil icon to edit a translation with the editor. If the code is present and properly copied, this should resolve the syntax error. If you continue to experience issues or have questions about a different section, such as the FAQ, please open a new support ticket and provide detailed information along with your debug info.
Please note that this solution might be outdated or not applicable to your specific 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. If the issue persists, do not hesitate to contact our support team for further assistance.
Problem: You are working on a site and trying to translate pages using WPML. During the translation process, you encounter an error with the URL that includes 'ateJobCreationError=101'. You are wondering what the error code 101 means and how to resolve this translation error. Solution: The error code 101 you encountered typically indicates that your site was blocked on our servers, likely due to an interaction issue. We have unblocked your site now. We recommend you check again to see if the issue has resolved.
If this solution does not apply to your case, or if it seems outdated, we 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. If the problem persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the 'pickup country' and 'pickup location' fields in the booking form on their website being translated by WPML, which disrupts their functionality. Solution: 1. We recommend checking the source of these strings. You can do this by navigating to WPML -> String Translation. Once there, search for the strings and try copying them to the secondary language to see if the issue persists. 2. Ensure that all WPML plugins are updated to the latest version. You can update the plugins by going to Plugins -> Add new -> Commercial tab.
If this solution does not resolve your issue or seems outdated, we 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. If the problem continues, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You have translated the mega menu primary header nav menu using WPML, but it still displays in English. Solution: 1. We recommend following the steps described in a similar ticket. Please check this link for detailed guidance: Translation of Mega Menu. 2. If the issue persists, please share the debug information of your site to help us diagnose the problem better. You can find the steps to provide this information here: Provide Debug Information for Faster Support.
If this solution does not apply to your case, or if it seems outdated, we 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
The client is experiencing an issue where changes made to an English page, specifically adding a new h1 tag and an icon, are not being reflected in the translated versions without incurring additional full translation charges.
Solution:
We identified that the main issue stems from the site not being connected to the Translation Memory before making these changes. To resolve this, we recommend connecting your sites to the Translation Memory to ensure translation consistency and avoid similar issues in the future. For detailed instructions on how to connect your sites, please refer to our guide on Automatic Translation Subscription for Multiple Sites.
Additionally, it's important to ensure that during migrations or site copies, the sites are correctly connected to the Translation Memory. This step is crucial for maintaining translation consistency across different environments.
As a one-time gesture, we have deposited 300,000 credits into your account to assist with the translations.
If this solution does not apply to your case, or if it seems outdated, we 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
