fizzpopmedia

That is correct. The import feature doesn’t work for ANY of my sites at this point. It was working previously.

Correct, I installed a clean wp and LSCWP and importing doesn’t work.

I tried repairing that database and it still doesn’t work.

FYI – I tested this with Gridpane and FlyWP and the result is the same.

Note that the CLI commands work correctly.
I ran: wp example.com litespeed-option get news
It returned the result of 1

I then ran: wp example.com litespeed-option set news 0
to disable news and it returned Success: Options saved. news: 0

To confirm, I then ran wp example.com litespeed-option get news again and it returned the result of 0 . I then checked the front end and the option had also changed correctly in the GUI.

Is the theory that every one of my DBs are corrupted on all my installs? That seems highly unlikely.

I also performed the instructions on a completely clean install. No change.

I am happy to provide admin access if that would be helpful.

@qtwrk the export is valid from any site I try.

I have tried exporting the settings for a number of sites and then importing it on many other sites but it always fails.

Here is a sample file.

Screenshot for clarity

I am using LiteSpeed on Open Lite Speed server.

I used the settings you suggested and it seems to have resolved the issue – I won’t know for sure until we have more customers submit the form.

#1576308

Also one thing I noticed.. When I clear out cookies for the site. I have a dev and staging version ive been ussing to try and figure this out that has the older version of clean talk.. There is only 20 cookies to clear. as soon as I turn your plugin back on, and the problem starts again. I go to chrome settings to delete cookies, and there is instantly 120 cookies to delete. Hope this helps with a solution

UPdated the plugin to the latest version, re activated it, and within a minute it was back to

400 Bad Request
Request Header Or Cookie Too Large
nginx

I deactivated it and its back up and running again. anything beyond just updated it that needs to be done to make this problem go away?

THanks,
BRian

Has this been resolved on the latest release? Ive just spent 10-15 hours with divi and wpengine trying to figure out this nightmare. We just deactived it, and finally the nightmare is over.