| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 809e52d80cbf3beb75b238fddb0da3951fb9a8e7.
|
|
Revert "Changed access::user_can to force the owner of an item to have"
This reverts commit 0b97cfd6f098be08be5f3cf1dbca1cce580ae330.
|
|
Revert "It helps to save before committing :-)"
This reverts commit 0d76d6fd77f53e9e92a9a013cd112c69217f3ceb.
|
|
|
|
|
|
view permission on the parent. Added a whitelist of allowable
owner permissions.
If the requested permission is view and the user requesting access
is the owner, check that they have view permission to the parent.
|
|
1) Change access_Core::user_can to return true for all permissions if the
owner is the specified user.
2) Change Item_Model::viewable to set the owner_id is the first view_restriction
This allowed simplification of the generating the where clause to a single
$this->orwhere instead of a where and an orwhere.
|
|
the album.
|
|
|
|
|
|
|
|
This required putting a wrapper view around the forms and passing
this view as the parameter to the item_edit_form event. The view
contains a $script variable that the modules can add script to be
included in the form html when rendered as part of the ajax response.
|
|
on the tag add form in the tag sidebar block. Updated the xss golden file as well. Still to do figure out how toget it into the edit popup dialog
|
|
|
|
|
|
|
|
Conflicts:
modules/gallery/helpers/access.php
|
|
|
|
Related to 719c59e0402464a0e2b14915f6d10218ff5d4729
(cherry picked from commit 831bf63c236fe88624470d2906729e035e9dbfc8)
|
|
(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
|
|
Related to 719c59e0402464a0e2b14915f6d10218ff5d4729
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
|
|
(cherry picked from commit 79a46658196a98a3972983cc422d1ee544b09d4a)
|
|
there's an error.
|
|
exception from View::render()
|
|
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.
|
|
|
|
|
