I have also had the same type of Media Library uploader error, with uploads hanging once Seller A. had created around 40 packages.
Although they can still upload the base file to be downloaded (these use a different process and are stored into their own uploads folder) trying to add another small ‘preview’ image – which goes into the Media Library, just hangs.
Although Seller A. does have 40-odd images in the Media Library, they are all pretty small (<120kB each)…..
DETAILED ERROR EXPLANATION (tested several times, consistent error)
Create/edit a Package, everything works fine EXCEPT for uploading any *new* files into the WPDM Media Library. Adding *existing* images from the Media Library is fine.
DEBUG CHECK ONE.
I can upload the same file directly via WP back-end Media Library uploader (note different code to WPDM Media Library uploader!).
So it’s unlikley to be an issue with the file itself.
DEBUG CHECK TWO.
Log into the site as Seller B. and it all works perfectly fine. The only difference betwen Seller A. and Seller B. is the number of ‘packages’, hence the number (or storage total) Media Library files they have allocated to their User ID.
So it’s unlikely to be a process coding “error’, rather it seems more likely a limitation being placed on the actual user ID.
——————–
Whe you access the WPDM Media File uploader it gives you a screen with the following: [Button] and text.
…or
[Select Files]
Maximum Upload File Size: 500MB
Unfortunately I haven’t been able to find where this 500MB value is set – it’s not through:
- Downloads > Settings > Front End Access > Max Upload Size From Front-end: – I’ve set this to 1000MB
- php.ini > upload_max_filesize – I’ve set this to: 1024MB
I can’t see this being a server setting anyway, as the server can’t know how much data the user ID has accumulated – the only way you could get this total is by a database query. So it could be set in WP, WPDM, another WPDM plugin or even the Theme, unfortuntely searching through files for ‘500’ gets an awful lot of hits…….
——————–
WORKAROUND
For WPDM installations I leave WP using the default WP Media Settings of: use ‘month-and-year’ based folders, seems a fortunate coincidence I did (as I don’t usually).
When you open the WPDM Media Library uploader it does have a filter, but this ‘defaults’ to displaying [All Dates], so basically it shows you *all* media files uploaded by *all* users. Huh? why there isn’t a ’40-per-page’ option OR a user filter (a realtively easy implementation) is a mystery to me.
Anyway, if I change the filter to an empty ‘older’ folder eg. [June 2019] it reports back:
No items found.
Drop files anywhere to upload
or….
And guess what? Uploading from here is fine. However…….
What is curious is that the file does not upload into the [June 2019] folder, instead it uploads into the ‘current’ folder – in this case is [Aug 2019].
ANALYSIS
No idea why it behaves like this – it was just dumb luck that I found this.
I’m guessing it is a coding issue with the WPDM Media File uploader, however as most of you already realise there really isn’t any official support for this product – so don’t hold your breath waiting for a reply or code fix. Even if you have paid for Pro licenses (like me) they almost *never* repond to any Forum support questions.
When they do there is no rhyme or reason, it almost seems like a random selection. So it seems more like scraps to keep the masses from rioting? lol.
BTW if you *really* want a response, my suggestion is to pretend you are a new buyer testing out their ‘free’ version before you buy – this way you will definitely get a response so you can push the questions as far as you think appropriate. They gave me some really good assistance ‘pre-purchase’, but that support has simply vanished now I’ve paid for it.
It’s a bit of a shame you have to resort to this, because it is a really-nice, great-value little product.
But IMHO with the support they ‘offer’, you need to be able to code PHP yourself to get it to work properly, especially if you want to use it for a commercial application where things might need to be fixed quickly. Most core edits won’t run in a child theme so that should also tell you quite a lot of how you need to manage these installations.
🙂