A bug in Forminator version 1.52.2

Hello @alanintertec ,

Thank you very much for the detailed report — we really appreciate the effort you’ve put into testing and confirming this on multiple sites.

We’ve tested Forminator v1.52.2 on our end and were not able to reproduce the issue. Forms are submitting normally, so this appears to be related to a site-specific setup rather than a general regression.

The 404 error for the jQuery UI image file in your console is worth noting, but it’s unlikely to be the direct cause of form submission failure on its own — that’s a missing asset, not a script error. The actual validation error is likely coming from somewhere else.

That said, your findings are consistent and worth investigating properly.

Let’s go through a few quick checks to narrow this down. To help isolate the cause, could you work through the following on a staging/test environment:

1. Reinstall Forminator
   Delete and reinstall version 1.52.2 to ensure all plugin files are complete and not corrupted.
2. Clear cache
   Clear your browser cache and any caching plugin or server/CDN cache, then test again.
3. Check for conflicts
   Temporarily:
   • Disable all other plugins
   • Switch to a default WordPress theme (like Twenty Twenty-Four)
     Then test the form. If it works, reactivate things one by one to find the cause.
4. Try another browser/device
   This helps rule out any browser-related issues.
   
5. Check your browser console more carefully
   Beyond the 404, are there any JavaScript errors in red? If so, please paste them here.

If the problem persists, we’d like to take a closer look at your form setup. Please share an export of the form with us:

To export your form:

• Go to Forminator → Forms in your dashboard
• Click the gear icon next to the form
• Select Export
• Copy the export code
• Paste it at https://pastebin.com
• Share the link with us here

Note: This export does not include any submitted data — your entries remain safe on your site.

Once we have that, we’ll investigate further and help you get this resolved.

Best regards,
Mina Emad

Hello @alanintertec ,

Thank you for the update on your issue.

Please note that we’re not allowed to have the login credentials shared here or log in to the website.

You can simply commence by sharing a link to your test form page and the export of the form with us here, and we will help debug the issue.

To export your form:

• Go to Forminator → Forms in your dashboard
• Click the gear icon next to the form
• Select Export
• Copy the export code
• Paste it at https://pastebin.com
• Share the link with us here

Note: This export does not include any submitted data — your entries remain safe on your site.

Once we have that, we’ll investigate further and help you get this resolved.

Best regards,
Mina Emad

Hello again @alanintertec ,

Thank you for sharing the form export — that was very helpful.

I’ve been able to reproduce the issue on my end, and it appears to be related specifically to visibility conditions involving file upload fields.

What’s happening

When a required field of any type (e.g., the “Date images where taken” fields) has a visibility condition based on a file upload field (e.g., the “Upload Images” fields) being empty (null) or not empty (i.e., Show/Hide the “Datepicker field” When the “file upload field” Is/Is not empty [null]), the following occurs:

• On the front end, the visibility logic works as expected
• However, on submission, the server-side validation fails, resulting in the error:
  “Your form is not valid, please fix the errors!”

How to solve

While rolling back to v1.52.1 (or older versions) appears to resolve the issue, please note that older versions may lack important security updates and improvements included in the latest release.

As a temporary workaround, we recommend:

• Avoid using file upload fields (“Upload Images”) in visibility conditions, especially when:
  • The condition checks for empty/null values
  • The affected fields (“Date images where taken”) are marked as required

If possible, you can:

• Replace the condition with another field type (e.g., checkbox, select, etc.), or
• Remove the required constraint from fields controlled by such conditions

Next Steps

We will escalate this to the development team for further investigation, as this behavior is not expected and should be addressed in a future update.

If you have any additional examples or edge cases, feel free to share them — they can help speed up the fix.

We really appreciate your thorough testing and patience while we look into this. Please don’t hesitate to reach out if you need help adjusting the form in the meantime.

Best regards,
Mina Emad

Hello @alanintertec,

Thank you for the update; it’s great to hear that the checkbox approach is working well for you!

I’m glad we were able to help you move forward with this. If you need any further assistance or run into anything else, please don’t hesitate to reach out — we’re always happy to help.

Since everything is now working as expected and the topic is resolved, we’d truly appreciate it if you could take a moment to share your experience with Forminator and the support you received by leaving a quick review here: https://wordpress.org/support/plugin/forminator/reviews/#new-post

Your feedback means a lot to us and helps others as well.Thanks again, and have a great day!

Best regards,
Mina Emad