We’ve used Freeform Pro 4.0.11 / EE 2.7.3 / Publisher 1.3.2 to generate forms using the composer. As we need localized labels we used the publisher tag {phrases: phrase_language} as the label field in Freeform fields (cp).

These label fields were then nicely translated (rendered) on the final template.

However since upgrading to 4.2.2 (and EE tot 2.9.3. and Publisher 1.6.2) these translations don’t work anymore. The final template shows the tag {phrases: phrase_language} instead of the rendered label.

Below is the response from Solspace, however none of the suggestions seem to work (except rebuilding 10+ forms).

Are these issue known to you and do you have any suggestions?

————————————————————————————————————————————————————————————

Sorry for the delay as I had to check with our devs, which confirmed what I thought: EE 2.9.x has made a number of changes to its parsing engine, which is very likely explaining your situation. Using variables/tags in field labels isn’t something that is documented in Freeform, but it seems this was working for you up to now. Although we have no experience with Publisher, our hypothesis is that EE template parsing changes is affecting how parsing is behaving in this case, when EE, Freeform and Publisher are combined for your purposes.

Again, it’s difficult to say how/when Publisher tags are parsed. I had a quick look at the Publisher documentation (https://boldminded.com/add-ons/publisher/phrases), and they mention that {phrase:[phrase_short_name]} is early parsed. EE must have changed something so that this isn’t parsing when it should, or how it used to.

Although we can’t test this since we’re not familiar with Publisher, perhaps using a custom Composer Template might be a workaround. In a custom Composer Template, you should have {composer:field_label} available. This parses to the field’s label. Instead of having the label use “{phrase:my_phrase}”, maybe (maybe, since I can’t test this) use “my_phrase” for the label, and in the Composer Template use {phrase:{composer:field_label}}. This *might* put parsing in the right order: hopefully {composer:field_label} parses first, making “{phrase:my_phrase}”, which Publisher then parses to the phrase.

Another option would be to use {exp:freeform:form} instead, or use {exp:freeform:composer} as a tag pair, which contains Composer code: this is similar to making your own code in the CP in the “Composer Templates” section.