Fida - WPMU DEV Support
Forum Replies Created
-
Hello @weju ,
I hope you are doing well.but i would prefer that it wouldn’t appear even in the code.
Could you explain this a bit more?
As there is no built-in option to hide minutes, you will need to use Custom CSS to hide them.
Kind Regards,
Fida Al HasanHello @orianifab ,
I hope you are doing well.
By default, Forminator uses the labels of multiple-option fields (such as Radio Buttons, Checkboxes, and Select fields) in form submissions and email notifications.
If you would prefer Forminator to use the option values instead, please open the Form Editor and navigate to:
Settings → Multiple Option Value
Then select “Option Values” as the preferred setting.
You can learn more about this option here:
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#multiple-option-valueKind Regards,
Fida Al HasanHello @kevincollins ,
I hope you are doing well.
Thank you for sharing this feature request. I agree that having the ability to temporarily disable CAPTCHA without removing the field would help save time and reduce repetitive configuration work during troubleshooting and development.
I have created an internal feature request and forwarded it to our developers for review. The team will evaluate the feasibility of implementing this functionality and consider it for a future release.
At the moment, we do not have an estimated timeline for this feature, but the request has been officially logged and shared with the development team.
Kind Regards,
Fida Al HasanHello @wpnitro ,
I hope you are doing well, and I’m sorry to hear that you’ve encountered this issue.
Please open the form in the editor and navigate to Behavior > Rendering. From there, enable the following options:
- Load form using AJAX
- Prevent page caching on form pages
After enabling these settings, kindly check whether the issue is resolved.
You can find more information about these options here:
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#renderingKind Regards,
Fida Al HasanHello @pembrokellc ,
I hope you are doing well, and I’m sorry to hear that you’ve encountered this issue.
In some cases, the Broken Link Checker (BLC) is unable to edit or unlink URLs within the Gutenberg Block Editor. This is a known limitation, and we already have an internal bug report in place. I have added your case as a vote to help prioritize the fix.
Our development team is actively working on a resolution; however, we do not have an estimated timeframe for its release at this moment.
Kind Regards,
Fida Al HasanForum: Plugins
In reply to: [Broken Link Checker] Quickly exclude a domainHello @galbaras ,
I hope you are doing well, and thank you for the details.
With the Cloud version, you can exclude specific domains and URLs, as well as filter by HTTP status codes. In your case, you can configure exclusions for 403 errors to prevent them from being flagged for specific domains.
Please check this screenshot: https://prnt.sc/TPA9K775E97FThe tool also supports both regular URLs and regex patterns, giving you flexibility in defining these rules.
For more information, please refer to the documentation:
https://wpmudev.com/docs/wpmu-dev-plugins/broken-link-checker/#ignore-url-rulesKind Regards,
Fida Al HasanHello @oyewumi5 ,
I hope you are doing well.I’m sorry, but there is currently no built-in solution available for this requirement.
While a custom-coded solution could potentially achieve this functionality, it falls outside the scope of the support we are able to provide. In this case, you would need assistance from a developer to implement the required custom code.
You may find a suitable developer through the official WordPress jobs directory here: https://jobs.wordpress.net/
Kind Regards,
Fida Al HasanHello @opusvista ,
I hope you are doing well.
I’m sorry, but there is currently no built-in solution available for this requirement. However, you may use the following manual workaround, which is not perfect but may fulfil your need.
You can enable the three name field labels: First Name, Middle Name, and Last Name. Then, rename them as:
- First Name
- Last Name
- Combined Name
You can find more information here:
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#name-labelsNext, enable the three-column layout from the field settings so the fields display in a single row.
Learn more here:
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#name-field-layoutIt will be something like this: https://prnt.sc/5uIILmaQbO6t
Please note that visitors would need to manually complete the Combined Name field as well.
Kind Regards,
Fida Al HasanHello @wordyad ,
I hope you are doing well.I was able to successfully submit the form located at the URL you shared and tested it multiple times without any issues. Please refer to the following screenshot for reference.
Screenshot: https://prnt.sc/sdN-Uz3VDHXrCould you please check whether the issue is still occurring on your end? If it does persist, the problem may be specific to your local environment. In that case, I recommend trying again using a different browser or testing in an incognito/private browsing window.
Please let us know how it goes.
Kind Regards,
Fida Al HasanHello @local99 ,
I hope you are doing well, and thank you for the update.
I visited the URLs you shared, and it appears that the site is currently experiencing a broader layout issue.
Screenshot: https://prnt.sc/13urEhUxWLElThe browser console shows multiple 404 errors for missing CSS and JavaScript files. These missing assets are likely affecting the site’s overall functionality and display.
Screenshot: https://prnt.sc/VFUtYXgktTjnI suspect the same issue may also be impacting Forminator, where required CSS and JavaScript files may not be loading correctly. This would explain why the Forminator admin layout appears broken.
I recommend first resolving the site-wide layout and missing asset issues, then reinstalling Forminator, and checking whether that resolves the problem.
Kind Regards,
Fida Al HasanHello @rickyvbits ,
I hope you are doing well.
Your site is currently using Defender version 4.9.0, which is quite outdated. Please update Defender to the latest available version, 5.11.0, and then check whether this resolves the issue.
If the issue continues after updating, please enable opcache.save_comments on your hosting environment and test again to see if that helps.
But I have other site using the same PHP version but no error.
Could you please confirm whether those sites are hosted on the same server, and whether opcache.save_comments is also disabled there?
Please also note that PHP 8.1 reached its official End of Life (EOL) on December 31, 2025. Since then, PHP 8.1 no longer receives security patches, bug fixes, or official support from the PHP development team. This may expose applications to unresolved vulnerabilities and compatibility risks. I strongly recommend upgrading to PHP 8.2 or higher at your earliest convenience.
Kind Regards,
Fida Al HasanHello @natewolf7 ,
I hope you are doing well, and thank you for the details.
I have forwarded your message to our team. As mentioned in our previous reply, our developers are planning to add a filter/hook that will allow users to override the stored value.
However, we do not have an estimated timeframe for its release at this time.Kind Regards,
Fida Al HasanHello @stumur ,
I hope you are doing well.
When a form is created in Forminator, the plugin generates a custom CSS file for that form and stores it by default in the following directory:
/uploads/forminator/random-names/css/Any files submitted through that form are stored in the same randomized uploads directory.
When a submission is deleted, the associated submission data is removed from the database. If that submission included uploaded files, those files are also deleted from:
/uploads/forminator/random-names/uploads/If all submissions are removed, the uploads directory will still remain in place, but it will be empty.
The CSS directory, however, will continue to contain the generated CSS file, as it is associated with the form itself rather than with individual submissions.
If you would like to remove the entire:
/uploads/forminator/random-names/directory, the form itself would also need to be deleted.
Kind Regards,
Fida Al HasanHello @dba83 ,
I hope you are doing well, and thank you for bringing this behavior to our attention.
I have tested the form in a staging environment and was able to replicate the behavior.
When a Calculation field is hidden, its associated Visibility Conditions no longer apply, as the field itself is not active. As a result, Forminator removes those conditions when the form is saved. If the Calculation field is later made visible again, the previously configured Visibility Conditions are no longer available, as they were removed during the save process.
We understand that this can be inconvenient, especially when working with forms that include multiple conditions and require temporarily hiding certain fields.
This behavior has been reported to the Forminator development team as a potential improvement. They will review it and consider implementing a solution in a future release; however, there is currently no estimated timeline.
Please feel free to reach out if you need any further assistance in the meantime.
Kind Regards,
Fida Al HasanHello @alanintertec ,
I hope you are doing well, and thank you for bringing this issue to our attention.
I have tested the form in a staging environment and was able to replicate the issue. It appears that the problem is resolved when the Forminator plugin is downgraded to a previous version (e.g., 1.52.1).
Specifically, the conditional required field—configured based on the Upload File field—should be ignored when it is hidden. However, in the latest version (1.52.2) of the plugin, this hidden required field is still being validated, which is causing the issue.
We have reported this behavior as a bug to the Forminator development team. They are expected to address it in an upcoming release, although an estimated timeline for the fix is not currently available.
Please feel free to reach out if you need any further assistance in the meantime.
Kind Regards,
Fida Al Hasan