Wordpress LScache Plugin: Beaver Builder Plugin and LSCAche
Last Updated on: Wed, 15 Apr 2026 00:00:02 I have a problem with updating the beaver builder plugin and LSCache plugin. If I login to a site and manually perform the upgrade everything works as it should. Problems only occur if you remotely update the bb plugin (which i have to do as I manage over 100 sites). Examples of remote updates are updating via managewp and also I tested it with the new auto update plugin feature in WordPress itself. The plugin auto updates and all seems fine. As soon as I log in it then breaks the site. I then have to manually purge all to fix the layout. What seems to be happening is the BB plugin deletes its compiled css and js when it is updated successfully. But whenever you remote update via managewp or auto update the light speed cache is not purging so the bb files are 404 and the layout breaks. Either lightspeed needs to detect managewp/auto update or the other way round? Im tearing my hair out on this one as I cannot find a reason this is happening. Hi, Did you enable Purge All On Upgrade to ON ? it supposed to purge all on plugin updates add_action( upgrader_process_complete, my_upgrade_function,10, 2) function my_upgrade_function( $upgrader_object, $options ) if (defined(LSCWP_V)) do_action( litespeed_purge_all ) please try add this into functions.php , see if upgrader_process_complete can trigger it or not Best regards, I always have Purge All On Upgrade to ON and that code did not work.It seems to break when a user log in after the plugin has been updated. Does Litespeed plugin do a purge when you log in? So my steps are: 1. Perform a beaver builder plugin update either through ManageWP or enable auto updates. 2. Once the remote update is complete if you browse the site everything seems fine and the layout is fine. 3. Once you log in I get a Purged all caches successfully. message and then when anyone visits the site it is broken with 404 to to all the Beaver builder cache files. Hi, yes well , due to the way LiteSpeed caches page (as it requires webserver to do the caching , so webserver needs to know the site domain when cache or purge , otherwise it doesnt know which domain to purge) if ManageWP or wp-cron is performed on CLI way , instead of https way , webserver may not know which domain/pages needs to be purged and ended up in weird issue. but does Beavers files constantly changing in name or something ? Best regards, When you upgrade any plugin, theme or update a page Beaver Builder. Direct quote from support: When you update the beaver builder plugin, it clears its own compiled css/js in the uploads folder so it can be regenerated with the updated version of the plugin, your cache is statically caching the pages with links to now non existent css/js files because they now dont exists, which is why you need to clear your statically cached pages. According BB support you now have special cache rules regarding Beaver Builder built into the plugin? Hi, yes , I assume these hooks are still valid ? https://github.com/litespeedtech/lscache_wp/blob/master/thirdparty/beaver-builder.cls.php Best regards, Hi thanks what should I do with this? actually , I dont see the issue here upgrader_process_complete this hook is fired when WP plugin upgrades as long as the upgrade is triggered by https cron , not WP CLI , it should work thats why I asked before as how did you ManageWP or wp-cron trigger ? you can firstly , try manually install a low version of BB , then manually upgrade it , see if it purges properly this will indicate where is the issue ok I will do some tests thanks I think all plugins work fine when the update is first processed. But it seems that as soon as any user logs in after an update, Litespeed purges the cache again, and it is at this point that it cannot find the Beaver css/js files to be clear when I manually upgrade there is no problem Hi, okay , please try this add this code into your themes functions.php add_action( upgrader_process_complete, my_upgrade_function,10, 2) function my_upgrade_function( $upgrader_object, $options ) error_log( test log , 3, /path/to/your/public_html/lscwp.log ) and change /path/to/your/public_html/lscwp.log to your actual path , then do the way you used to (the way that doesnt purge automatically) after that , check if you have file /path/to/your/public_html/lscwp.log and what is content of it Best regards, Hi, Just follow up , how thing goes ? Best regards, Hi, Im going to mark this topic Resolved , due to lack of activity. If you still need help, please feel free to re-open it. When re-open it, please also change the topic status to not solved Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference