I do not know why these fields are locked, is that lock not set by WPML? What does it mean anyway?
Unlocking seems to be as simple as clicking on the 'lock' icon.
Not all the untranslated fields are strings that belong to the currently locked ones.
As for the footer: as I mentioned earlier, the language-flags in the builder refer to building a different layout for footers in different languages. When not used, the default footer should be displayed. That has worked so on other websites when using WPML, if I remember correctly.
Thanks for your patience. Could you please check your server's PHP limit? I tried to update the WPML plugin to the latest version before escalating the report that I've prepared, but I'm getting "Het geüploade bestand overschreed het upload_max_filesize commando in php.ini." as shown in the attached screenshot.
Thanks for your patience. I’ve received feedback from our 2nd Tier Support, and this is what they found.
The footer uses template ID 156. It has been translated into IDs 3638 and 3636, but the translated versions contain different content.
The best and least disruptive approach would be to duplicate the template with ID 156. The key elements that need to be duplicated are post_content and the post meta _cs_generated_tss. This can be done with a simple database edit.
If you prefer to continue using the original template (ID 156), the translated templates will need to be removed. This can also be done via a database edit by deleting posts 3636 and 3638 from the wp_posts, wp_postmeta, and wp_icl_translations tables.
Since you'd like to only use the primary language footer template for all languages, as mentioned earlier in the ticket, your option would be to remove the translated footer template.
If you would like me to perform the edits for you, please backup everything and share access to your server PHPmyadmin.
I've just placed a fresh copy of the staging environment. I did a quick search on those ID's and they are present in more tables then the three mentioned. Should they also be removed in other DB tables?
I'm not an expert on SQL: is there a single commando that performs deletion of both ID's from all relevant tables? I'm happy to run that.
After that, what do we need to do to translate the strings of the footer?
Thanks for your reply. You’ll need to remove posts 3636 and 3638 from the following three tables: `wp_posts`, `wp_postmeta`, and `wp_icl_translations`.
You can backup and run the queries below in phpMyAdmin to locate the records and then delete them manually from the tables:
-- wp_posts
SELECT *
FROM wp_posts
WHERE ID IN (3636, 3638);
-- wp_postmeta
SELECT *
FROM wp_postmeta
WHERE post_id IN (3636, 3638);
-- wp_icl_translations
SELECT *
FROM wp_icl_translations
WHERE element_id IN (3636, 3638);
After making these changes, please let me know if all languages are now displaying the same primary-language footer template. Once confirmed, I’ll guide you on how to translate the footer template content correctly.
Thanks Kor, that saved my a lot of time. I've executed all three queries.
There is a footer showing now, so that's progress!
The only thing left is to correctly translate the strings used in that footer, and to implement this on the live website as well. How can we make sure to identify the correct DB-entries on the Live website to delete?
Thanks for your reply. I need to double-check whether the footer template is using the same post ID on your live site. Could you please back up your production site and share access with me? I’ll also need your permission to install the phpMyAdmin plugin so I can verify the post ID.
Once the fix is applied on the live site, we can then check and confirm how to translate the footer template content correctly.
Additionally, the credentials for your staging site no longer work on the other resolved ticket. It would be helpful if you could reset and share the updated credentials as well.
Thanks for your reply. I've checked your footer template, and it's displaying Widgets. Have you tried translating the widgets using String Translation as shown in the attached screenshot?
Also, it looks like the cornerstone templates cannot be translated using the WPML's Translation Editor, as explained here hidden link .
Hi,
Let's take one step back: have you been able to identify the correct SQL Statements to perform on the live website? The footer is still invisible there.
Once we have the footer visible again on the live website, I'll definitely check if the widgets of the footer have been translated!
On the Cornerstone Templates we have another support topic, so I've responded to your remark in that topic, and You have referred to 2nd tier already.
Thanks for getting back to me. To identify the correct SQL statements, I’ll need access to the live site. Could you please back it up and share access with me?
As for the Cornerstone template translation via String Translation, I’m testing a possible workaround now and will follow up with you in your other ticket.
Thanks for your reply. Yes, once the language flags in ThemeCo’s builder are clicked, a separate template is automatically created for that language. These templates need to be removed from the database so the same footer template can be used across all languages on your translated pages and posts.
Thanks for clarifying that a new post is created when the language switcher is clicked.
I added a simple text (DELETETHISFOOTER) to the translated footers, through the editor, and searched for that text through phpMyAdmin.
I deleted these post from the database tables posts, icl_languages_translations, postmeta.
