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.
The client reported an issue where a page that is not translated is displaying language icons at the bottom, and language flags are not showing on another page.
Solution:
We explained that the 'Suppliers' post type is set to 'Translatable - use translation if available or fallback to default language' in the WPML settings. This setting allows content to be available in English and also in secondary languages without needing a translation, which explains the presence of language icons.
Regarding the missing language flags, the Spanish post is created in Spanish and is not translated into any secondary languages nor is it a translation of an English post. This is why it does not show language flags in the footer. This behavior is expected under the current settings.
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.
The client needs urgent assistance with registering their live site with a new WPML license key.
Solution:
If you're experiencing this issue, we recommend you follow these steps after ensuring a full site backup (mandatory):
1. Visit your account page at https://wpml.org/account/sites/ 2. Delete the existing key for your site. 3. Navigate to Plugins>>Add New>>Commercial tab on your site dashboard. 4. Click on "Unregister WPML from this site". 5. Refresh the page. 6. Click on "Get a key for this site". 7. Copy the newly generated code. 8. Return to Plugins>>Add New>>Commercial tab. 9. Register the site with the new key.
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 open a new support ticket at WPML support forum.
The client is moving their website to a new WordPress installation and encountering issues with duplicate destination URLs, such as -2, -3, etc. The developer suspects this is due to WPML not being registered on the development site.
Solution:
We recommend registering the development site with a new WPML site key and ensuring WPML is updated to the latest version. Here are the steps to follow:
1. Go to
Plugins>>Add New>>Commercial
tab on your development site. 2. Click on "Unregister WPML from this site". 3. Refresh the page. 4. Click on "Get a key for this site" and follow the instructions to generate a new key. 5. Copy the newly generated code. 6. Return to
Plugins>>Add New>>Commercial
tab. 7. Register the site with the new key. 8. After registration, resave the permalinks via
Settings>>Permalinks
to check if the issue with duplicate URLs persists.
Additionally, ensure that the Advanced Translation Editor is migrated correctly if you are using it. For more details, refer to this documentation.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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. For further assistance, you can contact us directly through the WPML support forum.
The client reported that after moving their site, the language parameter was not included in the URLs as expected, despite having set the URL to use directories for different languages.
Solution:
We first checked if there was a compatibility issue and requested screenshots of certain dashboard pages to track the issue. It was discovered that the Custom Post Type 'Destinations' was not set to be translated. We advised the client to:
1. Ensure a site backup is done. 2. Go to WPML>>Settings>>Custom Post Types translation and set the 'Destinations' post type to 'Translatable – only show translated items' and save the changes. 3. Visit Settings>>Permalinks and resave the settings to ensure the changes take effect. For more details, refer to our documentation on translating custom posts.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
