-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support real private files #9
Comments
I think we've generally done this using static resources -- although we're still on MODX 2.8.1, so maybe that breaks with the updates to file handling in 2.8.2 (or 3? I can't remember, but I know you do 😬) |
The static resource still has to be publicly accessible (for a download with the DigitalProduct extension) or you need to set up a usergroup for each unique product (related to #11). |
Ah, interesting. I guess I was thinking of a single purchase enabling multiple resources (and/or downloads) via usergroups. |
Already possible. :) |
Currently the files option requires files to be publicly accessible, as DigitalProduct will either redirect or download them through curl.
To allow private files to be restricted (htaccess, outside webroot, etc) and only allow them to be downloaded by the module if the appropriate products were purchased, a new download method needs to be added with readfile() or a media source integration.
The text was updated successfully, but these errors were encountered: