It should be fairly straightforward. Make sure you've read the
permissions section of the manual, and make sure that the administrator
has both view & edit permissions for the relevant models. As far as
"best practices" -- most of what you need to do should fit in the
permission functions. If you're doing it outside those functions, you
might not be doing it the "best" way. Not a hard and fast rule, though.
Bryan
MichelV69 wrote:
Hello, all
I'm writing an application that requires some extension of the user
model, including the ability of the "administrator" to be able to edit
accounts. Are there any "gotchas" or best practices that can be
recommended? There doesn't seem to be anything in the new Hobo book,
nor on the Hobo website.
Thanks, everyone!
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
