| Age | Commit message (Collapse) | Author |
|---|
|
default theme when I combined the CSS
|
|
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
|
|
|
|
test to make sure that we continue to do so.
This makes sure that we don't have problems with 5.3 which treats the
literal "on" as a boolean.
|
|
stored in the persistant cache for 30 days. On the admin_maintenance page
there is a new link for completed tasks "browse log". Clicking this will
open a dialog box that has the the contents of the log displayed.
The user can then view the log and close the dialog, or press the save button
to download the log to their local machine.
|
|
|
|
|
|
(and removed the commented out <img>)
|
|
|
|
discover
|
|
add the message to admin_default as
well.
|
|
|
|
|
|
%count variables.
|
|
to load them conditionally.
|
|
Conflicts:
modules/gallery/libraries/Theme_View.php
themes/admin_default/views/admin.html.php
|
|
|
|
$theme->theme_script().
|
|
Gallery_View base class from Theme_View and Admin_View.
1) Move all the theme specific jquery stuff from gallery_theme::head()
and admin_head() into the theme files. Use $theme->script() as
appropriate.
2) Get rid of the extra boolean on $theme->url() that we were using so
that we could call $theme->script($theme->url(...)) -- add
$theme->theme_script() instead (poorly named, but still clearer than
what we had before)
3) Fix the bug that combined scripts didn't work at all in the admin
theme.
4) Get rid of $theme->display() in favor of new View(...)
|
|
|
|
1) Simplify the admin settings page to what most of our users
want. Eliminate basic_ and default_ ids. We just have company_id
and default_id. Advanced users can use advanced settings for now.
2) Fix security in print_photos (didn't get it right in my last commit)
3) Use the regular thumb and full urls if the images are publicly
available to reduce load on the proxy.
4) Simplify proxy expiration code.
5) Eliminate all specialized styles from the admin theme.
|
|
gallery_theme::admin_head. This allows us to potentially manage the scripts like we do in g2 (single file and compressed)
2) Change Theme_View::_call to always call the gallery_theme::$function first.
|
|
2) Removed the tabs on the digibug admin page word count is now at 35.
3) Added a default link which resets the event and company id's to gallery's ids
|
|
2) Remove most of the marketing cruft on the admin pages
3) Change the name of the admin settings to just Digibug
4) Remove the "switch on mouseover" approach
|
|
|
|
Basically copied the default/views/pager.html to admin_default/views/pager.html
and change the message to reflect the original comment message.
|
|
|
|
* made only the block headers draggable, so that the rest of the block could be normal
* this should fix bug #292
|
|
more intuitive for themers.
|
|
|
|
|
|
|
|
Signed-off-by: Bharat Mediratta <bharat@menalto.com>
|
|
Internationalize the admin dashboard common title.
|
|
|
|
* added drag & drop help message for empty groups
* fixed overflow issue with more than ~10 members in one group
* CSS improvements
|
|
|
|
toggle, and forms to external files.
|
|
vars. We'll eventually turn this into a registry where you can edit
settings directly (at your own risk).
|
|
|
|
single quotes in JS.
|
|
toolkits
|
|
Change the text of the edit button to "close" if the panel is opened.
Reset the original text when the panel is closed.
|
|
directly wherever possible instead of access::csrf_token().
|
|
|
|
|
|
|
|
into each theme. I chose to create methods Theme_View::file($path)
and Admin_View::file($path). These methods check for a theme override
file in the theme and return a link to it if it exists. So to
override the themeroller files. just create a lib/themeroller in the
theme and the files will be picked up.
|
|
|
|
should be implemented in the tags module for now, and then possibly
generalized out to lib later on.
|
