We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 21257 MODX Staff
    • 730 Posts
    I think that the custom user settings are like that, except you don’t have different input types like textarea, checkbox, select.. it’s just key/value pairs. But immensely useful to be able to extend the user’s profile with custom fields programmatically. You can handle input/output for those in any way you wish.
      Mike Schell
      Lead Developer, MODX Cloud
      Email: [email protected]
      GitHub: https://github.com/netProphET/
      Twitter: @mkschell
      • 22303 MODX Staff
      • 10,725 Posts
      Quote from: therebechips at Jul 08, 2009, 11:45 AM

      But - would it be the case that each user would end up with a string of permissions like this: {"create":true,"remove":true,"save":true.... } ? Isn’t that somewhat redundant if many of the parameters are identical for different users?
      You wouldn’t have to repeat those permissions (or attributes) in your own custom policies for each user; assign those to the groups and just add whatever policy attribute you want to identify the unique permission you are giving the user. That said, if this is different for each and every user, it would make much more sense IMO to use a user setting; these are automatically available from $modx->config (and the new $modx->getOption() function that will replace direct access to $modx->config starting in MODx 2.1) and would avoid the need of having a Policy for each and every user in the system.
        • 37059
        • 368 Posts
        I realize this is an antique thread, but I'd like to bump it because the OP described my current needs exactly. Any further progress/new ways to accomplish this?
          Jason