ahhhhhhh, ok, all clear now,
and I am getting a little off subject here (just a tiny bit ) but I remember an extra called member check which could resolve some of those issues you helped me with as far as presenting custom pages to certain users, but it’s not offered in package manager anymore, and the version of revo it’s compatible with is the old 1.9, is it discontinued? There is no link to a support thread. I thought it would be perfect to use with personalize.
In my old evo install I used the old personlize snippet with a trusted if statement using username to determine which chunk to use, but boy was that a hassle.
and I am definitely going to get back to that one solution we were working on, but the site I am working on now is for a client and they just need pages set up for employees not clients so it’s much more manageable and they would have to add chunks and such.
There are a number of ways to approach this in Revo:
- ACL entries and resource groups
- Personalize snippet
- Custom permission added to a policy and checked by a snippet or plugin using hasPermission()
- User setting checked by a snippet or plugin using getOption()
- User groups and a snippet or plugin using isMember()
- Output modifiers in tags using :memberof
Things to think about:
How often will the system be changed/reorganized?
How often new users and new restricted content will be added?
How comfortable are you with the various methods?
How does the method selected interact with the three questions above?
;)
