download_maxdays will not update only on certain products

Hey gang (and Ajeh - who I may need the most help from on this)

This past weekend I needed to modify certain products on my website that use download links. All has been well for the past 3 years, but I came upon this strange thing last night.

I use PHPmyadmin to upload a large group of items to mySQL. After I completed deleting my old items and uploaded the new ones (in which the ONLY change was the product model name and the new zip file name to match it), I wanted to change all my products_attributes_download/products_attributes_maxdays to 1000.
All the existing products updated correctly and so did the new products by applying 1000 to all the products in the products_attributes_download/products_attributes_maxdays row with a Query.

When I placed test orders for multiple downloadable products with existing and newly uploaded model numbers, the order completed correctly and I could download all the files for each one.
EXCEPT.... When I went and looked at the orders_products_download table, all the new product uploads from this today continued to stay with my original maxdays of 4 (which I used for year before last night), while all the other products correctly changed to 1000.

Here's what I modified:

1 - EVERY row in products_attributes_download/products_attributes_maxdays correctly says 1000 (existing and new uploaded products)

2 - The admin config was updated to 1000 (which I know doesn't matter in this instance)

3 - I keep running different SQLs changing the maxdays to different numbers, and the older products change when I run test orders, BUT the NEW product uploads never change from the original 'old' maxdays of 4 (ugh!).

4 - I optimized the database in every table

5 - I changed the field length in products_attributes_maxdays from 2 to 8 just in case it would help.... it didn't

I'm 'stumpified' !!! Does anyone have any ideas why the maxdays for these new product uploads will not change to the new amount of 1000??

Is there any other place in the tables where an original maxdays could be still 'stuck' at my old '4'?? Something I could flush out?

I would also be willing to reupload all of this data again in the table for the new products if one thing is configured wrong, but I just can't track it down.

Any help from the 'team' or members would be greatly appreciated.

thanks,

At this time, the Update status is using the settings of the Default Max days and Download count ...

Can you further detail what you mean by Default Days? I have the admin/config/attributes set to 1000 days. Is there another place that is considered 'default'.

I checked my uploading csv data and there is only one field carrying max_days in it (which is set to 1000 also).

I can't pinpoint another area of my csv files or in ZenCart that is overriding this 1000 days with a 4 for these particular products.

thanks,

The defaults are in the Configuration ... Attribute Settings ...

Download Expiration (Number of Days)
Set number of days before the download link expires. 0 means no limit.

Number of Downloads Allowed - Per Product
Set the maximum number of downloads. 0 means no download authorized.

Then on each of the Attributes are their initial settings for Maximum Days and Maximum Downloads ...

Thanks Ajeh, but no 'dice'.

I still get all the new product uploads to process after the order is finished with only 4 downloads (even though both the default setting and the products_attributes_downloads show 1000 downloads. All the existing products on the site with the exact same setting are showing 1000 downloads when purchased (correct)

I finally gave up and put everything back to 4 downloads across the board and created an SQL schedule to change all the orders_products_downloads to 1000 days at midnight. This way the customer gets their download within the original 4 days, but at midnight it resets to 1000. No phone calls after 4 days.

Then I modified the template to hide the download days from the customer so they don't even know the difference.

No problem Ajeh. Something weird was going on with this though that was unexplainable and I really wanted to track down....:smile:

It is very odd that your Attribute setting is not controlling this, regardless of what the default is set to ... :unsure:

Thanks for letting us know you have a work around ... :smile: