Age | Commit message (Collapse) | Author |
|
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
|
|
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.
|
|
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
|
|
|
|
|
|
whitespace changes.
|
|
This change had unintentional whitespace changes. Reverting for now, will reapply it.
This reverts commit c65bfb5a10b125b2cf04ebd5c5d1b58051281f8c.
|
|
Tracking vendor ticket: http://bit.ly/16b7Zj
|
|
4943103700332a11f16319496e485cfd7fd9e36a
Get rid of vestigial third column in exif::_keys().
|
|
hiwilson.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
ticket #235.
|
|
|
|
|
|
|
|
http://www.zenphoto.org/trac/ticket/1117
http://www.zenphoto.org/trac/ticket/1118
|
|
|
|
|
|
have a single exif_record for each item instead of 1 per key. It's
about 5x faster to scan photos this way.
|
|
http://gallery.svn.sourceforge.net/viewvc/gallery?view=rev&revision=13422
it was commented out in the ZenPhoto version. Filed upstream ticket
about this:
http://www.zenphoto.org/trac/ticket/1118
|
|
|
|
calls to this function, this is a 1-2x order of magnitude performance
improvement.
|
|
(thanks Romain LE DISEZ)
|
|
this is a great solution, but it'll probably cut down on a big class of errors opportunistically
|
|
|
|
- Add a "captured" column to the items table.
- Pull the DateTime EXIF field and put it into the captured column
- Pull the Caption EXIF & IPTC fields and put them into the description
field if there was not already a value there
|
|
appropriate. This allows us to switch the exif value column back to
varchar and improves the way that we deal with non-utf8 data in our
embedded EXIF/IPTC data.
|
|
svn merge -r20638:20640 vendor/exifer/modified trunk/modules/exif/lib
|
|
chars
|
|
fread: Length parameter must be greater than 0 in file modules/exif/lib/makers/gps.php on line 197
Filed upstream as:
http://www.zenphoto.org/trac/ticket/1108
|
|
cases and it slows down inserts.
|
|
binary data embedded in places like the EXIF caption field
|
|
|
|
|
|
|
|
|
|
|
|
many separate queries.
In the process, rip out the summary column, we weren't using it.
Clean up the test, and drop the exif_records database on uninstall.
|
|
directly wherever possible instead of access::csrf_token().
|