Footer template is not showing on translated page

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with locked fields in WPML and has concerns about the translation of the footer, which does not display correctly across different language versions of the site.
Solution:
We clarified that the locked fields can be unlocked simply by clicking on the 'lock' icon. Regarding the footer, it appears that the client had previously attempted to fix the issue by deleting the translated footer template directly from the database. However, this did not resolve the problem as the footer still does not appear correctly. We suggested that the footer's translation issue might be due to the limitations described in the WPML errata for the Pro theme, where layout texts are not translatable via the WPML Translation Editor (https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/).
The client can either manually translate the template or apply custom code to make it compatible with String Translation. We asked the client to confirm if they intend to use String Translation for the footer in the same way as the “Object (CPT) – Single View” template.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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 at WPML support forum.

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.

This topic is split from https://wpml.org/forums/topic/some-sections-are-still-not-translated/

Tagged: Bug, Known issue

This topic contains 29 replies, has 0 voices.

Last updated by dennisH-9 2 months, 3 weeks ago.

Assisted by: Kor.

Author	Posts
February 2, 2026 at 7:41 pm #17785138
dennisH-9	I'm going to mark this issue as resolved now, but I'm glad you're just as enthusiastic about all the work we have done together and the changes that are coming! One last practical thing tough: perhaps it's a good idea to update the support pages regarding ThemeCo's themes integration and urge the developers to keep in close contact, so the documentation is updated once the new software is released. One thing is for sure tough: ThemeCo is going the end the usage of their translating inside their editor, the flags in the right corner that got as both as they seem to create new posts. Just to reduce further support questions, I would like to suggest to remove that option from all documentation. May save you some time 😉 Once again, thanks a lot and keep doing such an incredible customer support job and be an inspiration for your colleagues!

Author

Posts

February 2, 2026 at 7:41 pm #17785138

dennisH-9

I'm going to mark this issue as resolved now, but I'm glad you're just as enthusiastic about all the work we have done together and the changes that are coming!

One last practical thing tough: perhaps it's a good idea to update the support pages regarding ThemeCo's themes integration and urge the developers to keep in close contact, so the documentation is updated once the new software is released.
One thing is for sure tough: ThemeCo is going the end the usage of their translating inside their editor, the flags in the right corner that got as both as they seem to create new posts. Just to reduce further support questions, I would like to suggest to remove that option from all documentation. May save you some time 😉

Once again, thanks a lot and keep doing such an incredible customer support job and be an inspiration for your colleagues!