Wordpress LScache Plugin: V3: Image optimisation database
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, checking this topic here I noticed I am now having to very similar database entries: wp_litespeed_img_optm wp_litespeed_img_optming Which of these am I suppose to keep with V3 and is it save to manually empty/delete the one not needed. I have had some problems with requesting image optimisation in the past, switching back and forth between stable and preview plugin version. Hi, wp_litespeed_img_optming can be safely deleted on v3.0 Best regards, Why is created again? I deleted it and it is again there? Each time when you send new request, it will be created. If you want it to not create again, the only way is to not use the image optimization send new request (both the manual request button, and the request cron). Hmm, why should I delete it in the first place if it is going to be recreated again? I asked if that was a possible error/problem caused by the transition from V2 to V3. Ah, BTW. After more than 1 day still stuck at 2% of optimization. Whenever I request a new optimization I receive: Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. [server] https://node100.quic.cloud [service] img_optm The option to pull images is hidden. I have been waiting for more than 2 months now for this image optimization to work again, and yet this is as broken as ever before. I am on a site owner plus license, so its that I am complaining about a free service? Hi, There is proceeding queue not pulled yet. [server] https://node100.quic.cloud [service] img_optm Could you please check if cron is working properly to pulling the images ? If you have link to QC dashboard , please check the image page , it would state some error log if there is. Best regards, There are some images optimized (like two hours ago), however I also geht this: Requests Status refresh In queue: 0 Proccessing: 0 Ready to be pulled: 0 Pulled: 0 Errors: 0 Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. [server] https://node100.quic.cloud [service] img_optm Still waiting for a solution , report number: FCLWIYNX
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference