| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
new organize; it may be hanging around from a prior version. Reinstate
the installer for this. Bump organize module to v4. Follow-on for #1584.
|
|
makes sure that it depends on the REST module.
|
|
|
|
|
|
reversed. organize_dialog contains the stuff that pops up in the dialog,
organize_frame contains the stuff that's in the embedded iframe.
|
|
JavaScript library. It's got all the functionality from the Flash
version except it doesn't support creating new albums or uploading
photos.
Only tested in Chrome 10.0.x so far.
|
|
the l10n_scanner cannot parse it properly and drops those from the
localization list. Fixes ticket #1284.
|
|
the organize module to 2 in 8fb56abf034dd1f5c561e7af12bf6e097a3de6f6
|
|
a call to Organize with the appropriate album open. I have not yet
figured out how to get the SWF code to highlight the active image, but
that's coming. Partial fix for #1204.
|
|
REST module is active.
|
|
|
|
module is deactivated
|
|
|
|
|
|
|
|
2) Use CSS to layout the thmbnail grid to the full dialog size. Fixes ticker #848.
3) Separate css that can be themed into organize_theme.css. This isolates the themed components into a separate file for easy of overriding by a theme.
|
|
|
|
shared images from wind to lib. Deleted unused images in the admin_wind. This will likely break a few ajax features.
|
|
install() function if all you're going to do is to set the version of
the module from module.info into the database. This means that for some
simple modules, you don't need an install.php file at all.
|
|
|
|
|
|
|
|
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.
|
|
doesn't really do""
This reverts commit 397468c47b8fc3fefeb54ff19a73980ed1dd8c20.
|
|
really do"
This reverts commit a25f08d433d504a53763feb358a1aa7f5f798de6.
|
|
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 is the first step towards having a simple, lightweight and
unified API for module interaction.
|
|
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
|
|
This reverts commit 31ffb82382d76390f1206944329dde86c687349c.
|
|
Change the wording for the sort order from "Default" to "Order Added"
|
|
producing errors in the log.
|
|
|
|
|
|
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.
|
|
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.
|
|
rewritten by beta2, pull all of its "tenticles" back into itself and
out of core or tags module.
|
|
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).
|
|
|
|
|
|
make_album_cover() functions into it.
|
|
into the core helper. Clean up interactions so that when we remove an
album cover we pick a new one, or clean out the old album cover if
there are no other choices.
|
|
feature its provided for.
|
|
|
|
|
