| Age | Commit message (Collapse) | Author |
|---|
|
Kohana makes this type of transition fairly straightforward in that
all controllers/helpers/etc are still located in the cascading
filesystem without any extra effort, except that I've temporarily
added a hack to force modules/gallery into the module path.
Rename what's left of "core" to be "application" so that it conforms
more closely to the Kohana standard (basically, just
application/config/config.php which is the minimal thing that you need
in the application directory)
There's still considerable work left to be done here.
|
|
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).
|
|
back to our users in the edit permissions dialog.
|
|
|
|
I've missed any spots let me know.
|
|
organize feature.
2) Remove the tag functionality at this point
3) Added a callback to handle validating conflicting names (only used
by organize at this point.
4) Closes #231
|
|
the "add a photo" quick menu option.
|
|
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
|
|
page where we'll show whatever information is useful. Get rid of the
IN_PRODUCTION hack in MY_View.php that we no longer need.
|
|
|
|
is already denied. Ie, at the root level you can't click the item to
reset because there's no permission to inherit from, so denied is now
just a non-actionable status.
|
|
single query. In most cases, we were fetching 4-5 variables per page
load, so this is 2-3x faster.
|
|
|
|
the pane has the ui-state-disabled class
|
|
we can tell them what to do in the forums and we don't have to build
super smart admin UIs to help users with weird edge cases.
This plus r20789 is probably a good enough fix for #232.
|
|
vars. We'll eventually turn this into a registry where you can edit
settings directly (at your own risk).
|
|
|
|
|
|
uploader
|
|
|
|
|
|
|
|
|
|
toolkits
|
|
|
|
|
|
|
|
quickpane for albums) to be easier clickable and changed markup to use <ul> (more semantically correct)
|
|
is implemented. Can't do move easily because it's tricky to handle
the post-move redirect.
|
|
so that .JPG works on case sensitive systems like Unix. Also add
.jpeg to the list.
Fixes ticket #183.
|
|
the links work and it's more helpful.
In the process, rename the Presentation menu to be Appearance because
that makes more sense to me (and at least one other user who wrote
about it on -devel).
|
|
gets run at scaffolding::package() time, not on the target machine.
Instead, create a core module variable to trigger running
graphics::choose_default_toolkit() on the first admin login after install.
Fixes ticket #206.
|
|
|
|
|
|
directly wherever possible instead of access::csrf_token().
|
|
the task only has one step from zero to 100.
|
|
E.g. "%link_startClick here%link_end" is now '<a href="%url">Click here</a>'.
Note: This isn't always the best solution. E.g. consider "Foo <a href='%url' class='gDialogLink'>bar</a>." Now the translator has to deal with
preserving CSS classes too...
|
|
|
|
(the styling of the flash button is a not themable solution and I put the CSS in the file for now)
|
|
applied to quick pane rotate buttons. Hope that jQuery UI includes rotate icons eventrually so we don't have to maintain this.
|
|
|
|
- Get / verify API Key from l10n server
- Submit translations
- Fetch translations / updates
Reference: Tasks: 75, 76, 55
TODO: Move out of core (and a series of other tasks).
|
|
|
|
|
|
uploader. This is modeled on
http://codex.gallery2.org/Gallery3:Upload_UX but is not yet complete.
Notes:
* Changed #gProgressBar to .gProgressBar to support multiple progress
bars on the same page
* Added a bunch of CSS to the "needs a home" section in
themes/default/css/screen.css
|
|
|
|
if you're using mysqli, and it asks for a connection which we can't easily get
from Kohana.
|
|
|
|
We now have two clear and separate login approaches:
login/ajax
login/html
Choose the one that's appropriate. Totally simplified the maintenance
page to be separate from the theme and dead simple, and use login/html
approach there. Totally simplified the top level login
(login_page.html.php) to just be a login page, not the rest of the
chrome on the page and use the login/ajax approach there.
Don't use access::required in albums and then catch the exception,
instead use access::can and check the return code.
Improve the text for maintenance mode.
|
|
data creation and the packaging code. The rest ofthe functionality is
either no longer required, or moved to the developer module (MPTT
Tree).
Also provide checking for the active user to be an admin.
|
