diegpl

It seems that this solution can bring me just the images page, not the images themselves through a filter, how can I get just the images through the filter? Thank you!

It is still working I just have forgotten to activated the main one. Thank you buddy! 😉

Another thing I realized is that “PNG Optimization Level” is allowing to set lossy option, but it does not seem to be working alright, since it resized the image from 3,56 MB to just 3 MB. Thank you.

I just uploaded a 3,56 MB png image size. The plugin resized it to 872 KB, Photoshop resized to 683,7K when saved for we.
These are the logs.
On http://xxx/wp-admin/upload.php?page=ewww-image-optimizer-dynamic-debug:
nothing appeared about it, but about other images that was not resized it did.
#0 ewww_image_optimizer() called at /wp-content/plugins/ewww-image-optimizer/image-editor.php:170
#1 _save() called at /wp-includes/class-wp-image-editor-gd.php:376
#2 save() called at /wp-content/plugins/optimize-images-resizing/inc/class-resize-image.php:106
#3 image_downsize() called
#4 call_user_func_array() called at /wp-includes/class-wp-hook.php:298
#5 apply_filters() called at /wp-includes/plugin.php:203
#6 apply_filters() called at /wp-includes/media.php:201
#7 image_downsize() called at /wp-includes/media.php:824
#8 wp_get_attachment_image_src() called at /wp-admin/async-upload.php:61

On http://xxxxx/wp-admin/upload.php?page=ewww-image-optimizer-queue-debug:
Just after the big png image was uploaded.
119241 – wp_ewwwio_media_optimize_batch_7cfe19bf086d4cabcd52050536fd2753
1482 – image/png

Another thing that called my attention was that although my max_execution_time is set to 90, plugin debug.log http://xxxx/wp-content/plugins/ewww-image-optimizer/debug.log showed max_execution_time: 600

It seems that you are right about it being a false positive, but why you told me that the first one can cause CPU issues if it is getting blocked? And how/why could it get blocked?
So does this one reallys runs every five minutes? If yes, why?
wp_ewwwio_media_optimize_cron_interval 300 5 0.083333333333333 Every 5 Minutes

According to this text https://www.ecenica.com/support/answer/fix-high-cpu-load-wordpress/ it is a good idea Disable WP-Cron and set another way for that, what do you think about that? If you agree, do you have any plugin to suggest me?

I know it is a lot of questions, but I hope to help you with that as well, supplying the maximum information about everything.

Thank you!

• This reply was modified 9 years, 2 months ago by diegpl.
• This reply was modified 9 years, 2 months ago by diegpl.

I did that. it returned a 404 error page. While logged I got this warn:
<!– Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/

Object Caching 8069/8218 objects using disk
Page Caching using disk: enhanced (User is logged in)
Page cache debug info:
Engine: disk: enhanced
Cache key:
Reject reason: User is logged in
Creation Time: 1487257699.000s
Header info:
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <http://xxxx/wp-json/&gt;; rel=”https://api.w.org/&#8221;
Database Caching using disk (Request-wide User is logged in)

Served from: esites.pro @ 2017-02-16 15:08:19 by W3 Total Cache –>

While not-logged this:
<!– Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/

Object Caching 1891/1916 objects using disk
Page Caching using disk: enhanced
Page cache debug info:
Engine: disk: enhanced
Cache key: xxx/w3tc_rewrite_test/_index.html
Creation Time: 1487257755.000s
Header info:
Set-Cookie: cbc_country_name=Brazil; expires=Fri, 17-Feb-2017 15:09:11 GMT; Max-Age=86400; path=/; domain=xxxx
Set-Cookie: cbc_country_code=br; expires=Fri, 17-Feb-2017 15:09:11 GMT; Max-Age=86400; path=/; domain=esites.pro
Set-Cookie: PHPSESSID=7622c3f0daf0f810df94b5837f1ee656; path=/
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <http://xxxx/wp-json/&gt;; rel=”https://api.w.org/&#8221;
Database Caching 6/33 queries in 0.262 seconds using disk

Served from: xxxx @ 2017-02-16 15:09:15 by W3 Total Cache –>

What was supposed to show up? Is the warn just about speed? It looked like an error warning, telling me something on my .htaccess was not right and because of that the plugin would not work as it should, right? Any thoughts? Thank you a lot!!!

I have taken a look into the warned folder and it is alright comparing to the install instructions. But on the general settings page the warning is still showing up. Is it a bug or not? Thank you a lot and congrats for the amazing plugin!!! 😉

Thats the error warning which appears to me, although debug message enabled for page cache showing up on the source code says its alright:
W3 Total Cache error: It appears Page Cache URL rewriting is not working. Please verify that the server configuration allows .htaccess
Unfortunately disk enhanced page caching will not function without custom rewrite rules. Please ask your server administrator for assistance. Also refer to the install page for the rules for your server.

That would be great man. Another thing you could implement on your plugin in order to free up the user of Imsanity and https://wordpress.org/plugins/optimize-images-resizing/ would be the possibility to set resize for post/page uploader, media library and anywhere else, just like Imsanity does. And a feature to look for useless images like “Optimize Images Resizing” does.
I just sent you a very extensive plugins test report through you FB page in order to help you up with more information about almost anything you want about WordPress plugins and themes. Im probably the biggest WordPress plugins tester ever existed lol. I hope it helps you up about new features for your plugin and others! 😉