summaryrefslogtreecommitdiff
path: root/modules/user/controllers/admin_users.php
AgeCommit message (Collapse)Author
2008-12-26User/Group administration cleanupFelix Rabinovich
2008-12-26Separate GET and POST in User AdministrationFelix Rabinovich
2008-12-26Group AdministrationFelix Rabinovich
2008-12-26User Administration. Add users. Take 3Felix Rabinovich
2008-12-26User Administration. Delete users. Take 3Felix Rabinovich
2008-12-26User Administration. Edit users. Take 3Felix Rabinovich
2008-12-25Rework log and message helpers to be parallel, but separate.Bharat Mediratta
1) they now have their own matching severity constants 2) they both have convenience functions success(), info(), warning() and error() 3) they both have severity_class()
2008-12-25Return the form on success so that we clear out any prior error formsBharat Mediratta
2008-12-25Ajaxify 'add users'Felix Rabinovich
2008-12-25fixes in user edit and deleteFelix Rabinovich
2008-12-25fixed minor log:add typoFelix Rabinovich
2008-12-25get_add_form() -> add_add_form_admin()Bharat Mediratta
2008-12-25Big round of normalization of the way that our controllersBharat Mediratta
communicate. Almost all controllers now use JSON to speak to the theme when we're dealing with form processing. This means tht we only send the form back and forth, but we use a JSON protocol to tell the browser success/error status as well as the location of any newly created resources, or where the browser should redirect the user. Lots of small changes: 1) Admin -> Edit Profile is gone. Instead I fixed the "Modify Profile" link in the top right corner to be a modal dialog 2) We use json_encode everywhere. No more Atom/XML for now. We can bring those back later, though. For now there's a lot of code duplication but that'll be easy to clean up. 3) REST_Controller is no longer abstract. All methods its subclasses should create throw exceptions, which means that subclasses don't have to implement stubs for those methods. 4) New pattern: helper method get_add_form calls take an Item_Model, not an id since we have to load the Item_Model in the controller anyway to check permissions. 5) User/Groups REST resources are separate from User/Group in the site admin. They do different things, we should avoid confusing overlap.
2008-12-25User administration: 1. Add users; 2. Group administration; 3. General cleanupFelix Rabinovich
2008-12-24Normalize our Admin controllers so that functions always print outBharat Mediratta
their results, as opposed to having them return their view back upstream. This is a little more code in every controller, but it's much less magical and more consistent. Look up the active_theme and active_admin_theme inside the view itself, no need to do that in the controllers. This makes view initialization easier in the controllers.
2008-12-22Remove extraneous view, not necessaryBharat Mediratta
2008-12-19Implement admin user editing. It's still very rough. Trying toBharat Mediratta
figure out how to share forms between user and admin editing. Incremental improvement
2008-12-19Create a new pattern for Site Admin controllers:Bharat Mediratta
1) They must all start with "admin_". This pattern is not directly routable. 2) Their urls must be /admin/xxx. 3) The Admin_Controller will take the xxx and look for Admin_Xxx_Controller and will delegate to that admin controller, after doing security checks. Moved the users and dashboard views into individual modules for now.