prandilorenzo1

I’ve seen that in the today update of AmpforWp there’s a fix for GDPR input issues. I’ve reactivated everything and seems to work now.
I close this thread, I think that was an issue with AmpforWp plugin.

I’ve seen that in the today update of the plugin there’s a fix for GDPR input issues. I’ve reactivated everything and seems to work now.

As you can see in the other topic I got this error using AmpforWp with litespeed with Cache turned on and Cache rest Api on too.
I’m going to try on a new installation to be sure that is exactly that the issue.

Seem to be resolved now: I’ve disabled “CACHE REST API”
I’ll keep it monitored to see if the issue strikes back

Done, here it’s https://www.diffchecker.com/Ww7w8iHB

Update from litespeed plugin forum

Turned everything on except enable cache, everything keep works..

It get broken just enabling the first voice “enable cache”
I suppose all others works just if this one is turned on, right?

Disabilng everything in the cache settings (except cache mobile) seem to solve the problem…

Have done, purged all and issue persists. Maybe I should try to use debug?

Obviously, yes.
I tried disabling html minify too, nothing changed

I’ve noticed that input work before the refresh of the page, after accepting cookies

I’ve done that, issue persists

I hope it’s this
HDEMLAUH

Sorry, what’s that? Where I could find it?