Download data store errors

Hi @scmsteve!

It could be a couple of reasons for this happening.

It could be that some download_ids for some specific products have a higher length than what the database can handle, it could also be that you are using something like Subscriptions and deleted some files which are still attached to the subscriptions.

In order to get a better idea of your setup, can you please forward us your status report? You can find this under “WooCommerce > Status” page.

Cheers!

We are using subscriptions, but all of the associated downloads are still there. Would this be better handled as a support ticket? I regret that it was almost two months ago when I looked at this, and got pulled in different directions and am just getting back to it so my memory is a little bit more spotty…. I had put in some debugging code and that is how I followed the sequence I mentioned above where it was happening at the time of trying to update the download count in the metabox, and at one point in the process the download_id exists as it assigns a permission, but when it gets to the metabox update that is gone. I had contacted support at the end of April, but didn’t get very far, as is typically the case, becuase we have a lot of active plugins (carefully curated and tested) and they insisted it was another plugin and wouldn’t help. Unfortunately I haven’t come up with a specific way to test this, I just see it happen periodically in the logs, and it seems the only side effect is that the download count in the meta box can’t be properly displayed but as far as I know we haven’t had reports of downloads being invalid/inaccessible at all.

By the way, these downloads aren’t managed by subscriptions (or memberships, or anything else), they are just either purchased or free downloads attached to their accounts.

@scmsteve If you’re still running into this issue and do have valid subscriptions for premium extensions, like Subscriptions, please do create a ticket in your WooCommerce.com account. This will allow us to troubleshoot much deeper than we can here.

I have tried, but what plugin should I file it under? We have a lot of paid plugins. This isn’t related to subscriptions from what I can tell, just purchased downloadable items. I think I did try formal support and was basically told that we had too many plugins, disable everything and see if it still happens. Well, since I can’t exactly duplicate the sequence that causes this error, it is very sporadic, it would be hard to know that and I can’t cripple our site in the mean time. Plus, I can’t test on a staging site when I don’t know what action triggers this. That is why I was hoping someone with more knowledge on the internals of what is going on would chime in and give some helpful debugging feedback, like some code to put in at some key point to capture more information than what is being made available.

I did the best I could at the time to narrow down what was happening, it seemed tied to the system trying to retrieve the download count to display in the metabox. It seems that somehow records are created but removed, at least based on the notes above, but it has been a busy month with many other things going on and I can no longer remember all the details. ??

@scmsteve You should be able to choose WooCommerce core as a selection when creating a support request.

As for too many plugins, I’m sorry if you were told that, but having a lot of plugins adds a lot of variables to the mix for troubleshooting purposes. If you are able to replicate the issue on a staging site, please do create a support request and we can take a further look. It appears it might happen when a customer’s downloads are edited, possibly from their order.

Hi,

We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

It isn’t resolved, too many other things going on that are more pressing. ?? .This is a very occasional issue and seems to have no user impact.

Since I still cannot cleanly reproduce it, nobody believes it is a real problem, but it is still happening now and then.

Before just closing issues, it would be nice if you reached out to verify first.