Hi all,
I am glad to release the new UserAccess Stack.
This stack is an authentication and authorization solution for RapidWeaver. You are able to create simple membership sites with this Stack.
It has also an integration with Repository 2. An integration with Poster 2 is currently in the works.
Wow just what I needed, thank you :-) Is it possible to lead different logins to different pages?
Itās a site wide authentication and authorization solution. So logged users are logged in site wide.
Taken on the fly, thanks for the discount.
Hej Jannis
What is the group setting? Can I create other groups? For example I have a login for workers in two different bakeries. The shop people need to see the exact same pages. Can I create a group called āshoppersonelā that will see the same page and another group called ābakersā that will see another page?
The group setting is just a comma separated string, where you are able to define the group names.
Just make sure not to use blanks in the names š
Exactly. Or see the same page with different content areas.
Newbie question - so when you say sitewide and Iām using a subdomain, does it go outside the subdomain for everything or just everything in the subdomain itself?
Just everything inside the subdomain.
Thanks - I have Page Safe (Joe workman Which can password protect something - can this be inside user access and password protest specific pages? Probably dumb, just curious :)
Should work together, yes.
Hej Jannis how about plug-in pages, how can we protect them with your stack?
Kind Regards
Kent
Well, itās Stacks plugin dependent. There is a lot of PHP involved.
Which plugin?
Formloom. But it has its own protection, but I am reading it into another page where people already are logged in. So it will be a hassle for people to make another login. But do not bother about it. I have formsnap also, and can easily redo it :-) Donāt want to waste your time, better use that for making more nice stacks for us :-)
BTW I am almost finished implementing UserAccess stack on our company site that has a lot of protected pages. It is really easy to implement once understanding how it works. I have 3 user groups now. Shop staff, bakers and administrators. It is also really fast to implement using Partials. So I am happy replacing the good old Lockdown plugin with these stacks. The only thing I am missing is the possibility to automatically lead different groups to different pages. Now I just give them the possibility, on the pages they login, to select the page they should go. Are they going to the wrong page, they will be lead to a āAccess forbiddenā page that will redirect them to the login page after a few seconds. I was thinking that maybe a redirect could be achieved when someone from a group login. I mean, if redirect from other groups is hidden by stack protect, then the one revealed could contain some sort of redirect? UPDATE, forget about it, it works with a redirect. That means I have most of the functions of the old Lockdown plugin. I can now automatically redirect people to the various pages they are supposed to login toā¦ very nice :-)
Exactly, that would have been my proposal also. I will include a redirect stack into UserAccess in the next update š
Keep the feedback coming, itās a brand new stack, so I am happy to hear about implementation use cases š
Yes, will do :-) Another very nice thing I discovered by using UserAccess is that on two pages, I have a production planning system, for the weekly planning of how much should be planned for the current week. This a very extensive system that produces production lists for each of the week days, with recipes and total use of ingredients etc. It is therefore off course very sensitive, cannot have people messing with those :-) These I have limited access to by manually protecting them with an obscure login system. This is now not necessary anymore since I now just use a Stack Protect stack with the relevant user group. That means the production planner just make his/her login and then automatically have access to those sensitive functions. Anyone else seeing these two pages do not have access to these functions. Also very nice, and an additional login is not necessary anymore. They are going to love this! It also means that UserAccess is more comprehensive than the obsolete Lockdown plugin.
Perfect example how I envisioned the usage of the UserAccess Stack. Thanks @Kent for sharing š
Iām finally getting a use for this on a live site, and itās really good. Once you did down into it, itās got a lot of great functionality.
Iām using it for a āguestsā section on a holiday letting site. Iāve been able to create unique sections and pages for each guest, with them having their own log-in details and able to see only the data that is relevent to them.
Good work Jannis.
Thanks Steve!
I will (relatively) soon add the functionality to create users online, so that you donāt have to add them inside Stacks.
Cheers!
That sounds excellent.
The ability to use an email as the log in would be great too. (I think we talked about that?).