Problem: After migrating a site from a staging server to a live domain, there are character encoding issues indicated by garbled text like “БългарѸÑкД. The client is concerned about whether they need to re-register the WPML site key and if they will lose previously translated data. Solution: The issue likely stems from the database tables or their columns not using a UTF-8 compatible collation. We recommend setting your database tables and columns to:
utf8mb4_unicode_520_ci
or another utf8mb4 collation supported by your hosting environment. For more details, visit WPML Minimum Requirements. If you are unsure how to adjust this, please contact your hosting provider to update the database collation safely.
This solution might be irrelevant if it's 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.
Problem: The client is unable to translate a section of their website, specifically a custom post type such as 'Portfolio' or 'past events', because the edit translation icon/page is not available. Solution: If you're experiencing this issue, it may be because the custom post type is not set as translatable. We recommend enabling translation for it. Please follow the guide on how to do this here: Translating Custom Posts. Additionally, we have enabled debug information for this support ticket. You can follow the instructions to retrieve and share it with us here: Provide Debug Information.
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 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 at WPML Support Forum.
Problem: The client reported that some footer text and other content are not appearing translated on the front end, despite being translated in the backend using the Herrington theme and Elementor.
Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML -> Translation Dashboard. 2. In the Other texts (Strings) section, search for the specific untranslated phrases or words. 3. If the footer is an Elementor template, check in the Templates or Template Parts sections within the Translation Dashboard. 4. Ensure these texts are sent for translation or that their existing translations are updated.
If the issue persists after these steps: 1. Go to WPML -> Theme and plugins localization. 2. Under Strings in the themes, select the Herrington theme and click Scan the theme for strings. 3. Under Strings in the plugins, select Elementor and any other relevant plugins, then click Scan the selected plugins for strings. 4. After scanning, navigate to WPML -> String Translation. 5. Search for the untranslated footer text or other phrases still visible on the site. 6. Translate any new strings found into the desired language.
If these solutions do not resolve the issue, it may be due to WPML configuration conflicts, cache issues, or a need for further troubleshooting. 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where the 'Join Us' button in the header is not translated into Portuguese despite being translated in the backend and in Elementor, or if your Member Directory page links are not visible in the Portuguese version and clicking on logos results in a 404 error page, here's what we recommend. Solution: For the 'Join Us' button translation issue, please ensure that your translations are correctly configured in both the backend and Elementor. If the issue persists, we might need to access your site to further investigate the configuration. Make sure you have a full backup of your site before proceeding. For the Member Directory page issue, the problem might be related to the shortcode used:
. This shortcode might not be filtering content by the current language in the frontend. We recommend contacting the authors of the shortcode to check the query behind it, particularly the suppress_filter attribute.
Please note that the solution provided 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.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
