Albums CMS Design Principles: Difference between revisions
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
==See Also== | ==See Also== | ||
*[[Gallery Listings]] | |||
*[http://littledamien.com/docs/?p=636|littledamien.com: albums cms specs & principles] | *[http://littledamien.com/docs/?p=636|littledamien.com: albums cms specs & principles] | ||
[[Category:Albums CMS]] | [[Category:Albums CMS]] | ||
[[Category:CMS Documentation]] | [[Category:CMS Documentation]] | ||
Revision as of 00:22, 11 February 2012
AJAX
When adding a new album-based CMS section, the following files may need to be updated with the new content type:
/_classes/content/cache_class.php /_classes/content/resort_class.php
Obviously if a file includes the cache_class then the new content type will be available to that file.
PHP Classes
Classes derived from album_class and album_xpost_class that don’t have the same columns as those tables should set the db_field property value for those fields to FALSE in their class constructors.
$this->layout->db_field = false;
Listings
JavaScript/JQuery handlers
LITTLED.Gallery.bindAlbumListingsHandlers()
The routine above doesn’t handle content refreshes. The code below adds that, along with some filtering utilities. This can be rolled up into a routine available through the LITTLED.CMS library.
LITTLED.init({ setSortables: LITTLED.Gallery.bindAlbumListingsHandlers });
LITTLED.Gallery.keywordAutocomplete();
LITTLED.setSortables();
$('.datepicker').datepicker();
$('.update-cache').click(LITTLED.updateCache);