Now that we have the option of storing product images in the file system instead of in the database, are there any inherent advantages/disadvantages to either method? Thinking mostly about execution speed, but would like to know in general. Thanks.
you have to decide which to use before you start images to products.
ie: if you start with "storein database" and insert product images then you switch, and add images, the previously inserted images before the switch will not be found and the reverse is true.
think database size - if you have a lot of modestly sized images your database will fill up faster - i think some of the cheaper plans have quite small database allowance
Media.Images.StoreInDB (should be on page 5 ) set to false
while you are there, you should look over some of the other settings just to familiarise yourself (some of them can be altered from other parts of admin eg configuration-->global settings)
Does 1.5 store the download sample file in the database? And if so, how do you change it so that it doesn't?
I am setting up a store that sells digital products, and I only have 90 products in and it keeps running out of space. The error message I get looks like this:
-------------------------- Could not allocate space for object 'dbo.Nop_Download'.'Nop_Download_PK' in database 'pranopv15d2703' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. --------------------------