Problem: The client was attempting to change the language URL format from a parameter to different languages in directories, but encountered issues where the settings would not save and the site would revert to using language parameters.
Solution: 1. We verified that there was no redirect file in the root directory where WordPress is installed. 2. We created a redirect file named
wpml.php
, added the necessary Header information, and set up a redirect from the main domain to the '/sk' directory for the Slovak version of the site. 3. After these changes, the site successfully redirected to the Slovak version, and the issue with the blank page on the main domain was resolved.
If you're experiencing a similar issue, we recommend checking for the presence of a redirect file in your root directory and ensuring it's correctly configured. For more information on setting up language directories, please refer to our documentation on Language URL options and redirecting the root page of your site.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket in our support forum.
Problem: The client encountered an issue where after updating a translation, the shortcode for a Fluent Form reverted to the original language shortcode instead of the translated one. The client had previously translated the shortcode using String Translation and added custom XML configuration and PHP code to make the shortcode translatable, but was unable to find the shortcode in the Advanced Translation Editor (ATE) window.
Additionally, we suggested that if the client is using the Divi builder, they could manually edit the second language page and ensure that the same shortcode/form from the default language page is present, allowing for manual adjustments as needed.
Please note that this solution might not be applicable if it's outdated or not relevant to your specific case. If you're experiencing similar issues and the provided solution does not help, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us on the WPML support forum.
Problem: The client was unable to find the header translation in the WPML Translations page and was instead seeing a 404 page. The header had been translated in the past and worked when manually requested through the translation basket, but the client was unsure how to proceed with changes in the header/footer for future updates.
Solution: 1. We asked the client to check the DIVI options to ensure the header template was set correctly, as it was mistakenly named "404 error". 2. We provided a guide for translating custom global headers and footers with the Divi Builder: https://wpml.org/documentation/theme-compatibility/divi-builder/#translating-custom-global-header-footer 3. We suggested making a small change to the header/footer to see if the issue persisted. 4. After renaming the header template page the header translation worked.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 you still need assistance, please open a new support ticket with us.
Problem: The client is receiving notifications from Wordfence about obsolete WPML plugins that have not been updated for 3-4 years and is wondering if they can disable these plugins without affecting site functionality or if there are plans to update them for compatibility with the latest version of WordPress. Solution: We assure the client that the plugins in question are still safe to use despite not being updated, as there have been no changes to their code. If the client is using the features provided by these plugins with their current theme, we recommend keeping them. For more information, we provide documentation links:
Problem: The client is unable to find the string for the translation of the custom text in the Divi Pixel plugin's Table of Contents module. Solution: We recommend the following steps to translate the Pixel Table of Contents elements using WPML's Advanced Translation Editor:
1.Please make sure to add the table title manually in Pixel Table of Contents “Table Title” field.
2. Insert the following XML in the WPML >> Settings > XML Configuration section:
3. Make a small change in the default language page and then open the translated page in WPML's Translation Editor. The table title should now be available for translation.
Problem: The client is unable to allocate prepaid credits to their site, specifically to a development site that has been changed to production. They also cannot see the option to allocate or transfer prepaid credits within the Translation Management tools, only the pay-as-you-go option is visible. Solution: 1. Unregister and re-register the site with a new sitekey. 2. Assign credits again to the development site. Refer to the documentation on how to unregister and register development sites:
To transfer credits back to your WPML.org account or add credits to your site: 1. On your site, use the option to transfer credits back to your WPML.org account. 2. On your WPML.org account, add credits to your site, or delete the sitekey to get credits back. Refer to the documentation on how to assign automatic translation credits: Assigning Automatic Translation Credits
