This is an issue with wordpress's month based organization of media files.
To re-create the issue:
- Delete an image file from a previous month
- Upload the same image file (same name)
- The newly uploaded file gets placed in the SAME month folder as it was originally, rather than in the current month.
This is an issue for me because the amazon s3 plugin (code.google.com/p/wordpress-s3/) which I'm using to host my images on s3, DOES place the newly uploaded file in the current month, so the file on s3 is in a different location than on the wordpress server.
Does anyone have experience with this "bug"? Which is the correct behavior, that of wordpress, or the s3 plugin?
What it looks like is that the s3 plugin and wordpress DO NOT work in parallel in their creation of month based uploads folders.
s3 always uses the current month. In other words, regardless of the publish date of the post, the upload will always get placed in the current month folder (i.e. if today's date is may 2012, I upload an image and it goes to s3bucket/uploads/2012/05/)
By contrast, it seems as though wordpress places the images in the folder based on the date of the original creation of the post. So if you create a post in february save as a draft, then add images in may, then publish it, in s3 your images will be in 2012/05, while in your regular server they will be in 2012/02. This is a serious problem for me for a lot of reasons that are too complex to get into here, but it is a serious issue nonetheless.