| Age | Commit message (Collapse) | Author |
|---|
|
(cherry picked from commit c9017ae2f21ff8f5d745f296a636b80a30add6a1)
|
|
- DENY = false
- ALLOW = true
- UNKNOW = null (for intent only)
- INHERIT = null (for cache)
Upgrade is not included for now.
(cherry picked from commit 719c59e0402464a0e2b14915f6d10218ff5d4729)
|
|
|
|
|
|
theme. Because the theme comes first, this means that themes can
override any module resources, at the cost that we no longer have
namespacing for JS and CSS files.
The only file getting used outside of this model is
themes/default/screen.css which is used in the admin theme. I fixed
that by copying screen.css into admin_default and renaming its
screen.css to admin_screen.css. I also copied over all the images
that it was referencing.
Fixes tickets #48 and #539.
Theme API changes:
- theme_script(), theme_url() and theme_css() are no longer needed
- script(), url() and css() now refer to the first matching asset in
the module load path, where gallery3/lib is at the end of the path
|
|
|
|
groups from the session
|
|
specified permission to the item. Changed can to delegate to this method
passing in the active user.
|
|
menu items with view permission have somewhere to hang these menu items
from. If its empty it will get removed by $menu->compact()
|
|
from using a single gQuickPane <div> that we move around. A race
condition happens when you mouse over two thumbnails quickly.
Whichever server response loses the race gets displayed, and sometimes
it's the one that you're no longer hovering over.
Fix it by changing gQuickPane to be a class and creating a <div> per
thumbnail.
Fixes ticket #290.
|
|
the thumbnail to the movie and then showing it as a JPG. Fixes ticket
#570.
|
|
highly inefficient to me, so let's see if we can live without it.
|
|
Fixes ticket #566.
|
|
|
|
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
|
|
(cherry picked from commit 79a46658196a98a3972983cc422d1ee544b09d4a)
|
|
there's an error.
|
|
exception from View::render()
|
|
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
|
|
Fixes ticket #554.
|
|
zlib.output_compression=On
|
|
|
|
zlib.output_compression in PHP, since that means that the stream is
already compressed. Fixes ticket 555.
|
|
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
|
|
|
|
This reverts commit a333e01bd1c8cb3ad08cd0ad16023e3fcdfc4181.
|
|
|
|
09c9b1a75561881a40ada71f02710355923602e2
|
|
golden file.
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
|
|
Signed-off-by: Tim Almdal <tnalmdal@shaw.ca>
|
|
dig deep enough, but now we form the complete message using t() style
semantics to replace % placeholders with __ style JS placeholders.
Also, stop appending the (completed) text to existing messages.. roll
it together.
|
|
in the gallery helper. This will let us bump the version without
having to bump the gallery module number.
|
|
|
|
|
|
|
|
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.
|
|
|
