Shahjada

Please update all wpdm add-ons, that will resolve your issue.

Hi,
We have rewrote the add-on from the ground to make the code base and UI better, still working on that view, it will be available with the next update, coming within this week.

Hi,
With wpdm v5.3.2, you should be able to do that without any adjustment. You only need to add the following 2 lines in wp-config.php:

define('WPDM_ADMIN_CAP','edit_posts');
 define('WPDM_MENU_ACCESS_CAP','edit_posts');

Hi,
We are releasing a new update of the add-on this week.

Thanks.

The update is available now.

Hi,
Yes, for email lock, when the user enters name and email once it stores in the browser’s temp storage, and for the next time, the name and email will be auto-filled from temp storage.

Here it is:

Okay, got the issue, update is coming by tomorrow.

To set default values, you will need:

WPDM Default Values

The problem was the lazy load option with sg optimizer was breaking the js code. I’ve disabled the lazyload option and everything is working fine now:

Yes.

you need to contact your server/hosting support.

Still redirecting me to that same captcha page.

Please give me your site URL too.

I’ve reinstalled wpdm pro on your site and downloads are working fine now.

I checked your site, I see there wpdm free version installed. But, you are a pro user. Did you removed the pro version and installed the free version?

Okay, adding no access option is a good idea, noted.

Releasing a new update by tomorrow with the double-entry fix. Actually Amazon S3 Bucket Access Control is for the authors, editors or admins, or any role who is authorized to create a package. Assign a bucket to a role means, when a user from that role will be creating a package, you will be able to upload to or attach files from the specified bucket.

PDF stamper add-on update fixed the issue.

Hi,
Sorry for the trouble, the issue was due to pdf stamper add-on incompatibility with the latest version of wpdm pro, we have updated it and everything is working fine now.

Done :).

You’re right, there was a spelling error, however, we have fixed it and released a quick update. Also, it is updated on your site.

As I see, It is working fine on your site:
https://tppr.me/7FFtm