[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f_Yz-LWrPrwvWE42i9l8UZDbpML00kOiRVziUpjPkwe0":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"benlumley","https:\u002F\u002Fprofiles.wordpress.org\u002Fbenlumley\u002F",2,270,85,30,84,"2026-04-04T19:14:58.351Z",[13,38],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":19,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":33,"download_link":34,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"filename-based-asset-cache-busting","Filename based asset cache busting","1.4","\u003Cp>Filename based cache busting for WordPress scripts\u002Fstyles using last modified date.\u003C\u002Fp>\n\u003Cp>Stop telling clients or users to hard refresh \u002F shift refresh. The url to all of the css\u002Fjs files on your site will change automatically whenever the files are modified. You can set proper long cache lifetimes to help get top scores on Google Pagespeed without running into cached css\u002Fjavascript problems.\u003C\u002Fp>\n\u003Cp>Based on this gist https:\u002F\u002Fgist.github.com\u002Focean90\u002F1966227 from Dominik Schilling, I’ve enhanced it by automatically replacing the asset version with the files modification time and automatically editing htaccess – making it install + forget.\u003C\u002Fp>\n\u003Cp>Includes querystring option as a fallback – which works in more scenarios.\u003C\u002Fp>\n\u003Ch3>Webservers\u003C\u002Fh3>\n\u003Ch4>Apache\u003C\u002Fh4>\n\u003Cp>The plugin should add what it needs to your .htaccess file jsut like WP itself. But if for any reason that doesn’t work for you – here’s what it adds:\u003C\u002Fp>\n\u003Cpre>\u003Ccode># FBACB\n\u003CIfModule mod_rewrite.c>\n  RewriteEngine On\n  RewriteBase \u002F\n\n  RewriteCond %{REQUEST_FILENAME} !-f\n  RewriteCond %{REQUEST_FILENAME} !-d\n  RewriteRule ^(.+)\\.([0-9\\.]+)\\.(js|css)$ $1.$3 [L]\n\u003C\u002FIfModule>\n\n# still fbacb\n\u003CIfModule mod_expires.c>\n    ExpiresActive on\n    ExpiresByType text\u002Fcss                            \"access plus 1 year\"\n    ExpiresByType application\u002Fjavascript              \"access plus 1 year\"\n\u003C\u002FIfModule>\n# END FBACB\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>NGINX\u003C\u002Fh4>\n\u003Cpre>\u003Ccode> location ~* ^(.+)\\.(?:\\d+)\\.(min.js|min.css|js|css)($|\\?.*$) {\n   try_files $uri $1.$2;\n }\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Host specific notes\u003C\u002Fh3>\n\u003Cp>Some webhosts need a bit of custom config to get the filename based urls working.\u003C\u002Fp>\n\u003Ch4>WP Engine\u003C\u002Fh4>\n\u003Cp>To work on WP-Engine, you’ll need the following redirect added via my.wpengine -> installname -> Redirect rules\u003C\u002Fp>\n\u003Cpre>\u003Ccode> Source: ^(.+)\\.([0-9\\.]+)\\.(js|css)$\n Dest: $1.$3\n Type: break (this is under advanced)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>CloudWays\u003C\u002Fh4>\n\u003Cp>Just works.\u003C\u002Fp>\n\u003Ch4>Flywheel\u003C\u002Fh4>\n\u003Cp>Just works.\u003C\u002Fp>\n\u003Ch4>PHP Fallback\u003C\u002Fh4>\n\u003Cp>If your webserver is failing to serve assets using url rewriting, the plugin attempts to serve them itsef (ie: via PHP). Obviously this is slow\u002Fless than ideal in production (it’ll be much slower) – so you should configure your web server correctly to serve the files. If you see this HTTP header “FBACB-Php-Fallback: yes” on your assets, this applies to you.\u003C\u002Fp>\n\u003Cp>Note that hosts are increasingly configured to serve css\u002Fjs directly from disk and won’t fall back to PHP + WordPress error handling – this fallback then won’t work.\u003C\u002Fp>\n","Filename based cache busting for WordPress scripts\u002Fstyles using last modified date.",200,9968,100,5,"2020-04-27T21:47:00.000Z","5.4.19","3.0.1","",[28,29,30,31,32],"asset","assets","css","js","version","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffilename-based-asset-cache-busting\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffilename-based-asset-cache-busting.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":39,"name":40,"version":41,"author":4,"author_profile":5,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":21,"num_ratings":6,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":26,"tags":49,"homepage":26,"download_link":55,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"password-protect-staging","Password Protect Staging","1.0.0","\u003Cp>Enable, set a user and PW via WP admin and users will be prompted via HTTP AUTH for a user\u002Fpw before being able to view the frontend.\u003C\u002Fp>\n\u003Cp>Aim of the plugin is to protect staging sites from the prying eyes of search engine robots, and to keep out anyone who might stumble across it accidentally.\u003C\u002Fp>\n\u003Cp>This isn’t particularly secure – password is in the database.\u003C\u002Fp>\n","Quickly and easily password protect a site to keep it from the prying eyes of google.",70,8298,"2014-10-16T08:22:00.000Z","5","3.5",[50,51,52,53,54],"auth","htpasswd","http","password","staging","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpassword-protect-staging.0.1.zip"]