I'm just getting started with my first serious auth-based implementation of social-networking functionality. Here's a dumb newbie question: - How do I add an image to the auth_group table? - What would be the recommended way to segregate my app administrative groups, like super_user, from groups defined by my user community? Should this be done by a naming convention?
There's a lot about auth in doc 2.0, and yet, I'm finding that I've only been able to make some headway on my app by: - searching past posts to this group, - reading and re-reading and re-reading the doc for any and all clues, - going to the appadmin to find out the names of all the fields in the various auth tables, such as auth_group and auth_permission. I believe future doc would be well served by adding some more meat to the auth section. And here I go again ... I'd like to see a reference be developed that lists all the various attributes of the tables in auth with lots of links to various examples. This, of course, in addition to reference entries for all of web2py's capabilities, with description, usage, exceptions, and linked examples. I know this is a lot of work, but it would mean that Massimo would spend less of his formidable talent answering dumb newbie questions like mine and have more time to work on T10. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
