| Age | Commit message (Collapse) | Author |
|---|
|
Old API: $obj->original("field_name")
New API: $obj->original()->field_name
This allows us to revert the varous xxx_updated events back to passing
an original ORM as well as the the updated one. This makes for a
cleaner event API.
Old API: comment_updated($comment) { $comment->original("field_name") }
Old API: comment_updated($old, $new) { $old->field_name }
|
|
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
xxx_search helpers and into xxx_event helpers.
|
|
- DENY = false
- ALLOW = true
- UNKNOW = null (for intent only)
- INHERIT = null (for cache)
Upgrade is not included for now.
(cherry picked from commit 719c59e0402464a0e2b14915f6d10218ff5d4729)
|
|
|
|
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
|
|
test to make sure that we continue to do so.
This makes sure that we don't have problems with 5.3 which treats the
literal "on" as a boolean.
|
|
|
|
This reverts commit 5118afc959650469874733a1060fbe22364d8c28.
|
|
This reverts commit 6ac5238b83d58824eb9327406a2ee50b7e603214.
|
|
|
|
This reverts commit 31969a1d8211187e415eac51d155b4efded365f3.
|
|
|
|
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.
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
Add xxx_installer::upgrade($version) method so that upgrade stanzas
are separate from install stanzas. In the old code, to do an upgrade
meant that you had to re-evolve everything from the initial install
because we'd step through each version's changes. But what we really
want is for the initial install to start off in the perfect initial
state, and the upgrades to do the work behind the scenes. So now the
install() function gets things set up properly the first time, and the
upgrade() function does any work to catch you up to the latest code.
See gallery_installer.php for a good example.
|
|
|
|
|
|
gallery module. This type of mass update is prone to some small bugs.
|
|
|
|
Install: <module>_installer::install() is called, any necessary tables
are created.
Activate: <module>_installer::activate() is called. Module
controllers are routable, helpers are accessible, etc. The module is
in use.
Deactivate: <module>_installer::deactivate() is called. Module code
is not accessible or routable. Module is *not* in use, but its tables
are still around.
Uninstall: <module>_installer::uninstall() is called. Module is
completely removed from the database.
Admin > Modules will install and activate modules, but will only
deactivate (will NOT uninstall modules).
|
|
run faster. This fixes ticket #235.
Incidentally, refactor exif and search to use the same patterns
overall so that if you understand one, you understand the other and
they generally use the same strings for localization.
|
|
|
|
|
|
(thanks Romain LE DISEZ)
|
|
|
|
|
|
join it against the item table to find missing ids it's fast.
|
|
before stopping. This is *way* more efficient than just doing 2 per
request.
|
|
was no work left to be done. This fixes a divide by zero error.
|
|
E.g. "%link_startClick here%link_end" is now '<a href="%url">Click here</a>'.
Note: This isn't always the best solution. E.g. consider "Foo <a href='%url' class='gDialogLink'>bar</a>." Now the translator has to deal with
preserving CSS classes too...
|
|
|
|
prefix handling.
|
|
|
|
incidentally fixes the the problem that admin/maintenance tasks have
been broken.
|
|
specify a single type and ask for it appropriately in
admin_maintenance. Specify a type for every existing task.
|
|
being translated.
|
|
mirror the drupal pattern of using braces {}.
|
|
tag, search, comment and notification modules (Ticket #68)
|
|
|
|
|
|
|
|
user/group buttons and search form on search results page.
|
|
notification modules can do their thing. In addition, correct search
so it works properly and doesn't try to create an Item_id_Model class.
|
|
tell if there're any out of date records that need updating
|
|
that are missing matching items.
|
|
the index when items change.
|
|
|
