| Age | Commit message (Collapse) | Author |
|---|
|
both the sidebar and the center content area from a dropdown at the
top of the dashboard sidebar.
|
|
admin.html.php looks for $sidebar and renders the page appropriately
if one exists. But only admin_dashboard has one currently.
|
|
hover over a toolkit it changes color and your cursor becomes a
pointer. Clicking changes the toolkit.
|
|
and then thumbnails for all the other available themes. If you select
one of the other available themes, it gives you a preview pane where
you can look at either the main page or the site admin page with the
new theme, then choose to activate it if you like it.
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
themes yet
|
|
- 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.
|
|
|
|
akismet if it's on. Force it on in the scaffolding so that we don't
try to run all comments we add from there through Akismet.
|
|
can do comparisons
|
|
page.
|
|
|
|
|
|
Introduce a "show" parameter which contains the id of the item that we
want to show when we go to the parent's page.
|
|
|
|
Implement image rotation this way.
|
|
|
|
|
|
|
|
|
|
|
|
right now, it doesn't allow you to reset to inherited values. That's
next.
|
|
|
|
up the tree
|
|
next/prev sib if one didn't exist. (that's what we were supposed to
be doing in the first place, anyway)
|
|
grotty looking stuff in themes.
|
|
interface.
|
|
|
|
yet, but it shows you which items have locked view perms.
|
|
|
|
the isAdmin bit at creation time.
|
|
toolkit we use. We only allow users to use one toolkit. The UI needs
work!
|
|
directly help since text/html works just as well for our JSON communications
|
|
|
|
|
|
admin more control. You can now track running tasks, resume stalled
tasks, cancel running tasks, and remove finished tasks.
Added graphics::compose() as a placeholder for future watermark
operations.
Added CSRF protection to maintenance urls.
|
|
the database. They're started with admin/maintenance/start/[task_name]
which sends down some JS/HTML which regularly pings the task at
admin/maintenance/start/[task_id] until its done.
The UI is still very rough. It works, though!
|
|
|
|
|
|
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()
|
|
into Admin_Controller::__call() again
|
|
invalid left/right pointers.
|
|
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.
|
|
|
