| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
1) Controller::$input is gone -- use Input::instance() now
2) Handle new 'database.<default>.connection.params' parameter
3) Handle new 'cache.<default>.prefix' parameter
|
|
|
|
|
|
API a little clearer. Write a test for it, too.
|
|
|
|
variables were reversed
|
|
1) check that target and source are not the same.
2) check that the source is not already a child of the target (use to be a
descendant) Fixes #741.
|
|
out of the move for now.
|
|
whenever we expand a tree.
|
|
it right away while still allowing incremental tree loading.
|
|
up to the album that you're viewing, and if you move a photo to a
different album it'll reload the entire album tree.
|
|
|
|
slow down simple operations. We may run into problems with more
complex operations, but let's only add tasks into the mix when it's
clear that we need them.
|
|
* Clean up naming conventions for variables in the controller
so that we specifically refer to albums with $album_id, etc.
* Move complexity for drawing tree out of the controller and into
the view.
* Simplify task definitions to get rid of extraneous text
* Change __PLACEHOLDERS__ to clearly define which is the album
and which is the item that we're moving before/after
* Remove as many CSS ids as we can from the tree view to keep
things simple
|
|
change the sort order on the fly.
|
|
|
|
|
|
|
|
1) If images are dragged from the content pane and dropped on a branch in the
tree that the user only has view priviledges, then the drop is cancelled
and the images are reverted.
2) The user cannot click on a branch, to which they only have view priviledges,
the content pane does not change to the new album
|
|
direct sql update. This bypasses the gallery3 event mechanism. Fire a album_rearrange event when the rearrangement is complete
|
|
batch::start() method so notifications are queued
|
|
bypassing ORM and generating the sql directly.
|
|
the debug statements in until we can solve this issue.
|
|
showing. As well fixed a problem where selectable single clink no longer
worked when the album was reloaded.
|
|
visual feedback of the drop position between thumbnails, so this commit provides a checkpoint for trying various options
|
|
Organize_Controller:
* Remove unnecessary constants
* Rename index() to dialog()
* Simplify _get_micro_thumb_grid
organize.js:
* Move sizing code in here from organize_dialog.html.php
organize_dialog.html.php:
* Move CSS and JS links in here so that we only load them when we need them.
* Move sizing code into organize.js
organize_thumb_grid.html.php:
* Move pagination logic in here, since it's view centric
* Collapse the css class determination code and inline it
|
|
the events to populate the button bar.
|
|
|
|
plus/minus""
This reverts commit e37526f94df74a52a9cf36f0a5a5e641958ebbb3.
|
|
doesn't really do""
This reverts commit 397468c47b8fc3fefeb54ff19a73980ed1dd8c20.
|
|
really do"
This reverts commit a25f08d433d504a53763feb358a1aa7f5f798de6.
|
|
This reverts commit 869c3de9612a598dae0ce400991bdbe173a2decc.
|
|
icons. Branches with no albums, will not have an icon.
|
|
anything, but get the dialog up, populate the album tree and intelligently
populate the micro thumb grid.
Still to do:
1) get the microthumbs laided out ptoperly
2) expand and collapse functionality in the album tree
3) use the album tree to change the content of the micro thumb grid
4) Actually add some functionality
At the moment, it supports a callback "" to allow modules to add icons
to the organize drawer label. The close button is added outside of this
framework as it will always be last.
|
|
This fixes ticket #546
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
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
|
|
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.
|
|
using the checklist in ticket #385.
|
|
other data leaks.
|
|
and verifying user permissions, but there are several above-the-bar
changes:
1) Server add is now only available to admins. This is a hard
requirement because we have to limit server access (eg:
server_add::children) to a user subset and the current permission
model doesn't include that. Easiest fix is to restrict to admins.
Got rid of the server_add permission.
2) We now know check permissions at every level, which means in
controllers AND in helpers. This "belt and suspenders" approach will
give us defense in depth in case we overlook it in one area.
3) We now do CSRF checking in every controller method that changes the
code, in addition to the Forge auto-check. Again, defense in depth
and it makes scanning the code for security much simpler.
4) Moved Simple_Uploader_Controller::convert_filename_to_title to
item:convert_filename_to_title
5) Fixed a bug in sending notification emails.
6) Fixed the Organize code to verify that you only have access to your
own tasks. In general, added permission checks to organize which had
pretty much no validation code.
I did my best to verify every feature that I touched.
|
|
gallery module. This type of mass update is prone to some small bugs.
|
|
rewritten by beta2, pull all of its "tenticles" back into itself and
out of core or tags module.
|
|
can't edit, but we are getting closer :-).
This change sets up a framework for modules to contribute edit panels
to the organize drawer. Currently implemented General (albums and
photos), Sort Order (albums only) and Manage Tags
|
|
|
|
|
|
|
|
|
