Dmytro - WPMU DEV Support

Hello @michba,

This version should be good for most plugins.

However, if the plugin hasn’t been updated for a long time, it may not be working correctly on the latest PHP versions, or have issues with one particular version.

“Uncaught TypeError” error may also be caused by other things like a plugin/theme conflict, incorrect file permissions, etc.

If the issue persists, we’d suggest to ask WP Debugging plugin’s support directly for their help at https://www.ads-software.com/support/plugin/wp-debugging/,sSince the error log you’ve shared references files from /wp-content/plugins/wp-debugging/ directory,

Best Regards,
Dmytro

Hello @rafaelpires20,

I hope the above suggestions helped.

We haven’t heard back from you for some time, so I’m marking this thread as resolved. Please feel free to reopen it and reply if you need our further assistance.

Best Regards,
Dmytro

Hello @juliotake,

I hope you’re doing great today!

Please note, that we provide support only in English. Feel free to use online translation services, if needed.

As for the PHP warnings, this appears to be an issue on the latest WordPress version, but it should not be affecting the form performance. Our developers are working on improving this in future plugin releases, but there’s no ETA at the moment.

As a workaround for now, you can try to temporarily switch the site language to English, or temporarily disable debugging, in order to hide these warnings:

https://learn.www.ads-software.com/tutorial/debugging-in-wordpress/

I hope this helps. Please let us know, if you have any questions.

Best Regards,
Dmytro

Hello @lomenade,

I hope you’re doing great today!

We haven’t heard back from you for a while, so I’m marking this thread as resolved. Please feel free to reopen it and reply if you need our further assistance.

Best Regards,
Dmytro

Hello @sr20detg20girl,

I hope the above suggestions helped.

As we haven’t heard back from you for a while, I’m marking this thread as resolved. Please feel free to reopen it and reply if you need our further assistance.

Best Regards,
Dmytro

Hello @companyatif,

I hope you’re doing great today!

This appears to be a bug, discovered in the latest version, and our developers are already working on a fix. We apologize for the inconvenience.

There is no ETA at the moment, but a workaround would be installing Forminator version 1.35.1 from here:
https://www.ads-software.com/plugins/forminator/advanced/

Best Regards,
Dmytro

Hello @joyca23,

It looks like some recent changes in WordPress core affected other plugins as well. If you can find the instances like /wp-content/plugins/{PLUGIN NAME} in the error log, you may notify the developers of this particular plugin, and keep it up to date.

As a workaround for now, you can also try to temporarily switch the backend language to English, and see if it helps.

Best Regards,
Dmytro

Hello @jkengineer,

The Cloud version doesn’t have exactly the same options, that’s why you can’t spot them in the Hub.

It’s mostly currently limited to configuring schedule scan options, and display options:
https://prnt.sc/Dy-Mx-gxSfHf

Our developers are working on adding more features in future versions. In order to be updated on new changes, you can monitor the changelog on the Development tab of the Broken Link Checker page, or subscribe to the updates at the bottom of the roadmap page here. If you’d like particular ones to be implemented, please let us know.

Best Regards,
Dmytro

Hello Marcin,

Thank you for the clarification.

There’s no integration with WooCommerce user accounts, therefore it requires either manually creating and mapping the form fields, or developing a custom snippet (must use plugin).

The list of the WooCommerce checkout meta field names can be found here.

You can easily map some of the fields, like street address, city, ZIP code to WooCommerce meta fields in User Registration >> Add Custom User Meta section:
https://prnt.sc/_jJY2PoyUbZo

However, WooCommerce stores country and state fields in particular format, which should be used instead of the full names.

Alpha-2 format is used for the country codes:
https://www.iban.com/country-codes

And ISO 3166-2 format is used for the state/province codes, for example:
https://en.wikipedia.org/wiki/ISO_3166-2:US

If your online shop operates in a limited number of countries, you can create Select fields with the country/state names, and values (codes), and then map them to WooCommerce fields the same way as other custom fields, in User Registration >> Add Custom User Meta:
https://prnt.sc/bBej_HcAFWpm

https://prnt.sc/hOBDWfG0_M66

https://prnt.sc/Hcsfav-MX7PC

If you need adding lots of countries and states, adding them manually as Select fields would become more difficult. In this case you may consider developing a custom snippet for mapping the large list of countries and provinces to WooCommerce meta fields.

Creating such snippets would be outside the scope of support we provide. You may hire a developer for this kind of advanced customization. For example, check out the WordPress jobs directory here: https://jobs.wordpress.net/

Feel free to email us at [email protected] if you need any further advice, using the following line as the subject: ATTN: WPMU DEV support – wp.org

I hope this helps. Please let us know if you have any questions!

Best Regards,
Dmytro

Hello @hollosipeter,

Thank you for the clarifications.

I’ve forwarded the details to the developers, in order for them to check if there’s something that could be improved in Forminator, to avoid similar issues.

As a workaround for now, you can try disabling International Telephone Input With Flags And Dial Codes plugin on specific pages with Forminator forms.

This can be done with this plugin, or a similar one: https://prnt.sc/9sf5icJSSvqT

Best Regards,
Dmytro

Hello Stanislaw,

I’ve tested it by connecting the same form on two sites, and HubSpot integration was working fine in both cases.

In order to illustrate the issue, could you please send some screenshots of the Forminator/Hubspot areas, where the form is not displaying as properly connected.

Since direct image uploads are not allowed on this forum, you can upload your screenshots to Google Drive, Dropbox, or use any cloud image/file sharing service.

Looking forward to your reply!

Best Regards,
Dmytro

Hello @geni1,

Thank you for sharing the form export. It looks like the visibility rule was somehow corrupt. When I remove, and re-create the rule, it starts working properly.

In you form export code, this rule looks like this:

"conditions": [
  {
	"element_id": "consent-1",
	"rule": "is",
	"value": "ausgew?hlt"
  }
],
"condition_action": "show",
"condition_rule": "all"
},

but it should have “checked” as the value, instead of “ausgew?hlt”:

"conditions": [
  {
	"element_id": "consent-1",
	"rule": "is",
	"value": "checked"
  }
],
"condition_action": "show",
"condition_rule": "all"
},

It’s possible that some translation plugin, or software is interfering, for example, when you import or export the form.

Please check on your end, if re-creating the visibility rule helps first. If the issue persists, try it after disabling translation plugins and browser add-ons.

Let us know if there’s still any issue after that.

Best Regards,
Dmytro

Hello @sg1magar,

On my test site flex-grow starts working only if I set display: flex; for that element, for example:

group-1 > .forminator-all-group-copies > .forminator-grouped-fields > .forminator-row > .kanamettl {
    display: flex;
    flex-grow: 5;
}

It works the same way for other groups, otherwise doesn’t change anything.

Could you please test on your end, whether using display: flex; rule helps. Let us know if you need any further assistance.

Best Regards,
Dmytro

Hello @david2024,

Thank you for letting us know the result of testing the form. I could not replicate this on a lab site.

Could you please export the form with both the upload and calculation fields, and share it via Google Drive, Dropbox, or a similar service, in order for us to test it.

Please also check if the issue persists with Twenty-Twenty Four, or another default WordPress theme.

Best Regards,
Dmytro

Hello @realdh1,

I couldn’t replicate the same issue with your form so far. The phone field looks fine on my end: https://prnt.sc/v_gPp21F-i1f

Could you please check if hard-refreshing the page makes any difference:
https://fabricdigital.co.nz/blog/how-to-hard-refresh-your-browser-and-clear-cache

If the issue persists, please let us know what browser and operating system you’re using, in order for our techs to thoroughly test it.

Please also check and let us know, if there’s any error in the browser console.

Best Regards,
Dmytro