| Age | Commit message (Collapse) | Author |
|---|
|
Fixes ticket #566.
|
|
there's an error.
|
|
good pattern for allowing modules to add their own hooks to item forms!
1) Album, photo and movie forms now all use edit_item as the group and
we publish item_edit_form and item_edit_form_completed events which
makes it much easier in the module to handle all events. They can
still differentiate based on $item->type if they want to.
2) Added tag::clear_all() and tag::compact() functions which takes the
place of hiwilson's tag::update() function and is now used in
tag_event::item_delete(). This provides a simple API that allows
us to have a lot less event handling code. It's less efficient
than what hiwilson was doing before in that it will delete and
re-add tags, but if that ever turns out to be a performance issue
we can do something about it then.
|
|
functionality. (3)support multi-word tagging.
|
|
make a huge log file. In the l10n_client case, it's not really
necessary to know that level of detail and it makes for a weird API.
|
|
Fixes ticket #194
|
|
old ORM relationships from hanging around, which was causing problems
when doing MPTT manipulations (resulting in incorrect permission
propagation-- very bad!)
|
|
their new target. After each move, recalculate the permissions for
the new parent's hierarchy.
Fixes ticket #552
|
|
related events from within the model handling code. The only
exception to this currently is item_created which is challenging
because we have to save the item using ORM_MPTT::add_to_parent()
before the object itself is fully set up. When we get that down to
one call to save() we can publish that event from within the model
also.
|
|
1) The item_updated event no longer takes the old and new items.
Instead we overload ORM to track the original data and make
that available via the item. This will allow us to move event
publishing down into the API methods which in turn will give us
more stability since we won't require each controller to remember
to do it.
2) ORM class now tracks the original values. It doesn't track
the original relationships (no need for that, yet)
3) Added new events:
item_deleted
group_deleted
user_deleted
|
|
in the gallery helper. This will let us bump the version without
having to bump the gallery module number.
|
|
|
|
|
|
absolute within them. Moved css from quick.js to quick.css.
|
|
Change the wording for the sort order from "Default" to "Order Added"
|
|
Digibug print button into it. Right now, it doesn't display properly.
|
|
|
|
|
|
|
|
|
|
Gallery n as opposed any variants of this.
|
|
|
|
and then set the task to done, the state to error and the status message set
to the Exception Message.
|
|
stored in the persistant cache for 30 days. On the admin_maintenance page
there is a new link for completed tasks "browse log". Clicking this will
open a dialog box that has the the contents of the log displayed.
The user can then view the log and close the dialog, or press the save button
to download the log to their local machine.
|
|
item::description. In addition add p::clean or p::purify to places that
xss cleaning had missed (i.e. rss feeds)
|
|
approach using html::specialchars and purify uses HTMLPurifier to intelligently
cleanse the output fields. Use purifier for text and title fields where it is
likely that a user would enter html to format their data.
|
|
1. Because it makes sense.
2. As a quick fix - For some reason it wouldn't work properly anymore now with the HTMLPurifier lib
|
|
|
|
call HTMLPurifier->purify()
|
|
call HTMLPurifier->purify()
|
|
|
|
|
|
Conflicts:
modules/server_add/controllers/admin_server_add.php
|
|
an EMPTY_INPUT_FILE exception which we can then log and continue.
|
|
|
|
using the checklist in ticket #385.
|
|
truncate incoming_translations after this
update to get rid of bad messages in your DB.
|
|
scanner.
|
|
|
|
|
|
|
|
Conflicts:
modules/gallery/libraries/Theme_View.php
themes/admin_default/views/admin.html.php
|
|
Gallery_View base class from Theme_View and Admin_View.
1) Move all the theme specific jquery stuff from gallery_theme::head()
and admin_head() into the theme files. Use $theme->script() as
appropriate.
2) Get rid of the extra boolean on $theme->url() that we were using so
that we could call $theme->script($theme->url(...)) -- add
$theme->theme_script() instead (poorly named, but still clearer than
what we had before)
3) Fix the bug that combined scripts didn't work at all in the admin
theme.
4) Get rid of $theme->display() in favor of new View(...)
|
|
change).
Refresh the install.sql.
|
|
other gallery 3 tables. Update the driver to match, add more upgrader
code, update the installer block and change the gallery module version
to 6.
|
|
1) Drop the *_modified key, we don't really need it. The modification date is not
relevant to our browser caching strategy.
2) Fix multiple issues with the Expires header and just hardcode it to the biggest
possibly value for code clarity.
3) print the $content out directly instead of using fwrite
4) Minor cleanups in the installer.
|
|
ticket #485 and gives us the extra adavantage of not having to serialize the data (as the database driver handles that for us)
|
|
addition of the cache table.
|
|
|
|
1) Eliminate digibug_album.html
2) Get rid of the $(document).ready() in digibug.js and rename popUp() to
digibug_popup() then just make direct calls to digibug_popup() in the
menu urls.
|
