| Age | Commit message (Collapse) | Author |
|---|
|
|
|
use this as the default instead of id. This prepares the way for
manual reordering in the organize functionality.
|
|
directly wherever possible instead of access::csrf_token().
|
|
draggable user. Also, drag the icon and name not just the icon.
|
|
|
|
buttons, buttons!
|
|
icon doesn't appear within the button outline with buttons that aren't floated. Will have to debug later.
|
|
user/group buttons and search form on search results page.
|
|
user email address to list.
|
|
not list. Apply cursor: move to jQuery UI draggable and sortable. Clean up admin table styles a bit.
|
|
|
|
users to groups.
|
|
a work in progress but it actually works mostly.
|
|
|
|
|
|
it unique, changed gFirstRow to gHeaderRow to make more semantically meaningful. Fixed closing span that I broke after Bharat fixed it last night.
|
|
into a single set of reusable classes. Applied alternating row bg colors. Removed inline CSS from admin views. Moved user admin css into admin_default theme style sheet.
|
|
|
|
some of the logic.
|
|
into a single set of reusable classes. Applied alternating row bg colors. Removed inline CSS from admin views. Moved user admin css into admin_default theme style sheet.
|
|
|
|
added groups to the admin_user view, so you will eventually be able to edit users, groups and memberships on one admin page.
|
|
Panels are hidden inline elements that can be revealed within list items, tables cells, etc. Still need to add the toggle off and ajaxify content.
|
|
|
|
- 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.
|
|
legends, etc etc.
|
|
1) drop unnecessary semicolon
2) start with <?php for extra security in the case that the server itself doesn't
have short_tags enabled (the app won't work, but we need to make sure that we're
still secure)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
figure out how to share forms between user and admin editing.
Incremental improvement
|
|
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.
|
