One part of my site deals with quite large images. I've used an image optimizer and reduced all the image file sizes by about 30%.
The problem is, if I just manually upload the whole folder, all the values in the filesize column of the "files" table will be wrong. My question is: does this really matter? Is there any negative side effect of this?
Neil
On 6/30/2011 7:59 AM, Neil Coghlan wrote:
One part of my site deals with quite large images. I've used an image optimizer and reduced all the image file sizes by about 30%.
The problem is, if I just manually upload the whole folder, all the values in the filesize column of the "files" table will be wrong. My question is: does this really matter? Is there any negative side effect of this?
If you're not using quotas there shouldn't be any effect. Drupal uses the filesizes in the DB to calculate quota usage.
Ted
that's what I too suspected, but then found this:
saying it was a bad idea to manually alter/overwrite anything in the /files folder
alternatively, is there any quick way of re-submitting images through the imagecache module so that the new values get written to the DB. Doing it one by one would be too painful.
On 30/06/2011 14:16, Ted wrote:
On 6/30/2011 7:59 AM, Neil Coghlan wrote:
One part of my site deals with quite large images. I've used an image optimizer and reduced all the image file sizes by about 30%.
The problem is, if I just manually upload the whole folder, all the values in the filesize column of the "files" table will be wrong. My question is: does this really matter? Is there any negative side effect of this?
If you're not using quotas there shouldn't be any effect. Drupal uses the filesizes in the DB to calculate quota usage.
Ted
The "flush" command in imagecache will wipe out the imagecache-generated images. They will then be regenerated on-demand, just like the first time. You can do so per-style.
--Larry Garfield
On 6/30/11 12:49 PM, Neil Coghlan wrote:
that's what I too suspected, but then found this:
saying it was a bad idea to manually alter/overwrite anything in the /files folder
alternatively, is there any quick way of re-submitting images through the imagecache module so that the new values get written to the DB. Doing it one by one would be too painful.
On 30/06/2011 14:16, Ted wrote:
On 6/30/2011 7:59 AM, Neil Coghlan wrote:
One part of my site deals with quite large images. I've used an image optimizer and reduced all the image file sizes by about 30%.
The problem is, if I just manually upload the whole folder, all the values in the filesize column of the "files" table will be wrong. My question is: does this really matter? Is there any negative side effect of this?
If you're not using quotas there shouldn't be any effect. Drupal uses the filesizes in the DB to calculate quota usage.
Ted
Unfortunately, this is only applicable to presets such as thumbnails, etc. It doesn't alter what's in the "files" table and flushing all your presets (which I did) has no effect on data stored in that table.
On 30/06/2011 15:58, Larry Garfield wrote:
The "flush" command in imagecache will wipe out the imagecache-generated images. They will then be regenerated on-demand, just like the first time. You can do so per-style.
--Larry Garfield
On 6/30/11 12:49 PM, Neil Coghlan wrote:
that's what I too suspected, but then found this:
saying it was a bad idea to manually alter/overwrite anything in the /files folder
alternatively, is there any quick way of re-submitting images through the imagecache module so that the new values get written to the DB. Doing it one by one would be too painful.
On 30/06/2011 14:16, Ted wrote:
On 6/30/2011 7:59 AM, Neil Coghlan wrote:
One part of my site deals with quite large images. I've used an image optimizer and reduced all the image file sizes by about 30%.
The problem is, if I just manually upload the whole folder, all the values in the filesize column of the "files" table will be wrong. My question is: does this really matter? Is there any negative side effect of this?
If you're not using quotas there shouldn't be any effect. Drupal uses the filesizes in the DB to calculate quota usage.
Ted