fixed an issue with some base64 encoded fonts and icons becoming invalid.better sourceMappingURL removal during minification.fixed an issue where some files were not being minified.changed the default cache directory to wp-content/cache.added support for custom cache location via wp-config.php constants.switched from WP_Filesystem_Direct() to WP_Filesystem().added auto varnish cache purge for Cloudways.added option to allow processing on specific query strings.added cache purging support for nginx helper plugin.changed deferred css/js cache clearing from 24h to 7 days.renamed a common name class to avoid conflicts with other plugins.fixed a bug when merging css/js can break the site layout if the plugin failed to write the cache file (there will be an html comment on the footer if this happens).changed writing the css/js files to WP_Filesystem_Direct with a secondary fallback method.cloudways & godaddy cache purging fixes.No, it's that business owners have 100 other things - which are usually more profitable and higher ROI - to focus on, and plugins not working shouldn't be one of them.Ĭhangelog (registro delle modifiche) 3.2.8 Because better competition will always come along and they'll just switch to them.Ī lot of cynical IT people will say "user error" or "you're lazy" or "you're retarded" lol. This is why the customer is always right. Or don't, and let a better competitor come along who does. It's up to the WP plugin author to make that possible, not the users. People shouldn't have to read up documentation just for a freakin plugin. Most people aren't tech-savvy and just want to push 'activate', click on a few recommended settings, and go. A successful plugin will cater to the dumbest of the dumbest people who are also in a rush. I read in other reviews that the plugin author said 'it's meant for advanced users' and 'manually adjust settings'.ġ) Well that should be in big bold words on the plugin pageĢ) You should put more emphasis on guiding users through the processģ) That's a great way to make a plugin less popular, since this is a frontend facing product, where your average user isn't tech savvy. If you need to customize the path and url, you need to edit your wp-config.php and add both define('FVM_DIR', '/path/to//your/public/directory') and define('FVM_URL', '').
You need a public directory to store and serve minified cache files. Purge all caches on the entire network (linux): wp site list -field=url | xargs -n1 -I % wp -url=% fvm purge.Purge all caches on a network site: wp -url= fvm purge.If you would like to hire me, please visit my profile links for further information. I can offer you additional custom made optimization on top of this plugin.
Wordpress minify how to#
Kindly read the HELP section after installing the plugin, about possible issues and how to solve them. In that case, you would need to add the file to the ignore list, else the cache would grow indefinitely (because obviously the original files themselves are dynamic and when you minify, the plugin sees a different file). If your cache is growing significantly, this could mean one of your CSS or JS files is dynamic and changes on every pageview. Once the first request is processed, any other pages that require the same set of CSS and JS files will be able to reuse the same generated static CSS or JS file. Minification is done on the frontend during the first uncached request. Each site is different, so the default recommendations may or may not work for you and you will need to test and find out how to adjust your settings. Note you need to look into the HELP tab after installing the plugin and manually configure it for your site. HTML, CSS & JS optimization plugin for developers and advanced users.
0 kommentar(er)
