Scan and Optimize not working after adding a system folder

  • Resolved WolfgangHammersmith

    (@wolfganghammersmith)


    9 years, 1 month ago

    Just updated the plugin after noticing some theme files weren’t optimized.

    The update didn’t do it so I noticed the developers put some of the images in an /img/ folder inside the theme folder. No problem, added the path to the advanced section and then did a new scan.

    This error comes back in a second or two:
    Operation timed out, you may need to increase the max_execution_time for PHP
    With debug turned on the output looks fine, these are the last two lines:

    found 13879 fullsize (1 unoptimized), and 130871 resizes (9 unoptimized)
ewww_image_optimizer_aux_images()

    Given how fast it throws the error it’s really unlikely to be a PHP timeout but digging around in that function doesn’t thrill me so I figured I’d try some support. ??

    https://www.ads-software.com/plugins/ewww-image-optimizer/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    Normally the scanner is recursive, so I’m not sure why it wouldn’t have grabbed those the first time around, unless you had done them a while back without having metadata stripped or something.
    At any rate, these sort of issues are usually a memory problem triggered by specific file types. I’ll dig out my instructions for debugging those, and try to post them for you tomorrow.

    Thread Starter WolfgangHammersmith

    (@wolfganghammersmith)

    The developers literally added an /img/ folder where there hadn’t ever been one so that path was never checked previously.

    I suspected the issue is with folder but I’ve removed it and still get the error.

    Server log has:
    [Fri Feb 05 11:30:21.135006 2016] [fcgid:warn] [pid 35554] [client 100.70.20.100:62069] mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 159 bytes) in /var/www/clients/client0/web77/web/wp-content/plugins/ewww-image-optimizer/aux-optimize.php on line 448, referer: https://clientwebsite.net/wp-admin/upload.php?page=ewww-image-optimizer-bulk

    Our development server has Version 2.5.6 of the plugin paired with WordPress 4.4.1. Scan and optimize is fine pre-update and post (both the core & plugin).

    UPDATE: I re-read what you’ve said and now I’m wondering if they didn’t stick a massive file into the /img/ folder by mistake! I will test with file size limits next.

    Thread Starter WolfgangHammersmith

    (@wolfganghammersmith)

    Nope. Limiting it to a smaller file PNG size wasn’t the ticket. I really should ask for a directory listing. I hate remote servers with CMS only access!

    Plugin Author nosilver4u

    (@nosilver4u)

    That might make things a little tricky. Is there any way you can get me a copy of the theme folder so I could test it on my dev server?
    If so, send it in a .zip file via https://ewww.io/contact-us/

    Plugin Author nosilver4u

    (@nosilver4u)

    Nevermind that, I remembered that after we had issues a few times with the mimetype functions during scanning that I rewrote the scanner. So the most likely problem is too many images in the ewwwio_images table.

    So, first step is to find baseline memory usage on the Bulk Optimize page. Can you please install this plugin and check how much memory is being used on the Bulk Optimize page: https://www.ads-software.com/plugins/debug-bar/

    It will add a Debug button on your admin bar that you can click to view memory stats.

    Then look at the line above the Show Optimized Images button on the Bulk Optimize page, and see how many images it says have been optimized.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Scan and Optimize not working after adding a system folder’ is closed to new replies.