Problem: The client is unable to automatically translate the URL slug when using WPML. Despite having automatic translations enabled, the URL field remains empty in the translation editor and defaults to the English slug, which does not meet the client's needs as they often differ from the page title. Solution: 1. To address the issue of untranslated URL slugs, we recommend following the steps in our guide on translating page slugs. You can find the guide here: Translating Page Slugs. 2. If you prefer the URL slug to auto-translate based on the page title, select the 'Auto-generate from title (default)' option in WPML -> Settings -> Translated documents options -> Page URL. 3. For manual translation of the slug, choose the 'Translate' option in the same settings area. This will allow the slug to appear in the Translation Editor for manual adjustment. 4. If these settings do not resolve the issue, we have also provided a screencast with additional steps that might help. View the screencast here: WPML Slug Translation Screencast.
Please note that the solution provided might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML 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.
Problem: You are trying to delete ACF repeater fields in the English version of your site, but after deletion, these fields still exist in other languages. Additionally, when trying to save translations in the WPML Translation Editor, the segments are not saving. Solution: First, ensure that all Repeater Fields and Groups are set to "Copy" in the ACF configuration. This setting helps synchronize the deletion across all languages. For more details on setting up field configurations, visit Recommended Custom Fields Translation Preferences for ACF and WPML.
Next, check your server's minimum requirements. WPML requires a WordPress memory limit of at least 128M, but your PHP Memory Limit is currently set to 128M, which might be insufficient. We recommend increasing the WordPress memory limit to at least 256 MB. Contact your hosting provider to adjust the PHP MEMORY LIMIT on the server to at least 256M or higher.
If this solution does not resolve your issue or seems outdated, please check for 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. If problems persist, we recommend opening a new support ticket at WPML support forum.
Problem: The client is unable to translate the updated RankMath snippet titles and descriptions because these strings are not visible in the WPML Translation Editor. Solution: If you're experiencing this issue, it's because the WPML Translation Editor is currently deactivated for this content. We recommend managing translations directly via the WordPress Editor. To adjust Rank Math settings for pages handled via the WordPress Editor, open the WordPress Editor and click on the hamburger icon (three dots) in the top-right corner. From there, you can access Rank Math and make the necessary adjustments for each page.
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: You are experiencing an issue where internal links are not being auto-translated when using the ACF Link field inside Flexible content. For example, the link remato.com/pricing does not change to remato.com/et/hinnakiri. Solution: We are aware of this issue and it should be addressed in the upcoming release of ACF Multilingual. We recommend installing the beta version of the plugin to see if it resolves the problem. You can check the changelog here.
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. For further assistance, you can contact us directly at WPML support forum.
Problem: The client is unable to see URL slugs in the page translation UI when trying to translate a new page URL slug, despite following the guide on translating page slugs. This issue is inconsistent across different environments and accounts. Solution: 1. Make a minor edit to the page in the default language and update it. Then, check if the translation shows the URL slug correctly. 2. If the issue persists, create a new test page or post, add a translation, and see if the slug appears in the editor. 3. Clear your site's cache as it might be a caching issue affecting the visibility of translated slugs. 4. If none of the above steps resolve the issue, it could be helpful to test using a different user account to see if the problem persists. 5. For further troubleshooting, especially if the problem occurs only in specific environments, provide temporary access to your site for detailed investigation by the WPML support team.
Please note that the 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.
