In the genaral settings, in the group "layout" you can define the loop that creates the fields.

There, you can add place holders {HELP} or {HELPTXT}. Those are also discussed in the section "help users" of the documentation. When the form is rendered, these place holders are replaced by the content of the "help" box for each field.

It looks as if you have the literal text "help for" in your field loop, or you have {HELPTXT} in the loop and for each field your help consists of these two words.

Is this an up-to date version of mpform? prior to 1.1.10 I think there was a bug in this area...

In the genaral settings, in the group "layout" you can define the loop that creates the fields.

There, you can add place holders {HELP} or {HELPTXT}. Those are also discussed in the section "help users" of the documentation. When the form is rendered, these place holders are replaced by the content of the "help" box for each field.

It looks as if you have the literal text "help for" in your field loop, or you have {HELPTXT} in the loop and for each field your help consists of these two words.

Is this an up-to date version of mpform? prior to 1.1.10 I think there was a bug in this area...

Thank you! This was correct, the "help for" text was typed in on the Layout section. I just upgraded to the latest version 1.3.21 from an older version thinking that it might sort this but it didn't do anything.

I had recently updated to WB 2.11.0 from 2.10. and I think the problem started after this update.

I had recently updated to WB 2.11.0 from 2.10. and I think the problem started after this update.

the text "help for" actually comes from the language file of WebsiteBaker. By default, the place holder "{HELP}" should have been in the template for the field loop.

One would have to check the upgrade script of WB if it does some global replacements in the database during update. I know there have been a few changes in the area of the language files, so it's not completely impossible that the upgrade has messed this up. But to be sure, one would have to inspect the upgrade script in detail.

mpForm prior to 1.3.9 did contain this string in the language files, but that string was used nowhere (maybe it was in the past, but at least last year it was not used anymore).

However, in WB 2.10 the way how language variables were loaded and how replacements are performed in the templates has changed, and at this point a definition of a translation entry $LANG['backend']['HELP'] started to cause problems when a placeholder '{HELP}' was used. In earlier versions values were replaced only once, but starting with 2.10 in the resulting string another round of replacements is performed.

So, if you have - upgraded to WB 2.10 or newer - and you did not upgrade mpform to 1.3.9 or newer in this course- and you have modified the general settings in some way, or at least saved them againthen, the place holder '{HELP}' inside the field loop was replaced by mistake

Sorry, I was on the wrong path when I wrote that the string would come from the global WB language file because the problematic entry wasn't there anymore, and mpform uses $MENU['HELP'] in some places.