Background of the issue:
I have been using WPML to translate my site, but the header won't translate or finish translating. I have tried deleting and creating a new header, switching to manual translation, turning off 'I prefer bigger segments', and using an older version of the translator. This allowed me to reach 100% completion, but saving still causes the translation to refresh. Link to a page where the issue can be seen: hidden link
Symptoms:
The header won't finish translating, and the translation icon keeps 'refreshing'. When I save, the translation refreshes, and when you click on English, the header disappears.
Questions:
Why won't the header finish translating?
Why does the translation icon keep refreshing?
Why does the header disappear when switching to English?
Could you please increase the WordPress memory limit (WP Memory Limit) to at least 256 MB? WPML requires at least 128M.
Your current values are:
PHP MemoryLimit 512M
WP Memory Limit 40M
You need to connect to your website's server and open the wp-config.php file in a text editor. The file is located in the WordPress root directory.
Add this code to the wp-config.php file to increase WordPress memory:
define ('WP_MEMORY_LIMIT', '256M');
Add this just before this comment:
// That's all, stop editing! Happy blogging.
The current values can be viewed under WPML > Support > WordPress.
These settings can be restricted directly by your hosting provider. Therefore, I recommend contacting them and asking them to change them directly if the changes are not applied immediately.
Now, please try to translate the template again. If this will not solve the issue, please let me know.
I have increased the WP memory limit to 256m, but it still won't stop translating - After I manually translate it - it refreshes at gives this message: English: Waiting for automatic translation
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
This would mean that you are using the translation mode "Translate Everything Automatically". Do you see any progress at WPML > Translation Management > Dashboard?
In case not, I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I am writing to you to let you know that I took a local copy of your site, but the migration process seems to not have been fully successful. The site is far from functioning as expected and I need more time for testing.
I was further not yet able to confirm the issue on a new install.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I realized the following issue on the button:
Få rådgivning <Span class="bold">86 62 18 88</span>
This is non-valid markup. Replace it with:
Få rådgivning <span class="bold">86 62 18 88</span>
Anyhow, this did not solve the issue.
The translation seem to only get completed if I remove the Search Widget from the Header.
Possible Workaround:
- Remove the Search widget from the header
Take note, that this issue also could occur when using a Elementor Form Widget.
I will need to run further tests on a new test site try to recreate this issue. The issue occurs on a copy of your site while testing only with Elementor PRO and WPML on the Twenty Twenty One Theme.
