Problem: The client reported an issue with incorrect URL slugs in different languages on their website. Specifically, the URL slug did not translate correctly for subpages in Slovenian and Croatian, showing 'services' instead of the correct translations 'storitve' and 'usluge'.
Solution: We resolved the issue by translating the Properties post type slug in WPML -> Settings -> Post Types Translation. After updating the slugs for Slovenian and Croatian, the URLs displayed correctly on the frontend, including subpages and menu items. For further guidance on translating page slugs, please visit Translating Page Slugs documentation.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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, please contact us through the WPML support forum.
Problem: The client was facing an issue with displaying content correctly on a multilingual website using Advanced Custom Fields (ACF). The specific problem was related to the custom field "thegem_post_item_gallery_images" not showing expected results in different languages. Solution: We recommended setting the custom field "thegem_post_item_gallery_images" to "Copy" in the WPML > Settings > Custom Field Translation section. After this adjustment, the client needed to update the original post and save it, then update the translation. This action resolved the issue.
Please note that this solution might be outdated or not applicable to your specific case. If you're still experiencing issues, 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 problem persists, please open a new support ticket.
Problem:
The client reported two issues: firstly, the 'add to cart' button and 'read more' button were not translated after scrolling down and loading more products on the category pages. Secondly, some fields in the cart and checkout pages reverted to English despite being previously translated to Slovenian. Solution:
Step 1: We asked the client to check the staging site with a minimal setup, including only WPML plugins, WooCommerce, WooCommerce Multilingual, and the theme, to ensure all strings were correctly translated.
Step 2: We instructed the client to reactivate plugins one by one to identify if any plugin was causing the translation issue.
Step 3: After the client updated all plugins and the theme, and reactivated each plugin, the issue was resolved, likely due to outdated cache being cleared.
Step 4: To translate the 'page not found' string in the browser tab, we provided a link to the String Translation page: String Translation.
Step 5: We advised that Loco Translate is not necessary if the client is using WPML's String Translation, as it is more powerful.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us on the WPML support forum.
Strings inside the cart page can not be translated
Solution:
The customer used an element from Elements pro plugin which is not compatible with WPML, that is why the strings from the Elementor elements of that plugin was not available in translation editor.
The solution was to use the manual translation mode for the cart page.
