| Age | Commit message (Collapse) | Author |
|---|
|
|
|
- Propagate size limits (including detecting memory limits from GD) down to the
Flash so that we don't even start uploads that won't work
- Improve the error messages to be more user meaningful and provide links to the
codex for errors
- Tell the user up front what the file size limit is.
Fixes #1638
|
|
* Fixes #1628
|
|
|
|
Added a theme_info variable to the theme globals. The properties in the theme.info file are now contained in this theme_info structure.
Access is:
<?= $theme_info->author ?>
will display the theme author.
|
|
type, unset the combine_queue for that type entirely. This way future
calls to css() and script() emit an element until there's a new call
to start_combining(). Fixes 1685.
|
|
interact with the combine list ahead of time, and to be able to do things like
minification after it's combined. Fixes #1653.
|
|
|
|
the <html> element, including things like namespaces. Fixes #1615.
|
|
combining functions.
|
|
combined and when. Backwards compatible in that old themes will work,
but their CSS/JS will no longer be combined unless they make some
changes. Fixes #1600.
|
|
|
|
Allows for cleaner code and fewer function calls.
|
|
to be naturally ordered and case insensitive.
|
|
added spaces around =s
|
|
(that does 2 trips to Database server and is less optimal).
exists() method is not needed anymore thus got removed
|
|
rows or just 1. Is sufficient to return straight after reading 1 row.
|
|
|
|
Requires making Menu::get() return a reference. Fixes #1545.
|
|
|
|
deleting the first item row in the database. The root issue is a bug
in Kohana that's addressed in dca9b5f3fc8e80ee0667cac88d688e2287b1e7f4
but in this change we deal with the fact that reloading an item can
result in an instance of the item that's unloaded. In those cases, we
should just ignore it and move on. Fixes #1489.
|
|
Fixes #1417.
|
|
http://dev.kohanaframework.org/projects/kohana2/repository/revisions/4605
So now our cache entries don't expire. For now, do cache expiration
whenever we render Admin > Maintenance, since that's the type of place
that users will go when they want their cache to expire anyway.
|
|
- add_user_to_group and remove_user_from_group should take Group_Definition instances
to be consistent
- add_user_to_group and remove_user_from_group in drivers/IdentityProvider.php should
not be static
|
|
|
|
reply-to addresses to an empty string. The first time the user model is saved, set the sendmail from and reply-to addresses. Requires an update to gallery version 38.
|
|
file and store them as gallery module variables. Requires a version number bump to 37.
|
|
the final say. Fixes ticket #1315.
|
|
the l10n_scanner cannot parse it properly and drops those from the
localization list. Fixes ticket #1284.
|
|
This fixes ticket #973.
|
|
ticket #1228.
|
|
|
|
set in the db
|
|
links on the Admin > Maintenance page to allow you to turn it on and
off. This should be efficient since we cache all vars and look them
up on every request anyway.
This also allows us to have the Fix task enable maintenance mode while
it's running which greatly reduces the chances that somebody will come
along and hork the database while we're tinkering with MPTT pointers.
Fixes ticket #1259.
|
|
validation.
|
|
identity provider after we fail to set up a new one.
|
|
|
|
ticket #1199.
|
|
Instead of overwriting Kohana_Exception::handle() (which we were doing
in MY_Kohana_Exception) we instead use their existing template system.
gallery/views/kohana/error.php overrides system/views/kohana/error.php
and is the standard error template for all exceptions. Our version of
error.php figures out the appropriate view based on context (cli,
authenticated admin, guest viewing a 404, guest viewing a system
error) and delegates appropriately. Each delegated view has a narrow
responsibility.
This paves the way for us to add new error views per module. For
example, the rest module will define its own template in
Rest_Exception and then its exceptions can be rendered the way that it
wants (json encoded, in that case).
|
|
|
|
we specify the continue_url in the session, but we store it in the
login form so that we can propagate it across the session creation
that happens at login time.
|
|
- Pass the CSS selector of the active image in as an arg to site_menu
so that quick operations know what they're operating on.
- Change the ids from g-{photo,movie}-id to the generic g-item-id
- Initialize ajax handlers for site menu on the photo and movie page
- Drop the movie context menu, it's now in the site menu
|
|
security check. Not sure why the patch worked for some and not for
others, but this should resolve it either way. Fixes ticket #1123.
|
|
|
|
admin pages, just like in non-admin pages.
TODO: Set $view->page_title in the many admin controllers we have. I just set it for admin_maintenance.php to show how it's intended to be used. I copied the title from views/admin_maintenance.html.php to the controller.
|
|
passwords, hashes or personally identifiable information.
|
|
a recent refactoring / fix.
|
|
|
|
|
|
array from the Cache.
Until now, we loaded hundreds of translation messages row by row, and unserializing one by one at bootstrap time. That amounted to a significant percentage of the complete request time. This approach is more than 10x faster.
|
