Yes, this is also on my todo list đ
Hej Jannis
I updated it in RW Classic, but after restart it still says version 1.2 and I cannot find it in my folder. The version in the stacks folder are still 1.2.0 and the date created is 12 march 2022
Please try again with version 1.3.1, just available now. Please restart RW afterwards.
Tested on my side, works fine.
Yes I got the update 1.3.1 thank you Jannis, have a nice day :-)
Hi @jannis,
A quick question about UserAccess.
For the past year or so, Iâve been looking at a good way to authenticate different users and allow them to view data specific to them. UserAccess and Sitelok are on my short list. To be honest: thereâs not much else out there that I could add to my list, but still! ;)
One of my use cases is that a logged in user should have access to downloads that are specific to him/her. Users should NOT have access to each others files. The idea is that users can always go back to my site, log in and:
- view their invoices and contracts
- re-download the (ZIP) files theyâve purchased from me.
Since each file is tailor made for that specific user, and invoices are of course customer specific, I canât simply provide a one-download-link-for-all.
I understand the current way to do things is to either:
- build different download pages for each user, using UserAccess or Sitelok to make sure only the rightful user can access the download page in question;
- build one big download page that has download links to all files for all users, protect each link with UserAccessâ Stack Protect stack to hide them from users that are not the rightful owner of the content.
My question for you: If you have any tips on how this can be done more elegantly (read: with much less work for me :), Iâm all ears! I couldnât find a quicker way in the documentation.
It would be awesome if there was some sort of file access restriction stack in UserAccessâ bundle in a future version. Sitelok doesnât offer this and I think itâs a feature that would set UserAccess apart.
Cheers,
Erwin
H Erwin,
I think the integration with Repository Stack 2 (see the documentation) might be helpful here.
As soon as a UserAccess user logs in, he will be able to list only his files in Repository Stack.He wonât be able to list other user files.
Note: The link to the files themselves arenât protected. If youâre able to guess other users login name and file names, you might be able to spoof link to files. Therefore, giving your files a unique id most probably is sufficient to restrict the access. I think the same will be true for SiteLock.
Cheers
Jannis
Hi @Jannis
Thanks so much! i will have a look into Repository.
Cheers,
Erwin
@Jannis is it possible to use repository to provide a freely accessible download page, ie for an eMagazine or similar? I am going through all the documentation now, but not sure. If not, does anyone else have any thoughts please?
Yes, just donât use authentication, and make every setting read only.
Thank you for such a quick response, Iâll give this a go!