This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Tagged: Exception
This topic contains 5 replies, has 0 voices.
Last updated by Mihai Apetrei 1 week, 1 day ago.
Assisted by: Mihai Apetrei.
Author | Posts |
---|---|
November 15, 2024 at 12:47 pm #16408471 | |
robertv-38 |
Background of the issue: Symptoms: Questions: |
November 15, 2024 at 1:09 pm #16408516 | |
Mihai Apetrei Supporter
Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00) |
Hi there, and thank you for reaching out. Certain strings may require a specific procedure to be located and translated. Moreover, the proper method for translating strings greatly depends on how they have been incorporated into the theme/plugin. IMPORTANT: Sometimes, there are even duplicates of the same string and only one of them is the correct one that needs to be translated. Also, sometimes, simply removing the string (checking the box and removing it) and then re-registering it again by scanning for it (one of the methods below) and re-translating it resolves the issue. Please attempt both methods and check if either of them resolves the issue. Method 1: Navigate to WPML > String Translation, and at the bottom of the page, you will find a checkbox labeled "Look for strings while pages are rendered." You can enable (check) that option, then go to the front end to a page where the string is displayed, and afterward return to WPML > String Translation to search for that string and see if it now appears. Method 2: If you can't locate them within WPML > String Translation, they might be included as admin text strings. This is the typical process for finding and translating admin text strings: Related documentation: PS: There is also something important to mention; if the strings come from outside of WordPress, it would be impossible for WPML to see or translate them. Please keep us informed about your progress. Mihai Apetrei |
November 19, 2024 at 6:42 pm #16421094 | |
robertv-38 |
Dear Mihai, Thank you for your help. 1. The home page its first sentence is displayed correctly in the translation section but appears half English, half Dutch in live mode. ''Out liefde for het love'' instead of ''Out of love for the dearest'' 2. My privacy policy page does not initially show in English when browsing the site in English mode. Thanks again. |
November 19, 2024 at 11:10 pm #16421888 | |
Mihai Apetrei Supporter
Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00) |
Hi there and welcome back. Can you please let me know if the issue mentioned initially in the ticket was resolved (the ones with the buttons)? Also, regarding the other issues you mentioned, please note that, per our Support Policy, we can handle only one issue/topic per ticket. Continuing with one issue per ticket helps supporters focus on one problem at once and enables other users to find solutions to their questions faster. If the button-related issue is fixed, can you please mark this ticket as resolved and open a new ticket for any new issue you encounter (one ticket per issue) so we can properly focus on and tackle each one? Thank you very much for your understanding and cooperation. Mihai |
November 20, 2024 at 6:38 am #16422257 | |
robertv-38 |
Dear Mihai, I followed the steps, but still I can't seem to find certain strings: 1. I enabled checkbox labeled "Look for strings while pages are rendered." then went to the front end to a page where the string is displayed, and afterward returned to WPML > String Translation to search for that string and see if it now appeared That didn't work for me so after I followed method 2. Method 2: Finding and translating admin text strings. Also that didn't work for me. I inspected a button at a page of the string I couldn't find (the buttons at my homepage suddenly seem to be translated now) as shown at the attachment. But it doesn't show up at WPML > String Translation. |
November 20, 2024 at 11:13 pm #16426769 | |
Mihai Apetrei Supporter
Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00) |
Thank you for the update. After reviewing the screenshot you attached in your last reply, I cannot determine which page builder the page is using. It doesn’t appear to be a popular one, like Elementor. This suggests that the page builder —either enabled by a custom plugin or through the current theme— might not be fully compatible with WPML (or might need a specific approach to help WPML see those blocks). Sometimes, plugins or themes use specific blocks that WPML does not recognize right away. I’m not sure if the theme includes the page builder or if you are using a specific plugin to enable it. Please reach out to the support team for that product and ask if it is compatible with WPML. They might offer a quick solution that allows WPML to recognize those specific buttons. Each section on the page is a block, and you may need to register these custom blocks first, as shown in this example: https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/. Let me know if you get any information from the support team regarding the plugin or theme that enables this page builder. I look forward to your response. |