Using a filter for jpg_quality will hellp you to set your quality for uplaoded images. add_filter(‘jpeg_quality’, create_function(‘$n’, ‘return 70;’)); In most good implementations of Image Optimization you can find a various usae of ImageOptimization tools such as optimng/jpegtran etc, there a lot of plugins that help you to do that.
When I go to the dashboard>settings>permalinks and click save changes, this code disappears It sounds like WordPress is overwriting your htaccess file when you save. Thus, your changes are gone. Perhaps set this up outside of the htaccess in the apache config? Or ask your host to do this for you. Then WP can’t overwrite … Read more
I used your exact set of .htaccess directives to achive json gzip’ing. Took my files from 23k to 4k. So I would assume its one of the two following things: Your.htaccess is not allowed to use these directives so it ignores them. Thus you either need to do one of the following: a) edit the … Read more
For compressing the uploaded image I wrote a simple code snippet that immediately overwrites a newly uploaded file with an image whose quality can be specified: function wt_handle_upload_callback( $data ) { $image_quality = 30; // Change this according to your needs $file_path = $data[‘file’]; $image = false; switch ( $data[‘type’] ) { case ‘image/jpeg’: { … Read more
(this should be a comment, but my reputation is too low) Setting jpeg_quality will not disable compression because it does not disable processing. JPEGs will be always compressed, and they are almost never lossless, not even at 100 – it does not stand for “100% original quality”. What happens here, is that WordPress’s default image … Read more
My advice to you is not to worry about adding in the copious amount of .htaccess rules for forcing browser caching and setting correct expire time values for assets. If you download the W3 Total Cache plugin it handles adding all of the above into your .htaccess file for you. If you would prefer not … Read more
One solution I found was to include the original image in the $sizes array. Like this, after all the conversions to others sizes the uploaded image will also be converted to its same size and some other given quality. Please note that by doing this you’ll lose the original image, and if you add any … Read more
There is little ‘bug’ in PHPWee. It should use <?php instead of <?: <? namespace PHPWee; require_once(“src/CssMin/CssMin.php”); require_once(“src/HtmlMin/HtmlMin.php”); require_once(“src/JsMin/JsMin.php”); // Open-source (BSD) PHP inline minifier functions for HTML, XHTML, HTML5, CSS 1-3 and Javascript. // BSD Licensed – https://github.com/searchturbine/phpwee-php-minifier/blob/master/LICENSE // // Usage // $output = \PHPWee\Minify::html($any_html); // $output = \PHPWee\Minify::css($any_css); // $output = \PHPWee\Minify::js($any_js);
That is a huge difference! I think this is your issue… Any time an image is uploaded, if that image was saved in the Adobe RGB color space, then the image does not get loaded correctly for resizing. Thumbnails are saved in the default color space, which is sRGB. By failing to perform the color … Read more
It’s set in schema.php, the WordPress Administration Scheme API. You can also find it in the Codex. As you can see from a search through core, there’s (as far as my search went) exactly no use case for it, aside from defining it as 0 when adding that option to the DB. If you want … Read more