Problem: The client is unable to see the translated strings on the frontend, even though they are translated in the WPML String Translation. The strings are related to admin texts (options saved in the database). Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation → Translate texts in admin screens. 2. Search for the option related to the plugin, which usually starts with 'wcrp_' or similar. 3. Select the relevant fields (labels) and add them for translation. 4. Return to the String Translation page and translate those strings. This process should ensure that the translated values appear on the frontend.
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 for further assistance.
Problem: The client was unable to see the date range translations for rental products on their WooCommerce site, despite other custom fields being translatable. Solution: We advised the client to ensure that the date range custom field was set to 'Copy' in the WPML settings. After setting it to 'Copy', the client needed to update the default language product and re-save it. This action should sync the data correctly across different language versions. If you're experiencing this issue, we recommend you try these steps: 1. Check if the date range custom field is set to 'Copy' in WPML settings. 2. Update the default language product. 3. Re-save the product to sync the data across translations.
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: If you're experiencing 404 errors on translated pages of your WooCommerce shop built with Elementor and using a rental product plugin, and issues with translated buttons and widgets not functioning correctly, this summary might help. Solution: Firstly, for the 'Rent a bike' button in the header that works in English but not in Dutch or Spanish, ensure that the header was created and translated using Elementor's dynamic links rather than manually adding URLs in the button settings. Manually added links can remain connected to the original language, leading to 404 errors on translated pages. For more information on using dynamic links in Elementor, visit Elementor Dynamic Links.
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 problems persist, please open a new support ticket with us for further assistance.
