reBusted!
View on WordPress.orgScores higher than 2% of indexed plugins
About
Force browsers to load the most recent file if modified.
What It Does
reBusted! forces web browsers to fetch the most recent version of your static files (CSS, JavaScript, images) when they have been modified, rather than serving the cached copy. It works by appending a unique query string or hash to asset URLs after each change. This solves the common frustration of users seeing stale styles or scripts after a site update.
Who It's For
This plugin is best suited for developers, designers, and agencies actively iterating on WordPress sites where clients or visitors repeatedly see outdated cached assets. It is also helpful for content teams that push frequent visual changes and want to avoid confusion from old browser caches. Small business owners running active redesigns will benefit most.
Who Should Skip It
Anyone running a production site with a proper caching plugin, CDN, or cache-busting workflow already in place does not need this tool. Visitors on modern browsers with reasonable cache headers will rarely see stale assets in the first place.
The Bottom Line
reBusted! does a narrow job competently and earns perfect ratings from its small user base, but its overall quality score of 50.9 reflects limited maintenance activity and almost no support footprint. It is a reasonable pick for developers in active build cycles, though most production sites will get the same result from a modern caching plugin or CDN. Treat it as a useful utility, not an essential one.
Related Plugins
Pick Query Monitor when you need a full developer debugging suite covering database queries, PHP errors, hooks, and HTTP calls, not just cache busting.
Choose WP Crontrol if your real problem is debugging or managing scheduled tasks rather than forcing browser cache refreshes.
Pick Clear Cache for Me if you need a one-click button to purge multiple caches after edits, including widget-specific cache clearing.
Choose WP Debugging when your issue is inspecting PHP errors and the debug log rather than controlling browser asset caching.
Pick Debug Log Manager if you need a centralized viewer for WordPress error logs instead of a browser-side cache solution.