Forum Replies Created
I just rolled back to 4.7.8 and it seems to have fixed the issue – I’d still like to update to the latest version at some point though so please let me know how to handle this. Thanks!
This seems similar to my issue, are you seeing any errors on your downloads pages? I see something like this:
Warning: Invalid argument supplied for foreach() in […]/wp-content/plugins/download-manager/libs/class.Apply.php on line 685
Yep, the Archive is working out just fine. Thanks for your help and quick responses!
Hello, I’m having a similar issue as above. I’m using User Role Editor, and I have a test user assigned to multiple roles. In a search result listing, I see only the packages associated with the primary user role, not the additional roles. When I look through the frontend archives ( using [wpdm-archive] ), I see the files I expect to.
Also, even though I’ve assigned my categories to be restricted to certain user roles, I’m assigning the access restriction again, directly on the packages, because…
If I create a package and assign it to a category that is restricted to certain user roles, and leave the “Allow Access” under package settings blank, it will not show up in search, but it will show when I browse in the archives.
I’ve tried disabling all plugins (besides WPDM, the directory addon, and User Role Editor) and switching my theme to the basic 2017 theme, and I still have the same results.
Using User Role Editor 4.46, latest WP version, and latest WPDM/directory versions.
To summarize:
In search listings, I only see the files related to my primary user role, and then only if I set the package setting “Allow Access” to include that user role. When I look through files in the archive listing, I see all the packages I expect – packages related to my primary and additional roles, and packages that are relying on the category-based access restrictions.
Any help is greatly appreciated! Thank you!
I’m having the same issue. I just disabled an install of WPDM Pro I had on a dev server and am attempting to use it on another server. It says my license key says invalid even though I can see in my account it’s paid through 2019.
I’ll need to move the site one more time before it’s live – is there a way I can handle this myself?