Thank you for the reply, but as a nonprofit entity, I can’t really justify spending another $200 just to use the software in a dev environment. Most of our plugin vendors recognize the non production needs for a dev space and license to the domain, allowing dev. or test. to fall within that single license pricing.
I’ll look for some alternate options to allow us to offer downloadable files to our users. We don’t actually rely on any permissions or selling of the downloads, it’s just a document sharing function in our case.
So can I confirm that the frontend will not allow one user to delete other user’s packages? Based on the above exchange, are you enabling that feature with the developers, or simply making it not look like it is possible to delete?
What I mean is that that URL above, is the URL being used for the [download_url] variable. It does not seem to be pulling the actual file download URL.
I missed your earlier post about updating to 6.0.9, which I’ve just done and that seemed to resolve the auto-publish feature. However, per my other open ticket, the link is still broken on the download.
Yes, still having a problem as the File URL link doesn’t appear to reference an actual file on the page, though it does work in the template preview.
As I have a separate ticket open with you regarding the auto-publish uploaded files, I provided the user details there. Please let me know if you have any questions.
Tamra Dugan
Forum Replies Created