Plugin Support
qtwrk
(@qtwrk)
please provide the report number
you can get it in toolbox -> report -> click “send to LiteSpeed”
Done, report number: DAZHGNUP
Mike
Plugin Support
qtwrk
(@qtwrk)
could you please try disable object cache , purge all , then try enable REST cache again ?
Thanks qtwrk, Done as requested, same thing happens, REST cache reverts to off.
Plugin Support
qtwrk
(@qtwrk)
okay , let’s try it in different way
export your current setting if needed
disable plugin
go to phpMyAdmin or mysql cli -> your wp database -> wp_options table
search and delete all the rows that contains litespeed.
, don’t miss the dot at end
then re-enable plugin , import back setting if you have exported , now try again.
No problem, just to confirm, delete all rows that contain litespeed. – there are hundreds.
OK, I tried that and even though it appeared to delete all 229 rows, they immediately reappeared or weren’t actually deleted perhaps. No change with REST cache functionality either.
Should I instead delete the LiteSpeed plugin and then the rows in WP_options?
Plugin Support
qtwrk
(@qtwrk)
yes , there will be 100 – 200 rows
did you re-enable the plugin after you delete it ?
they should not come up until you enable the plugin again.
I did but they had already reappeared. I disabled the plugin, ran a SQL query, deleted the 229 rows and actually did that twice because they immediately reappeared. Strange. I was thinking that maybe I needed to delete the plugin?
Plugin Support
qtwrk
(@qtwrk)
wait , please confirm that re-appear back WITHOUT you re-enable the plugin ?
Correct, I never saw that happen before. There is a chance I’ve somehow goofed, but I don’t think so. I can repeat the process if you wish?
Plugin Support
qtwrk
(@qtwrk)
now that’s weird
do you have something as “protection” or “lockdown” the change ?
Not that I’m aware of, but I wondered if it related to Hostinger’s hpanel master settings for Litespeed perhaps?
Plugin Support
qtwrk
(@qtwrk)
I don’t think that will affect the site if you manually uninsall it
OK, so should I try again, this time uninstalling the LiteSpeed plugin perhaps?