Problem:
Unable to review translation of custom post type posts.
Solution:
We enabled error reporting and the theme was generating fatal error on reviewing Gallery post type posts. The client don't want to translate the Gallery post type posts, so he set them to not translatable.
Problem: The client needed assistance with two issues: translating the filter labels 'All', 'Room', and 'Rooms' on the homepage and archive pages, and changing the Cyrillic translations to Latin for the Serbian language on the Cart and Checkout pages in WooCommerce.
Solution: 1) To translate 'All', 'Room', and 'Rooms': - Go to WPML > String Translation. - For 'All', type 'All' in the search box, select "Exact match", and click the "Search" button. Translate the string found under the "augustine-core" domain by clicking the "+" icon under the language flags. - For 'Room' and 'Rooms', type '%s Room' in the search box and press the "Search" button. Translate the strings under the 'augustine-core' text domain using the same method.
2) To translate WooCommerce strings on the Cart and Checkout pages to Latin for the Serbian language: - Go to WPML > Theme and Plugins Localization. - Select the "WooCommerce" plugin and scan it for strings. - Once the scan is complete, navigate to WPML > String Translation. - Input the text you wish to translate in the search box, using English as the source language. For example, type "Product" instead of "Производ". - If the string is under the 'woocommerce' text domain, add a translation for the Serbian language by clicking on the "+" icon below the Serbian flag.
Please note that the solution provided might be outdated or not applicable to your case. If the steps above do not resolve your issue, 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 you still need assistance, please open a new support ticket.
Problem: The client has translated ACF fields for a custom post type 'accommodaties' but the translations are not showing on the English version of the site.
Solution: We recommend the following steps to resolve the issue: 1. Open the
, around line 142, replace the code snippet with the provided workaround that includes WPML filters for registering and translating strings. 3. Open the
, around line 339, replace the code snippet with the provided workaround similar to step 2. 5. Visit the page with the facets in the original language to register the strings. 6. Go to WPML > String Translation and translate the strings.
Before making these changes, ensure to back up your database. Additionally, if the default language on the website is Dutch and the strings are registered in English, the language of the string may need to be changed to Dutch before translating. For guidance on changing the source language of strings, refer to the documentation.
Please note that this solution 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 needed, do not hesitate to open a new support ticket for further assistance.
Problem: If you're experiencing an issue where the overlay menu for the second language is not visible on the mobile version of your site, while it works correctly for the primary language, the problem may be related to the theme you are using.
Solution: First, ensure that your theme is compatible with WPML. You can check the theme's certification status on the WPML's list of compatible themes.
If the theme is not certified, you might encounter issues with multilingual functionality. In the theme file
, the theme author uses a custom function to display the navigation menu. We recommend replacing this custom function with the standard WordPress function
wp_nav_menu()
to ensure compatibility with WPML. Here is an example of how you can adjust the code:
Please note that custom code assistance is beyond the scope of WPML support. If you need help with custom code, consider contacting one of our certified partners.
Keep in mind that the theme's last update was in 2017, which is quite outdated. We recommend using a theme from the list of compatible themes to ensure proper content translation on your site.
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 on the WPML Known Issues page, 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.
Problem: The client reported that URLs set in any anchor tag were being manipulated by WPML, as evidenced by different values in a hidden input field and an anchor tag. Solution: We recommended the client to set the pages to "Translatable - only show translated items" in WPML > Settings > Post Type translation to see if this resolves the issue.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 through the WPML support forum.
Problem: The client was experiencing an issue where the subscribe form worked in Bulgarian but not in English. In the English version, the successful subscription message did not appear, and a 500 error was present in the console on the feedback file. Solution: We recommended the client to first create a backup of their site and database. Then, we suggested deactivating the "Bravis Addons" plugin and switching to a different WordPress theme to see if the problem persists. If the subscribe form worked after these steps, we advised reactivating the plugin and switching back to the original theme to check if the form continued to work. If the issue remained, we suggested deactivating the plugin again, switching to a standard WordPress theme, adding the subscribe form shortcode to a new page, and translating that page.
Please note that this solution might not be relevant to your case, as it could be outdated or not applicable to your specific situation. If you're experiencing a similar issue and the provided solution does not help, we highly recommend checking 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 with us.
Problem: The client reported an issue with the translation of a cart update notice and its link on a WooCommerce product page. This problem occurred when visiting an English version product page for the first time and using the "Login/Signup Popup" plugin to log in. The notice and link remained in German on the first visit but worked correctly on subsequent visits.
Solution: We identified that the issue might be related to caching, as it does not occur when using the WooCommerce login page directly. Since the "Login/Signup Popup" plugin is not listed in our compatible plugins directory, we recommended that the client contact the plugin author and suggest they join our Go Global program to ensure compatibility with WPML. Alternatively, the client can use the WooCommerce login page to avoid this issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 with us.
