| Age | Commit message (Collapse) | Author |
|---|
|
available to themes that want to use it. It should probably
eventually be generalized away from just being for full sized images,
but it's a step in the right direction.
Fixes ticket #427.
|
|
so that right clicking works.
Turn the full size rendering code into a function and call it with
arguments, instead of creating a hacky named data structure to hold
the info.
Further partial fixes for ticket #427.
|
|
Partial fix for ticket #427.
|
|
|
|
|
|
|
|
|
|
that we might want it to appear more than once in views.
|
|
image. There's no security hole here, it's just a bad user
experience.
|
|
we use in albums
|
|
|
|
debugging
|
|
100%. Think this is a jQuery UI CSS issue and I haven't figured out an override for it yet.
|
|
layout.
|
|
|
|
link.
|
|
|
|
an abstraction for when we add movie support.
|
|
classes to newly added span classes in the pager templates directly, will likely move these out and apply through ui.init.js later.
|
|
- And refactor printf to our string interpolation / pluralization syntax
- Also, a slight change to the translations_incomings table, using binary(16) instead of char(32) as message key.
|
|
back to below the photo.
|
|
1) drop unnecessary semicolon
2) start with <?php for extra security in the case that the server itself doesn't
have short_tags enabled (the app won't work, but we need to make sure that we're
still secure)
|
|
next/prev sib if one didn't exist. (that's what we were supposed to
be doing in the first place, anyway)
|
|
|
|
grotty looking stuff in themes.
|
|
interface.
|
|
1) Deleted in-place-editing. We'll be replacing this with a real edit
system that groups settings together and is more coherent.
2) Tweaked the way that dialog boxes work to get the ajax stuff working
again. It's imperfect and does not work properly for uploading images.
This is going to get redone also, but this is a good resting point.
3) Created edit forms for albums and photos. Moved _update and _create out
of Items_Controller and into the individual subclasses.
4) Created access::required which is a shorthand for:
if (!access::can(...)) {
access::forbidden();
}
5) Added validation rules to Items_Model
6) Converted login to use the regular modal dialog approach in the theme.
|
|
|
|
|
|
search to header_top. Reduced borders. Started album grid improvements. Minor white space improvements. Still need to handle text/photo alignment in album grid, improve placement of search.
|
|
site menu
|
|
Updated album/item view icons.
|
|
|
|
|
|
|
|
"Options" menu placeholder to display item options (add, edit, subscribe, permissions, etc.). Renamed gAlbumHeaderMenu to gItemMenu which can be used on both album and item views.
|
|
so that they don't push the album grid down.
|
|
|
|
|
|
$theme->block_type() so that the themer has a consistent interface.
Also added a bunch more callbacks and normalized the names so that the
module author has plenty of options for where stuff gets put on the
page. Especially renamed album/photo/sidebar to be album_blocks()
photo_blocks() and sidebar_blocks() to make it clear that those are
going to be larger content sections and not just basic insertion
points.
Used __call() to collapse all functions in the theme, which
incidentally makes it trivially easy to add a new insertion point.
|
|
|
|
Removed unused CSS. CSS format updates. Applied jQuery tab styles to gSiteMenu. Removed gBlockHeader, all we need is a good old h3 element for a heading.
|
|
|
|
and also allow modules to contribute blocks to the layout.
|
|
|
|
slideshow link and button text. The slideshow link will only show up if the slideshow module is installed.
|
|
|
|
implementation yet
|
|
try to display a comment if it is not installed
|
|
1) Changed the way that we get forms. Now, if you want to get a form
for a REST resource you prefix /form to the resource id. So:
/form/photo/1 : returns a form for editing photo id 1
/form/comments/1 : returns a form for adding a comment to photo id 1
/form/comment/1 : returns a form for editing comment id 1
2) Changed the comment module to have two controllers:
comment: deals with a single comment resource
comments: deal with collections of comments attached to an item
Related stuff:
- Moved the comments js into the theme
- Reworked Comment_Helper for clarity
- Moved form generation code down into Comment_Helper
- Cleaned up routes (eliminating new comment ones added in recent rev)
- Added form() function to all REST controllers
- Changed comment module to use a block instead of an arbitrary helper call from the theme
- Comment controller only returns HTML currently, but returns a 201 Created status
code when a new comment is added, which the Ajax code can catch and act upon.
- Got rid of a lot of extra views in comment module
|
