jeff41

Hello Adam.

Thank you for your perseverance. I did switch the axax load settings with no change noted in trying to submit the form. I also updated forminator to the latest version but still have the same error. I then played around with changing the “Other Needs” options and was able to submit the form if I left all the options blank. I redesigned the form by splitting “Other Needs” into two groups “Kitchen Needs” and “Other Needs” by duplicating it and deleting options as needed. Same result – I was able to submit the form only if both were left blank.

I hope that information helps. Using field groups makes the receipt looks more professional. It is a good addition to the form.

Best regards, Jeff

Hello Adam.

I was unsuccessful in avoiding that error. I first set the  zlib.output_compression option to off (it was on) as the easiest test. Adding a function to the MU folder just changed the location to the call to ob_end_flush() function I added to the MU folder.

This form is the only one I’ve used with the new field groups. I rewrote that form without field groups and it is working fine. So I have a work around, but will leave this chat open in case you have more suggestions. I still have the staging site I can use for testing.

Best Regards, Jeff

Hello Nithin.

Thank you for the reply. I created a staging site, https://staging.malahatlegion.ca and made the following changes:

• Deactivated all the plugins except forminator.
• Replaced the OceanWP theme with twenty twenty three

the form is not valid error still persists.

I exported the form to my one drive. Here is the link https://1drv.ms/t/s!AustHvQBdWXKg5ggB07DPVj2jPb3fw

Other than the forminator plugin, I enabled just defender as a precaution. I’ve had several hacking attempts in the past after posting website info here in the past.

The page with the error is, https://staging.malahatlegion.ca/hall-rental-for-special-occasions/

Best Regards,

Jeff

Hi,

I did the first part of the test you asked for. I am using wp-Optimize to handle caching an turned the cache feature off. Ensured all plugins I use are the latest and turned off all elementor experiments except the flexbox one.

The site appeared to be okay until I actually used the editor to make a minor modification in a page. After saving the change I can still see the same result as in the photo where the “Howdy Site Admin” and top bar is showing on public access.

Turning off all the plugins and going through them one at a time will take some time. I will need to make a staging site to do that and try that later.

Thanks for the followup,

Jeff

Thank you, Peter. The culprit is using my iPad rather than my computer keyboard. Apparently after the latest operating system update, the iPad is doing some manipulations behind the scene, so to speak. Even using the html substitution ' on my iPad recommended by Kim led to a different error diagnostic.

after retyping the where clause on my computer keyboard, the publisher table works again.

Appreciate both your and Kim’s help..

Jeff

Thank you for the suggestion, Kim. Unfortunately although the error message changed, I still get the message specifically flagging the 'wdm_lowest_bid' construct when I changed it in the publisher advanced settings where clause section.

Jeff

Here is a link to the exported form in my Dropbox.

https://www.dropbox.com/s/o2ghzxe6fe4ri88/forminator-flea-market-tailgate-reservation-form-export.txt?dl=0

Thank you for looking into this problem.

Jeff

Just an additional note, on rollback to version 1.16.2, the behavior is normal now.