• Hello!

    We have enabled your plugin for testing but it’s been stuck at 2% since February. Any idea how to fix that?

    Also, there is a typo in the plugin, it says “Inital size” instead of “Initial Size”.

    Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • Hello.

    Perhaps there is some image that is not being converted or with an error. What do you have in the Optimization Log on the main page of the plugin?

    Thread Starter joyryde

    (@joyryde)

    Hello!

    Here is a screenshot:

    https://tinyurl.com/ycztckmt

    When you scroll down, every single image says “Error: Server responded an HTTP error 500” so I think your plugin uses more memory than Hostgator hosting allows. We have it set to only do 1 image at a time.

    • This reply was modified 2 years, 7 months ago by joyryde.

    In your screenshot, the Server is Down. This means that your site cannot connect to the optimization server. This is not a problem with the plugin, perhaps the hosting is blocking requests.

    Thread Starter joyryde

    (@joyryde)

    So your hosting company is blocking ours?

    No. There may be difficulties from your server to the optimization server.

    Thread Starter joyryde

    (@joyryde)

    Looking now it says “Status: stable”

    Error: Server responded an HTTP error 500

    Try uploading a different image and optimizing it.

    Thread Starter joyryde

    (@joyryde)

    When a new image is uploaded it doesn’t optimize. Apparently we have to go to Media first, and then manually optimize each one, but we have 10,000 so this plugin probably wont work for us…since it doesn’t optimize on upload, nor on prior uploads.

    Do you have optimization enabled when uploading in the plugin settings?

    Thread Starter joyryde

    (@joyryde)

    I’m not sure if this issue is related, but I’ve noticed critical issues with our installation today because apparently cronjobs are failing and blocking the rest of the queue (in our case, sending emails, for example).

    I’m not clear if it should be like this, but I found tens of events in the cronlog named “wrio/cron/optimization_process”, some of which should be executed every second. In the log from the optimizer there were several errors with the message “Broken Pipe” or similar.

    I don’t want to give a false alarm, but maybe a developer can take a look at whether it would be possible that errors in the processing affect the rest of the cron queue, because of course it shouldn’t.

    Thanks at this point for all the work ??

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Stuck at 2% for weeks or months…?’ is closed to new replies.