This thread is resolved. Here is a description of the problem and solution.
Problem: The client was trying to use the 'Translate Everything Automatically' feature in WPML for string translation but encountered an issue where English strings were not being translated automatically on their Dutch website.
Solution: We explained that in 'Translate Everything Automatically' mode, strings that are not in the site's default language will not be automatically translated. Since English is not the default language of the client's site, those strings need to be translated manually. This behavior is expected based on WPML's settings.
Regarding the specific translation issue with the string "Wanneer?", we suggested that it might be related to custom code in the client's Child Theme. We recommended reaching out to the Theme's Author for further assistance if the client wishes to have that text remain untranslated.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related 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 with us.
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.
Thank you for getting in touch with us. I've checked your debug information and noticed that you use the WP-Optimize plugin. Can you please try emptying all your caches to see if the content shows up translated?
About the API, if you can see the pages, it's likely that it's a false negative.
Please click on the gear icon and resave the translations. You can add a small blank space at the end of the translation so WPML recognizes that it has to save it again.
Let's see if that solves it.
One important thing to notice, is that every content that belongs to a page/post should be translated using the translation editor (you can translate the content of posts and pages in the corresponding WordPress section for that). The String Translation feature is intended to translate content that doesn't belong to a specific post (like widgets, admin texts and so on).
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to a testing site where the issue is replicated.
You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this:
I took a look at your development website and noticed that the strings in question belong to your custom-made theme, the "kfi" domain.
What I can advise you to do, is to delete the strings in question, by selecting their checkboxes and clicking on "Delete selected strings". Once that's done, rescan your theme and try translating the strings again.
It might be possible, that these strings weren't properly registered for translation. If deleting and re-translating doesn not work, I recommend you get in touch with your theme developer, so he can assure if the strings are properly translatable and offer a workaround in case they're not.
Where is the string of which you sent me the screenshot being used?
Hi there,
I removed the strings and added them again. But it still does not work. The strings do translate manually, but not automatically.
I do not think it is the theme, because we we have used a lot in combination with WPML with no problem.
You can test with: <?php esc_html_e('When?', 'kfi'); ?> (also see screenshot). This is on the homepage. At the moment a translation is still being printed (Wanneer?). Although I cleared the kfi domain.
And if you try to translate other domains (eg "motopress-hotel-booking") it also does not work.
It's possible that this issue is being caused by a 3rd party plugin. To check that, I'd like to debug your website locally, with a copy.
Unfortunately, I wasn't able to make a copy of your website (probably due to security restrictions on your server). Please provide me with a duplicator package, so I can analyze it locally. Refer to our documentation:
I'll have to escalate your ticket to our development team. It appears that the custom theme you are using is causing problems, since it's incompatible with WPML.
Before I escalate, can you tell me exactly where to find the 2 strings in the front end you mentioned in your first message? The "Next" and "dogfriendly-holiday-home" ones. I mean, where they appear on the website.
This way, I can make sure that issue will be understood and facilitate it for our developers.
Hi Lucas, we have used this theme already for several websites with WPML and never had any issues with it.
The mentioned strings were just an example. All strings are not translating automatically. For ease of debugging you can use the When? string on the homepage and the Guests string on the homepage.
In "Translate Everything Automatically" mode, strings not in your site's default language won't auto-translate. For your site, English strings need manual translation because English isn't the default language. This is expected with WPML settings. I'm sorry I haven't noticed that earlier.
Regarding the "Wanneer?" translation issue, it may stem from custom code in your Child Theme. I've checked and updated the translation locally; it now excludes properly after deletion. The issue likely originates from the theme itself. I recommend you get in touch with your Theme's Author, in case you wish to have that text untranslated.
