Problem: The client was unable to translate the "button hover texts" on the header's layouts despite trying all recommendations found on the forum and using Ai agents. Solution: We added a custom XML configuration to enable the translation of the buttons/hover buttons. We advised the client to go to the translation management page, click on the "refresh" icon, and update the translations. After updating, we recommended checking the front-end to ensure the translations were applied correctly.
If this solution does not resolve your issue, or if it seems 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that the workaround for translating the 'All' filters and 'More..' buttons was lost after updating the translation. They were unable to find these elements in the translation editor. Solution: We recommended translating the 'All' texts through the WPML String Translation page. For the 'More..' button, we provided a custom XML configuration to ensure it is translatable. Here is the XML code you need to add:
If this solution does not resolve your issue, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: You are using a custom block with a video on your WordPress site, but the source is missing from the translation. You expected to see the video with the source included, but instead, the video appears without the source in the translated version. Solution: If you're experiencing this issue with custom Gutenberg blocks, you need to ensure they are properly registered to be translatable. You can find detailed instructions on how to make your custom Gutenberg blocks translatable here.
Please note that the creation and maintenance of custom code falls outside our support scope. For implementing custom solutions, you can refer to our documentation for developers.
If the issue is specific to one or a few pages, we recommend creating the translations manually using the WordPress Editor. Simply activate the option for the page as explained here.
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. If you still need assistance, please open a new support ticket.
Problem: You are trying to display a data table on a translated page, but it is not visible due to the URL translation affecting content filtering. Solution: We recommend ensuring that your table setup adheres to WPML's guidelines for handling multilingual data. Please review our detailed documentation for developers, which can help you configure your data tables correctly:
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. If issues persist, please open a new support ticket.
Problem: The client was unable to access the Translation Tools tab in the WPML plugin to retrieve the migration code for a staging site. This issue was compounded by a connection error message advising to check the internet connection.
Solution: 1. Ensure that the WPML plugin is properly registered: - Visit https://wpml.org/account/websites/ - Delete the existing site URL if already registered and re-enter it to generate a new site key. - Copy the new key and enter it under Plugins > Install > Commercial to re-register WPML.
2. Enable the Advanced Translation Editor: - Go to WPML > Settings and select "Advanced Translation Editor". - Fill out the necessary settings in WPML > Settings > AI Translation, including context, target audience, and post-translation actions. - Complete the Setup Wizard in WooCommerce > WPML Multilingual & Multicurrency for WooCommerce.
3. If issues persist, particularly with accessing the Translation Tools tab, check for conflicts with other plugins or themes, particularly those that might affect JavaScript operations or the WP REST API. Disabling conflicting plugins or switching to a parent theme may resolve the issue.
If these steps do not resolve your issue, or if the solution 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate multiple shortcodes containing ids to another string for the translated version on your site. You have added them to the custom XML config, but the Advanced Translation Editor (ATE) only picks up the changed strings, not the shortcode id. The specific shortcodes involved are for ws_form and mwai_chatbot. Solution: We have reviewed your issue and found that the values for these shortcodes only appear when being directly searched for within ATE. By searching for them in ATE, you can manually add the value and thus translate it.
Please note that this solution might be 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 the issue persists, please open a new support ticket.
