[Resolved] Layouts items not showing up in String translation (in WPML)

[Author]

Posts

[Nigel]

Garen

I'm closing soon until next week, so I'm assigning this ticket to Beda so that he can interact with you directly once he has deployed your site and done some testing.

[Beda]

The issue is that the things you translated for Layouts, where translated as strings in WPML String Translation while they should have been translated in WPML Translation Management, see this DOC:
https://toolset.com/documentation/translating-sites-built-with-toolset/translating-layouts/

I see that you have already a ticket open for this in WPML Forum:
https://wpml.org/forums/topic/layouts-translations/

It alls starts from the wrong approach of using String Translation for those contents, which should in fact never happen when translating Layouts with settings as you do have on the site.

Now, the only workaround I got so far and confirmed from WPML is “you will have to translate them again” but there may be a workaround which I am trying now.
Please stand by so I can update you with the results.

[garenM]

Thanks Beta, but for translate them again is not a solution, are 7 languages and the site are very big. Can you tell me what version of plugin can i upload so it will showing the string translation

[Beda]

Ok, I deeply analyzed the issue here and I cannot determine any issue in Layouts.
The issue seems in WPML whereas the strings are in fact translated on the front end but do not figure as such in the backend neither where expected (Translation Management) nor in the unexpected place (String Translation).

While I suggest to close either of these tickets you have opened, and suggest you follow up with WPML support, because this is a WPML issue as it looks, I will directly escalate this to our 2nd Tier and make tests with older WPML versions to see if that worked fine, so maybe we can restore the translations on your end somehow, which on my local tests was not only not possible but additionally, if re-translated, it broke the entire site.

This is because you sent HTML and ShortCode for translation while you'd have only to use [wpml-string] shortcode wrapping the very limited amount of Strings you have in the layouts, as you do not want to translate ShorCodes or HTML.
Then, those would be found in String Translation, however, for that it is too late at this point.

I will feedback to you asap with findings, but I already can foresee that this will not be resolved overnight, unfortunately it looks like a problem in WPML that has no solution as of yet.

I will prioritize this as much I can.

Thank you for your patience and understanding

[garenM]

Thank you for your time

[Beda]

I did not yet determine if this works in older WPML versions, and using String Translations for this kind of translation is the wrong approach, since this system exist.
Hence it would be the wrong thing to do to resolve this by continuing the translation like this.

I understand the amount of translations you have is not something you can recreate and I will do everything to find the solution - inclusive tomorrow I will quickly test older versions to see if at least a rollback could resolve the issue for current editing, but, as said, that would then not solve future updates issues.

I will keep you in the loop.

[garenM]

Hey, any update?

[garenM]

if this is not fixing today we have to add a previous version on it because we need to update a lot of translations

[Nigel]

Beda doesn't work Monday's, but he has a colleague looking at this. The first task is to see if we can find/confirm an older version of WPML where this works, making that an option for you.

I haven't seen any progress on the internal ticket yet, but if I do I will let you know.

[Beda]

There is no progress on this yet. I did what I could before I went to my weekend and passed the issue to my colleagues, and since there where no news I am looking into it with priority again
(see my working hours here https://toolset.com/forums/users/beda-s/)

Regarding a fix, meaning a proper fix of a possible bug that allows you to adjust the problem with a patch or update, please do not expect this to happen as soon as overnight.
It will require time, for the developers, to debug and adjust this unknown error in the code, then prepare either a patch or an update.

I will prioritize my testing about finding a working version mix, for which I have no promise but I will do my best so to update you today.

I apologize that this is disappointing, I do understand that and want to offer you a way to have your voice heard without the need of posting it publicly or to technical support but directly to Support and product Management:
https://toolset.com/need-help-toolset/

I will be back here ASAP with news.

[Beda]

Here is the official erratum for this issue which you can now follow:
https://wpml.org/errata/translating-layout-with-wpml/

[garenM]

Thanks a lot Beta for the solutions

[Beda]

You are welcome, and I extend again our apologies for this problem

Our developers are working on it and I will update you here once a solution is provided.

Meanwhile I escalate the ticket back to "Escalated to 2nd Tier" so it can be tracked by myself.

Thanks!

[Beda]

This will be fixed in String Translation version 3.0.5

There is one caveat:
You will have to edit each of the Layouts translations in WPML > Translation Management, and send each to translation, and translate each (but there, you will see the translations you have Made already will actually appear).
All you will need to do, is check the "Translation done" checkbox below each of the translation areas, and save.

That will require a little organizational work from your end but there will be no beed to re-do the actual translations.

Thank you for your patience and I will update you here once String Translation 3.0.5 is released.

[garenM]

Thank you for your update