Ronaldt

Same here, disabled the premium to temp fix the problem. Awaiting the Premium update.

Thanks @wpmudevsupport13

That worked, thanks.

We will fix it like that for now in the hope that it will be fixed somewhat soon-ish. Thanks @wpmudevsupport11

Hi @sterndata, thank you for that reminder.

Yes, I do realise that. I’ve had contact with Forminator before and know I should get an ATTN invite to a specific contact person before random support-questions are picked up on their general contact form. That’s why I asked for an “invite” to continue the conversation through that channel and not here on the WP support forums, so that more sensitive information can be shared between them and me, not the world.

What I do not like is that my last post here has been completely removed, I take it by you? It had some information I would like to share with the supporters of the plugin. Per e-mail I even got a reply from one of the plugin supporters that I could contact them and ATTN his name (what I was looking for in my post).
So thank you for keeping these forums safe, but please don’t do it though completely removing entire posts.

Hi @wpmudevsupport11,

Sorry, I see our client had replaced the default address field to a couple manual input fields just before I exported the form to combat the situation… #confusing

I have now created a simplified form that might be easier to test it:

https://res.cloudinary.com/comsi-rtv/raw/upload/v1637655230/wpmudev/export-form-german-v2.json

When submitting the form this is the output per mail:

Those address fields should be translated and show the same translated labels that are on the frontpage.

Kind regards,
Ronald

Hi @wpmudevsupport12,

Thank you for quick response and leaving the topic open, sorry for my late reaction.

In the WordPress ??Settings the default language of the website is set to Dutch (managed through WPML).
Via WPML our client is working on translating it into English and German. It is basically a complete new form, but unlike other CPT’s we can’t set the language for a specific form. While the frontend is shown correctly, after submit I guess the form does not know what language it should set the address field to.

Can you confirm?
https://res.cloudinary.com/comsi-rtv/raw/upload/v1637248350/wpmudev/export-form-german.json

I checked the translations in the link you sent, but in that there are no translatable options for:

• Street Address
• Address Line 2
• City
• Country

The other fields fall back to the name of the label which are actually in German, so no problem there.

I can ask our client to (for now) use the macros as a work-around. Thanks for that tip. There will be a couple more forms per language though, and some of them will have quite a number for fields. So while this works for this form, it would be much appreciated if the problem could get fixed in the plugin.

Cheers,
Ronald

That works, simple fix until this plugin will be updated (if ever).

Hi @wpmudevsupport12

I’ve been in contact with @wpmudev-support9 last week, got to try out a beta of the next release but that didn’t help unfortunately.

There are a couple plugins that call that wp_cache_delete hook. Here’s a list of all the plugins (search in /wp-content/):
https://res.cloudinary.com/comsi-rtv/raw/upload/v1632122462/wpmudev/grep-clear-cache.txt

Please note that the MainWP plugin (external maintenance plugin we use to manage all our client website themes/plugins) calls it too, but we’ve been very careful to not trigger an update via MainWP on this website.

Cheers,
Ronald

Thanks @wpmudev-support9

I’ve set up the debug logs just now and will wait a bit until that populates a bit. I expect to use the contact form in a couple of hours and send them along.

Thank you @wpmudev-support8, we will use that workaround for now even though that’s quite a lot of fields in the actual form ??

Have a great day.

Great, will do @wpmudev-support2

Well @wpmudev-support8, you and I have a different understanding of the word ignored ?? It has been over a year and nothing has been done about this. To me, that falls in the category ignored.

It’s no rocket science to make unique id’s for elements. I mean, instead of forminator-field-name-1 they can use forminator-form-12-field-name-1 for form number 12. Or any other fix would work for us.

Yes, there is the drawback of backwards compatibility for people that target the “old” (non-unique) with custom javascript but waiting longer only makes that list longer too.

Could you please have another word with the devs?

I’ve just sent the message @wpmudev-support1
I hope it can be of any help.

Yes, using line breaks works. We would rather use paragraphs of course but for now this workaround works.

I’ve marked this topic as resolved trusting that it will be fixed