Problem: The client reported an issue where the product URL in English still showed parts in Finnish, despite being translated. Additionally, there were PHP warnings related to file access restrictions due to open_basedir settings on the server. Solution: 1. We initially attempted to debug the issue and requested a staging site or a duplicator copy from the client to safely investigate the problem further. https://wpml.org/fr/faq/provide-supporters-copy-site/ 2. After initial checks, we escalated the issue to our second-tier support for deeper investigation. 3. We suggested the client ask their hosting provider to disable the open_basedir restrictions in the PHP settings to see if that resolves the permalink translation issue.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing a 404 error when trying to view a product translated using WPML in Finnish. The issue arises even after translating the permalinks in WooCommerce Multilingual & Multicurrency. Solution: The 404 error is not directly related to WPML. If you disable WPML, you will notice that the same issue persists because you have used the same slug for your Product category base and Custom base in WordPress settings. This duplication causes conflicts within WordPress as it requires unique slugs for proper functionality. We recommend changing one of the slugs to ensure they are unique. You can adjust your permalink settings by visiting your WordPress dashboard and navigating to the permalink options at https://sh-teksor.fi/wp-admin/options-permalink.php.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, please check 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. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: You are trying to translate the Kadence Advanced Form (Adv) block using WPML, but the translations are not visible in the Advanced Translation Management (ATM) or among the strings. Solution: First, ensure that the issue is due to the compatibility of the Kadence Blocks with WPML by checking our errata page at https://wpml.org/errata/kadence-blocks-new-blocks-are-not-compatible-yet/. If the issue matches, follow these steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following XML configuration:
3. Click the Save button. 4. Edit the form and click the Update button. 5. Translate the form again. This should resolve the issue, allowing you to see and manage the translations in WPML.
If this solution does not apply to your case, or if it seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are encountering an error message related to the String Translation table on your site, specifically involving the 'wpml_string_table_ok_for_mo_import' key in the '_options' database table. Solution: First, delete the 'wpml_string_table_ok_for_mo_import' option from your database to hide the notice. Next, navigate to the WPML → Languages page. This action should automatically recreate the option. If your WPML tables are correct, this should resolve the message. However, if the error persists, it indicates that further database patching might be necessary. Please ensure to back up your database before making any changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to find 'Field Placeholder' texts in the Advanced Translation Editor (ATE) for a Kadence Form block, even after updating their XML file. Solution: We recommend removing any custom XML configurations for the Kadence Blocks, as we already maintain the default configurations which can be found here: WPML config for Kadence Blocks. After removing the custom config, edit the placeholder text directly in the form on the original content and then reopen the translation editor. This should allow the placeholder to be sent to the translation editor as an HTML attribute without any issues.
If the issue persists, we suggest checking the 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 problem still remains unresolved, please open a new support ticket at WPML support forum for further assistance.
