Greg Primrose asked 2 years ago
Since last Sunday or so, we've been getting this error on almost all our formidable forms.
We've had no issues with the plugin for years, but beginning last Sunday about, no one can use our forms as they just error out.
For example, we have a form to apply to join our station, several people have reported they get the error on the employment history section, but someone today said they got it on demographics.
We are on the most current version.
I am on a grandfathered license, so I really don't want to have to upgrade to get the logging, but I can't see any reason it would suddenly begin erroring out.
Shawn Pery answered 2 years ago
Try adding a hidden date/time field and see if that let's you submit.
Greg Primrose
replied 2 years ago That didn't help, and another form we have that's having issues already has a date/time stamp.
Victor Font Staff answered 2 years ago
Have you cleared all caches, including browser, opcache, memcache, etc?
Greg Primrose answered 2 years ago
We've cleared all our caches.
I've ran repair tools on the tables.
I've deleted every entry in the form.
Nothing will fix this form.
I even tried rolling back the app.
I guess I'm going to have to upgrade my license so I can get the logging to see what the form is crashing on.
You don’t need the logging add-on to troubleshoot this issue. Logging is for API troubleshooting. WordPress debug should tell you what you need to know if you enable it.
Greg Primrose answered 2 years ago
I enabled WP-Debug.
It showed errors related to two plugins.
[12-Mar-2023 23:27:44 UTC] PHP Notice: Trying to get property 'ID' of non-object in /home/cvfc/public_html/wp-content/plugins/show-hide-author/show_hide_author.php on line 245
[12-Mar-2023 23:27:44 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:27:44 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:27:54 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:27:54 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:27:58 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:27:58 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:28:20 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:28:20 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:29:05 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
[12-Mar-2023 23:29:05 UTC] PHP Notice: Trying to get property 'post_parent' of non-object in /home/cvfc/public_html/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Core.php on line 429
I disabled and uninstalled both plugins.
Still getting the same error with Formidable, and now no errors in the debug log.
Greg Primrose answered 2 years ago
Update:
It's been two weeks now and the forms are still broken. I finally found an error after using three different debug problems. This error occurs on every page that fails. It doesn't show up in the debug logs but I found it with a dfifferent plugin.
"Unknown: Multipart body parts limit exceeded 64. To increase the limit change max_multipart_body_parts in php.ini."
Of course, I can't find any usual documentation on how to add "max_multipart_body_parts" to my php.ini since it doesn't currently exist.
Bobby Clapp Staff answered 2 years ago
Nice find. Can you find something like this in your php ini file or add it?
; How many multipart body parts (combined input variable and file uploads) may
; be accepted.
; Default Value: -1 (Sum of max_input_vars and max_file_uploads)
max_multipart_body_parts = -1
Greg Primrose
replied 2 years ago There's nothing like that in my php.ini
I'll add it and see what happens.
ilmira abdullina answered 2 years ago
Hello I started receiving exactly the same error once changed the domain name for my website. Is there any fix for that?
Walter Jones answered 2 years ago
There was a fix issued recently related to that error as it relates to woo commerce. Anyone running that? If so update FF.
Please login or Register to submit your answer
That is a generic error. My guess is that it isn't getting through the spam filter. Have you submitted a ticket with Formidable support?
I will.
I turned off the Honeypot and the error is continuing.
Do you have any settings limiting the amount of submissions to these forms?
We do not have any that I'm aware of. The forms are set to open.