whuang99

Hi Erica, I cleared browser cache, purged Siteground cache, added cache exclusions and none of these solutions worked.

I also disabled Siteground Optimizer and tested in a different browser that didn’t have anything cached. It’s still messed up.

• This reply was modified 10 months, 3 weeks ago by whuang99.

Hi Aurovrata, thanks for looking into it. To you previous question, I verified the Cloudflare rules are working and disabled in the backend.

Instead of enabling WP_DEBUG, I set Cloudflare to Development Mode (bypasses cache), and the Smart Grid UI loaded up normally without error.

I’ve already had page rules in Cloudflare setup to disable caching in the backend according to those instructions, which makes this error a bit perplexing. Already dumped cache too.

• This reply was modified 3 years, 8 months ago by whuang99.
• This reply was modified 3 years, 8 months ago by whuang99.

I also did rollback to earlier versions of smartgrid, as well as CF7 and it made no difference. When smartgrid is disabled, CF7 seems to work fine.

Jules – I’m on WP 5.4.2, was on CF7 5.2, and am using Conditional Fields Pro 1.9.7.

Theme is Avada 6.2.2

I did try rolling back Conditional Fields Pro to an earlier version and it didn’t make a difference. It was only when I rolled back CF7 back to 5.1.9 did it resolve.

• This reply was modified 4 years, 4 months ago by whuang99.

Had the same issue after updating to 5.2.

The problem is 5.2 breaks the conditional fields function. Normally, if the group hasn’t been triggered, CF7 ignores the required fields within the group and submits the form. Not the case with the update.

Thank you for looking into it. How would I fix this?

By the way, I tried bootstrap and standard, also tried disabling CSS.

Seems your support form is just hanging there, won’t submit. Is there an email I can send this information to?

I’m having the same issue with text in horizontal view in mobile not responsive. Any resolution?

Also, I tried disabling widgets individually via the plugin UI. It seems that some widgets cause the 502, whereas others (button widget) are okay.