Make WordPress Core

Opened 11 years ago

Closed 9 years ago

Last modified 7 years ago

#25249 closed enhancement (maybelater)

Change directory of re-sized images / manipulated media

Reported by: valllabh's profile valllabh Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Media Keywords: dev-feedback
Focuses: Cc:

Description

Re-sized images currently stores next to the uploaded image. This creates lots of mess at single place.

Situation

If there are 1000 images in library, as after upload WP will automatically create 3 re-sized versions so 3000 images near the origanl is really messy.
Right now there is no way to separate out original images.

Re-sized images should be kept separately as those are not important for backup purposes if you have original images.

Idea

We can have directory called "manipulated" or "manip" where we can replicate exact path to main image.

Original Image Path:
/wp-content/uploads/2013/09/awesome-image.jpg

Resized Image Path:
/wp-content/uploads/manip/2013/09/awesome-image-1024x472.jpg
/wp-content/uploads/manip/2013/09/awesome-image-300x300.jpg
/wp-content/uploads/manip/2013/09/awesome-image-150x150.jpg

Change History (7)

#1 @SergeyBiryukov
11 years ago

  • Component changed from General to Media

This ticket was mentioned in IRC in #wordpress-dev by DH-Shredder. View the logs.


11 years ago

#3 @kirasong
11 years ago

Hi valllabh!

Sorry it took so long for a reply on this one.

I see the value in having better organization.
The trick here is that there isn't currently the idea of a hard "gold master" image in WordPress -- yet. When there is, though, this will be something we'll need to make a decision on.

Related: #21810 #23424

#4 follow-up: @Ipstenu
11 years ago

Re-sized images should be kept separately as those are not important for backup
purposes if you have original images.

Keep in mind the way WP generates these, though :) It makes the image on upload, so if we don't restore the resized from backup, we'll have to add in something to regenerate them all (which can get very CPU expensive). Not that the idea of putting them in a subfolder is bad (I kind of like it and it would help hosts who limit the number of files in a folder), just that for a backup I'd want all my images thank you :D

#5 @chriscct7
9 years ago

  • Keywords 2nd-opinion removed
  • Milestone Awaiting Review deleted
  • Resolution set to maybelater
  • Status changed from new to closed

Closing due to lack of interest.

#6 @johnbillion
7 years ago

#41918 was marked as a duplicate.

#7 in reply to: ↑ 4 @pgideonbolger
7 years ago

Replying to Ipstenu:

Re-sized images should be kept separately as those are not important for backup
purposes if you have original images.

Keep in mind the way WP generates these, though :) It makes the image on upload, so if we don't restore the resized from backup, we'll have to add in something to regenerate them all (which can get very CPU expensive). Not that the idea of putting them in a subfolder is bad (I kind of like it and it would help hosts who limit the number of files in a folder), just that for a backup I'd want all my images thank you :D

I find that I have to remove the thumbnails using regex and regenerate them using a plugin every time I move a site anyway. It would certainly help me a lot if the thumbnails could be kept in a separate folder.
Some of our clients accumulate photo libraries of 8-10gb, so reducing the size of the filesystem can really speed things up.

Note: See TracTickets for help on using tickets.