| Age | Commit message (Collapse) | Author |
|---|
|
check to see if gettext is installed. The 3rd party library used in the exif module expects gettext to be available. Rather than doing all the time use the gallery ready event to only do it when it might be needed. Fixes ticket #672"
This reverts commit 33690a32bcf132e5ab470ff77ba23c073ac26271.
|
|
see if gettext is installed. The 3rd party library used in the exif module expects gettext to be available. Rather than doing all the time use the gallery ready event to only do it when it might be needed. Fixes ticket #672
|
|
|
|
Conflicts:
modules/gallery/views/l10n_client.html.php
modules/organize/views/organize_tree.html.php
modules/server_add/helpers/server_add_event.php
|
|
1.5 second counter only after we've done any expensive queries. This
guarantees at least some time to do work.
Fixes ticket #693.
|
|
views.
|
|
Adding SafeString::of_safe_html() calls where urls are passed as parameters to t() and t2().
|
|
the system's default table specification. Fixes ticket #597.
|
|
|
|
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
|
|
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
have a single exif_record for each item instead of 1 per key. It's
about 5x faster to scan photos this way.
|
|
|
|
(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.
|
|
chars
|
|
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().
|
|
|
|
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.
|
|
|
|
mirror the drupal pattern of using braces {}.
|
|
tag, search, comment and notification modules (Ticket #68)
(missed this one)
|
