| Age | Commit message (Collapse) | Author |
|---|
|
|
|
clearer what its purpose is. Add some spacing in the theme for it
so that it's less cramped.
|
|
|
|
|
|
relative_path_cache columns.
|
|
trailing hyphens.
|
|
|
|
we're not relying on overriding url::site() to do tricks around item
urls. This means that you won't get item urls by doing
url::site("albums/37"), for example, but it also means that we won't
get pretty urls where we don't expect them (like in the action of a
<form> element).
Incidentally, this will help us move over to using the slug format
because if you've got a bad character in a url, the edit forms will
now work on it since they'll be id based.
|
|
|
|
|
|
code in get_item_from_uri() by using relative_url() instead of
relative_path().
|
|
validation for the fields.
|
|
|
|
|
|
|
|
|
|
component for that given item. Album hierarchies are represented by
nested slugs. By default, we convert the filename to a slug when you
create an album, photo or movie.
|
|
|
|
(And the tests should illustrate that kohana 2.4's API doesn't quite fit our purpose of simply getting the best match between the accepted (client) and the installed (g3) locales.)
|
|
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.
|
|
request::accepts_language() when we upgrade to Kohana 2.4
|
|
and check the browser's / OS' locale preferences.
Ticket 582.
|
|
instead it throws an exception if there's a problem. The normal case
for graphics::generate is that it's going to succeed. It'll only fail
if something un-handleable went wrong, so just use the resulting
exception.
|
|
support it, this causes crashes as soon as you try to use it, which
breaks a bunch of our tests. Also, give the user some idea that
sharpen() is missing in the UI. Fixes #689.
|
|
of the root album (which has no visible album cover, so no point in
offering that option). This fully resolves #705.
|
|
|
|
think there's something better in the jQuery UI themeroller set.
|
|
|
|
|
|
Conflicts:
modules/gallery/views/l10n_client.html.php
modules/organize/views/organize_tree.html.php
modules/server_add/helpers/server_add_event.php
|
|
|
|
delimiters) instead of just the string contents.
Benefits: Using json_encode(), which is very robust. And as a user, it's clearer how to use this API compared to what it was before.
|
|
views.
|
|
instead of SafeString directly.
|
|
|
|
that we generate when resizing.
|
|
Adding SafeString::of_safe_html() calls where urls are passed as parameters to t() and t2().
|
|
1) increased gallery module version to 11
2) added image_sharpened parameter to the gallery module
3) sharpen all resizes.
|
|
Conflicts:
modules/akismet/views/admin_akismet.html.php
modules/comment/helpers/comment_rss.php
modules/gallery/helpers/gallery_rss.php
modules/gallery/libraries/I18n.php
modules/gallery/views/permissions_browse.html.php
modules/gallery/views/simple_uploader.html.php
modules/info/views/info_block.html.php
modules/organize/controllers/organize.php
modules/organize/views/organize.html.php
modules/organize/views/organize_album.html.php
themes/default/views/album.html.php
themes/default/views/movie.html.php
themes/default/views/photo.html.php
|
|
SafeString::purify().
Removing any p::clean() calls for arguments to t() and t2() since their args are wrapped in a SafeString anyway.
|
|
SafeString::purify() and SafeString::of_safe_html().
Removing SafeString::mark_html_safe() since it's no longer needed.
|
|
|
|
is not working.
|
|
Benefits:
- url::site() is often used in views and we can ensure in the url class that returned strings are indeed safe for use in HTML. Makes the list of vars of unknown safety status shorter.
- url::site() is often used as message parameter to t() and t2(). The parameter would be HTML-escaped if it wasn't marked as safe HTML already. Makes the usage simpler / shorter.
|
|
of ticket #537
* removed start/stop translation menu items from the admin, since they are on the languags admin page now
|
|
Refactoring of Xss_Security_Test.
t() and t2() return a SafeString instance.
TODO:
- Update all code to use SafeString where appropriate.
- Update golden fole of Xss_Security_Test
- Stop reporting CLEAN vars in Xss_Security_Test
|
|
change the sort order on the fly.
|
|
* Order Added => Manual
* Capture Date => Date captured
* Creation Date => Date uploaded
* Updated Date => Date modified
Set the default sort order to "created" which mimics what we had
before, expt that it is not manual.
|
|
a BMP masquerading as a .jpg causing us to be unable to rebuild
resizes and thumbnails. Now if that happens, we discard the file, log
it and move on.
|
|
the system's default table specification. Fixes ticket #597.
|
