PINT Inc

I tried both my main admin account as well as the wpdmsupport account.
Both are administrators.

It is not worth our time or our clients time to continue this conversation.

We already provided a test URL and login credentials in a private reply where it is obviously broken using a fresh install.

You then say “it works on my machine”, which is extremely unprofessional.

What browser and URL did you test? Where is my access to that “working” environment?

If not, please test using the URL and credentials I already provided.

This is very unprofessional and lazy. Did we not pay for the plugin and support?

So, after a little more looking into your plugin code, since this is a high-priority issue for our client, I was able to get things working by overriding just a few things:

1. fileRequest function from wp-content/plugins/download-manager/src/DropZone/DropZone.php
2. A 100% custom wp-content/themes/<THEME_NAME>/download-manager/file-request.php that generates correct/working POST data (this was the main fix right here!)
3. Bypass uploadFile and chunkUploadFile from wp-content/plugins/download-manager/src/AuthorDashboard/AuthorDashboard.php by adding my own wp_ajax_wpdm_frontend_file_upload and wp_ajax_nopriv_wpdm_frontend_file_upload actions that are basically copies of the original functions, but allow me to bypass the restrictive “must be logged in” setting that your plugin doesn’t aloow the user to customize via settings or proper filters.

Really it seems like there just needs to be more filters added for developers to use, then we can fix/change things ourselves without having to other support 🙂

However, we would still prefer that this issue be looked into on the sandbox site, as there is still a core JS error/issue with the plugin. We’d love to be able to continue recommended you to clients (2 paid licenses in the last 6 months so far from us), but the fragility/lack of developer filters and hooks makes it difficult to continue recommending WPDM right now.

I look forward to your fix!

Did you read my initial comment correctly? Are there translation issues?

After the 6.7.1. upgrade, your built-in, non-custom feature stopped working. Please reread the comment and provide an appropriate response. We have already spent a lot of time working around issues with your plugin, but this time we are reaching out since support is supposed to be included.