• Resolved kjross13

    (@kjross13)


    I use the Draft Scheduler plugin to post hundreds of recipes to my recipe blog. Now that I am using your plugin on my multi site install, I am getting hundreds, if not thousands of these error when I schedule posts:

    Warning: fileperms(): stat failed for /wpid-13353251-150×150.jpeg in /home/kravers/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 1516

    Warning: fileowner(): stat failed for /wpid-13353251-150×150.jpeg in /home/kravers/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 1520

    Warning: filegroup(): stat failed for /wpid-13353251-150×150.jpeg in /home/kravers/public_html/wp-content/plugins/ewww-image-optimizer/ewww-image-optimizer.php on line 1524

    I seem to get one of each of these for every post that is scheduled.

    Please help

    http://wordpress.org/plugins/ewww-image-optimizer/

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

    (@nosilver4u)

    Generally that means the file doesn’t yet exist. I might do a look at that particular plugin to see what exactly is happening there. At any rate, the next version is going to be doing some preventative checks to be sure that file operations aren’t attempted unless the file exists. I’m planning to release it shortly after WordPress 3.7 (which was due out this week, but they just did RC2, so hard to say).

    Plugin Author nosilver4u

    (@nosilver4u)

    From what I can tell, it doesn’t seem like Draft Scheduler is the problem. How are those images being uploaded? It seems like they are missing a full path, as it is highly unlikely that “/wpid-13353251-150×150.jpeg” is the full path.

    Thread Starter kjross13

    (@kjross13)

    I have a custom application that uploads the images, and even though I get that huge number of errors, once the posts are scheduled/published, they do work and the images do load…which is what I thought was so weird about the whole situation.

    Plugin Author nosilver4u

    (@nosilver4u)

    Those ‘errors’ are technically only ‘warnings’ so they aren’t fatal, which allows wordpress to keep processing things. So, while it is a bit obnoxious, it won’t cause any harm. I’d like to try and make the ‘file-finding’ algorithm a little more robust for 1.7.0, so one way or another we’ll take care of those errors.

    Would you mind sharing what application you are using, so I can attempt to see where and how it is storing file paths and such?

    If not, are the files stored in wp-content/uploads, or someplace else?

    Plugin Author nosilver4u

    (@nosilver4u)

    If you want, you could try the development release at http://downloads.wordpress.org/plugin/ewww-image-optimizer.zip

    I’ve enhanced the file-finding algorithm to see if it works for some plugins that don’t do things quite the way WP expects them to. Plus it also has the code to not attempt any operations on files that don’t exist yet.

    Plugin Author nosilver4u

    (@nosilver4u)

    see if the issue is fixed with 1.7.0

    Thread Starter kjross13

    (@kjross13)

    ok, I will test it and let you know within a few hours.

    Plugin Author nosilver4u

    (@nosilver4u)

    any news?

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Getting Error Codes When Using Draft Scheduler’ is closed to new replies.