We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 9207 ☆ A M B ☆
    • 2,475 Posts
    I’ve gone off the deep-end into the realm of permissions and contexts and access policies. So I’m trying to come up with a viable solution for a permission-heavy site. I’ll explain briefly:

    The idea is that the site will host many sub-sites, each of which is a log-in only area, but there are different permissions for each. So user [email protected] might have a "Head-Chef" role in one sub-site and "Dishwasher" role in another sub-site. Make sense?

    I know Revo can handle this type of situation via User-Groups and Resource-Groups. I’m wondering the following:

    1. Would it be cleaner to manage permissions if each "sub-site" was given its own context? Or would that be a total mess if we wanted the site administrators to have full access to each of the sub-sites?
    2. If we have a public login portal page (front-end), the page that loads on successful login will have to show all resources that a particular user has access to... do contexts introduce any surprises with listing resources? It seems as though I’ve already stumbled into something with WayFinder:
    http://modxcms.com/forums/index.php/topic,56230.msg322989.html#msg322989

    Thanks or any guidance!
      • 3749
      • 24,544 Posts
      The only advantage to using contexts, IMO, would be to avoid having to put new documents into resource groups (which you’d probably have to do anyway). It could certainly be done with out contexts and my rule is never use contexts unless you have a really good reason to do so. As you’ve discovered, not all the add-ons are up to speed on contexts.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting