I use Dynamic Forms 2.7 to create some multilingual forms for our new homepage. I started with an easy task: the contact form.

The structure was made by the wizard, I translated the content into german (the main language of the page). After that I changed the settings of the "Form Localization" for english and french.

In section "Submit Link / Button" AND for each localization I choose "Use Submit Linkbutton". I entered the text (english: Submit, french: Suivant).

The result:
If I see the site in german everything looks fine. I get a link with the correct text.
In english and french I get 2 different submit links/buttons

In english: A link "Submit" and a HTML-Button "Submit"
In french: A link "Suivant" and a HTML-Button "Submit"

I already tried to change the settings for link / HTML-button / image-button, but nothing works. I still get 2 different submit links.

So, what's wrong here?

I'm experiencing the same issue... trying to use a different image for each language, though getting a link and a submit button instead.

If you know ascx or something we can change ourselves to solve this issue while we wait for a patch, .. would be great.

For some more input:

the real problem is we can't just say we won't use imagebuttons, because the linkbutton translation is acting weird as well.

I took a look at the database, and noticed this table:

"DynamicForms_FormLocalization" had a lot of the same records being entered for the same moduleID. Like when I changed the "continue" text for one language, about 10 records would change at once.

Also "UseSubmitButton" gets filled in a -1 sometimes, but this could be by design, of course. There's a lot of things happening, but without knowing how it should work, it's all just guesswork.

I would even change the values straight in the database (if there is a problem with the interface entering the values) if I knew what the data should look like.

This is really quite an issue for us, since ALL our dynamic forms suffer from this, since they all require localization and all need a submit button, or link.

I think it is an issue of the presentation and could not be solved by "hacking" into the database. In addition it is never a good idea to hack into a program.

Only workaround I found:
If you select "Use Submit Linkbutton" in the "Form Localization" you will get a proper localized link to submit the form. Behind the link there is also an additional HTML Submit-Button, but I think it is ok while there is a proper localized link.

Of course, it would be nice if it works correctly, but in my opinion it is not a critical issue. There are other known localization issues, which are still driving me crazy (@Chad: ).

Hey J.

Thanks for your reply.

Unfortunately, your workaround doesn't seem to work for me, as soon as I fill something in "form localization", the extra "submit" button appears for those languages. Even when selecting "Use Submit Linkbutton".

And "hacking" is a big word, was only looking . Having a background as database administrator always makes me very curious about the way tables & data is built up.

Yes, the extra submit button is always displayed for each foreign language. But there is a functional button or link with to right language at all. So one of the links / buttons fits the selected language

@Chad: Just a further bug report for your interest:
The "Submit / Save Javascript" of the form is missing for both links / buttons with foreign languages. It is only called if the form was displayed in the native language of the portal.

Hi guys... Just to confirm, this is only a problem on content localization if you are using the HTML Input Button for submission right? Not for the link button or image button? I have this on the list to review for the next release, the HTML Input Button was a new feature that was added and apparently it was not added to the localization area.

-Chad

I am using df 3.0 / DNN 5.01 and there is no "HTML Input Button" in "Localization Form". Is there a workaround?

Chris

After localizing the questions I had to remove p> 

in Source of each df question header and footer. to not have those additional lines breaking the form's layout.