summaryrefslogtreecommitdiff
path: root/modules/user/controllers
AgeCommit message (Collapse)Author
2009-02-10Adding UI for site language selection and user language preference.Andy Staudacher
2009-02-10Line length fixBharat Mediratta
2009-02-04Use the matches validation rule in order to perform cross fieldTim Almdal
validation between the password and password2 fields
2009-02-04Complete the Recover Password functionality (Ticket #5).Tim Almdal
This change requires a reinstall in order to pick up the new hash field in the user table.
2009-02-04A preview of the password reset functionality. What's working... youTim Almdal
can start to logon, request the password to be reset, and an email is sent to the users email address. If you click on the link you get an unformatted form. But its a start :-)
2009-02-03Add a confirmation password input field that must match the primaryTim Almdal
password field in order for the update to succeed. If there is no data entered in the primary password field, the confirmation field is ignored. Addresses Trac Ticket #4
2009-01-29Fix lint errorsBharat Mediratta
2009-01-28Fully implement the user administration backend with drag/drop to addBharat Mediratta
users to groups.
2009-01-28Add drag and drop support to the admin_users interface. This is stillBharat Mediratta
a work in progress but it actually works mostly.
2009-01-25Undo the adding underscores to the id on forge generated formsTim Almdal
2009-01-24Supply a form id on all forms. This id can be used by modules otherTim Almdal
than the originating module to provide additional functionality to the form.
2009-01-22toggling of user edit panel works now.Jakob Hilden
added groups to the admin_user view, so you will eventually be able to edit users, groups and memberships on one admin page.
2009-01-15Changing t() placeholder syntax from {{replace_me}} to %replace_me.Andy Staudacher
2009-01-12Updated for new Form_Submit API.Bharat Mediratta
OLD: $form->submit("Foo") --> <input type="submit" value="Foo"> New: $form->submit("foo_button")->("Foo") --> <input type="submit" name="foo_button" value="Foo"> Mostly we don't care what the button is so we leave the name blank.
2009-01-10Big set of changes to comments, with related changes to akismet andBharat Mediratta
user modules. * Don't delete vars when we delete a module. This makes reinstalling a module a lot easier. * Add user::lookup() as the preferred way to load a user, so that other modules don't delve into the user module (that'd be a problem when we swap out user modules) * Notify site admins if Akismet is not fully configured * Bundle all server variables into the comment so that if/when we re-check the comment, we are not using the server info from the site admin's request. * Update Akismet to grab request context data from the comment * Pre-seed comment fields if we have a logged in user. Update comment::create() API to clarify it for this. * Delete comment::update(), that's a controller function. * Add url to User_Model * Add author_name() author_email() and author_url() to Comment_Model. It'll return the appropriate values depending on whether the comment was left by a logged in user or a guest. * Use resetForm() instead of clearForm() when we reload the comment form after ajax submit, this way we preserve the pre-seeded values. * In the user profile page, ignore blank passwords.
2009-01-08i18n refactoring: Rename all _() (reserved by gettext) calls to t().Andy Staudacher
- And refactor printf to our string interpolation / pluralization syntax - Also, a slight change to the translations_incomings table, using binary(16) instead of char(32) as message key.
2009-01-06Put up an error if you rename a user to an already existing name.Bharat Mediratta
2009-01-06Add a submit button to the login formBharat Mediratta
2008-12-29Remove rest::JSON content type; it's causing lots of problems and it doesn't ↵Bharat Mediratta
directly help since text/html works just as well for our JSON communications
2008-12-26Added content type to JSON output functionsFelix Rabinovich
2008-12-26User/Group administration cleanupFelix Rabinovich
2008-12-26Separate GET and POST in Group AdministrationFelix Rabinovich
2008-12-26Separate GET and POST in User AdministrationFelix Rabinovich
2008-12-26Login is 'info' not 'success'Bharat Mediratta
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-25Don't let the admin delete themselves, either. That would be bad.Bharat Mediratta
2008-12-25Only admins can delete users.Bharat Mediratta
2008-12-25Fix rules for editing users.Bharat Mediratta
2008-12-25Rest_Controller -> REST_Controller everywhere, for consistency.Bharat Mediratta
2008-12-25User administration: 1. Add users; 2. Group administration; 3. General cleanupFelix Rabinovich
2008-12-24Adding userFelix 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-24Tersify a log messageBharat Mediratta
2008-12-24Lots of deltas rolled up into a bigger change. Sorry for the mess.Bharat Mediratta
1) Deleted in-place-editing. We'll be replacing this with a real edit system that groups settings together and is more coherent. 2) Tweaked the way that dialog boxes work to get the ajax stuff working again. It's imperfect and does not work properly for uploading images. This is going to get redone also, but this is a good resting point. 3) Created edit forms for albums and photos. Moved _update and _create out of Items_Controller and into the individual subclasses. 4) Created access::required which is a shorthand for: if (!access::can(...)) { access::forbidden(); } 5) Added validation rules to Items_Model 6) Converted login to use the regular modal dialog approach in the theme.
2008-12-23Edit user - first draftFelix Rabinovich
2008-12-22Remove extraneous view, not necessaryBharat Mediratta
2008-12-21Add info/warning/error classes to log messages.Bharat Mediratta
2008-12-21Move logging up to the controllers so that our logging can operate at a more ↵Bharat Mediratta
meta level
2008-12-21Add a logging facility, and instrument login/logout to use it.Bharat 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