n8-B

@Amos – here’s a gist of the code I used to prevent the wpdm_login action from loading: https://gist.github.com/N8-B/a445c580266e7af109ca

If you’re comfortable with php, add it to your functions.php file. If not, have a developer do it for you. It solved my log-in problems, but your set-up might be different.

Hi Shaon,

I’ve fixed the log-in problem by removing the wpdm_login action in a custom plug-in. But it’d be a good idea to look into it since there are likely other WPDM customers who use WooCommerce.

We sell both physical and digital items as well as subscription products, which, as far as I’m aware, requires more functionality than WP Download Manager offers.

Thanks

Any update on this, Shaon?
Thanks!

Thanks, Shaon. Unfortunately, the site is live and I had to roll back to version 3.3.8. I’ll have to use version 3.3.8 until the Amazon S3 plug-in is updated as all of my package files are stored on Amazon.

Hi Shaon,

Thanks for the reply. I understand that version 4.0 uses custom post types. I have no problem with updating the package IDs and re-enabling the password lock for each package. As I stated in my first message, my problem is that the ‘password lock’ feature is not working in version 4. I get the error ‘Wrong password’ when trying to download packages on the front end. Again, all password-locked packages work perfectly in version 3.3.8.

Do you plan making the Amazon S3 extension compatible with version 4?

If not, is there another way of adding files from Amazon S3 to packages without the Amazon S3 plug-in?