Wordpress LScache Plugin: Object Cache causing problems when deleting and updating an option
Last Updated on: Wed, 15 Apr 2026 00:00:02 HI! Im noticing unexpected behavior when calling delete_option and update_option when Object Cache is enabled, similar to the behavior reported in this support forum thread. The option value is not changed after calling delete_option and update_option. You can reproduce the behavior with this: update_option(testing_cache, 1 ) error_log( get option before delete: . get_option(testing_cache)) delete_option(testing_cache) error_log( get option after delete: . get_option(testing_cache)) update_option(testing_cache, 2 ) error_log( get option after update: . get_option(testing_cache)) When Object Cache is enabled, the log shows: [20-Aug-2020 18:48:33 UTC] get option before delete: 1 [20-Aug-2020 18:48:33 UTC] get option after delete: 1 [20-Aug-2020 18:48:33 UTC] get option after update: 1 When Object Cache is disabled, the log shows the expected output: [20-Aug-2020 18:50:10 UTC] get option before delete: 1 [20-Aug-2020 18:50:10 UTC] get option after delete: [20-Aug-2020 18:50:10 UTC] get option after update: 2 I also want to note that both the Memcached and Redis Extensions are disabled on my site. The user in the support forum link above also reported that the extensions were disabled. Im using LiteSpeed Cache version 3.3.1. I tried both on frontend and backend pages, cant reproduce it. Can you tell your OC settings? Thanks for taking a look at this! Ive tested this on a handful of sites, and I can reproduce it on all of them. The Object Cache is on, and all of the OC settings are the defaults. The Memcached and Redis Extensions are both disabled. Basically, I installed LiteSpeed Cache, turned Object Cache on, and the behavior described above occurs. Hi, Could you please submit a ticket here ? We will investigate it further Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference