Skip to content
Boilerplate image gallery block that makes is easy(er) for designers to add a jquery / javascript slideshow, slider, gallery, etc. to a website.

README.md

Concrete5 Designer Gallery

Boilerplate image gallery block that provides all of the back-end code (add/edit dialog and controller) so you can focus on implementing the front-end slideshow, slider, gallery, etc.

For a tutorial on how to use this to build a Flex Slider block, see: http://c5blog.jordanlev.com/blog/2011/12/build-a-slideshow-block/

Installation

Download this code by clicking the "Zip" button above. Unzip the downloaded file and move the entire designer_gallery directory into your site's top-level packages directory. Then log into your site and go to Dashboard -> Add Functionality. Click the "Install" button next to "Designer Gallery".

Note: to enable image links, you'll want to install Mnkras's free Page Selector Attribute addon *before** installing this gallery).*

Customization Steps

This package provides a backend / editing interface, but it is up to you to provide the front-end. The general steps involved are:

  1. Uninstall the package via Dashboard -> Add Functionality. We must do this because we are about to rename the package (and its block), which you never want to do while it is installed -- that would result in Concrete5 errors.
  2. Rename the designer_gallery package directory and block directory as needed (should be the lowercase_and_underscore version of your block's name -- for example, "My Awesome Gallery" would get a directory name of "my_awesome_gallery" for both the top-level package directory and the block directory under the package's blocks directory).
  3. Edit the package controller.php file:
    • Change the class name to be a TitleCaseWithNoSpaces version of the package name, followed by Package -- for example, "My Awesome Gallery" would get a class name of MyAwesomeGalleryPackage.
    • Change the package handle ($pkgHandle) to the lowercase_with_underscores version of the package name (the same as the package directory name).
    • Change the return values of the getPackageName() and getPackageDescription() functions.
  4. Edit the block's controller.php file:
    • Change the class name to be a TitleCaseWithNoSpaces version of the block name, followed by BlockController -- for example, "My Awesome Gallery" would get a class name of MyAwesomeGalleryBlockController.
    • Change the table name to bt followed by the CamelCase version of the block name -- for example, "My Awesome Gallery" would get a table name of btMyAwesomeGallery.
    • Change the block name and description. It is recommended that the name correspond with the directory and class names, but this is not a technical requirement (just avoids confusion).
  5. Edit the block's db.xml file so the table name matches what you set in the block controller.php.
  6. Optional: Replace the package's icon.png file with your own icon (should be a 97x97 PNG with rounded corners, called icon.png).
  7. Optional: If you want to allow images to link to another page on your site when clicked, you'll need to install Mnkras's free Page Selector Attribute addon before re-installing the package in the next step.
  8. Install the package via Dashboard -> Add Functionality.
  9. Implement the front-end.
    • Put all of your required javascript files into the block's top-level js directory.
      • NOTE: Do *not** put the base jQuery library in here -- Concrete5 loads this automatically on every page already so if you add it here, it will get loaded twice and cause conflicts and errors on the page.*
    • Put all of your required css files into the block's top-level css directory.
    • If a stylesheet utilizes background images, place those in the block's top-level images directory, then tweak the css so image paths point to that images directory -- e.g. url(../images/example.png)
      • NOTE: Do *not** put the images that will be displayed in your gallery/slideshow/slider/fader here -- those will be chosen by the user when they add this block to a page.*
    • Modify the block's top-level view.php file to generate the proper html needed for your gallery/slideshow/slider/fader, as well as the javascript initialization code (as per your jQuery library's instructions). This is the hard part! It can often require tweaking the CSS that came with your gallery/slideshow/slider/fader. See the next section for additional help.

Customization Notes, Tips, and Gotchas

Some things to watch out for when building your own slideshow:

  • The package requires Concrete 5.4.1 or higher (primarily because you couldn't specify the order of files in a file set before that version).

  • When building your own template, it's best to append the block ID to an element's id (for example, <div id="gallery<?php echo $bID ?>">) because otherwise your javascript will break if the user adds more than one of these blocks to the same page.

  • Along similar lines, you should only use id's to refer to elements from javascript -- for CSS styles you should stick to classes instead, because there may be more than one of these blocks on a page.

  • If the javascript animations for your gallery are getting in the way of editing the page, you can disable it while in edit mode by putting a php "if" statement around your initialization script, for example:

    <?php if (!Page::getCurrentPage()->isEditMode()): ?>
    <script type="text/javascript>
    ...
    </script>
    <?php endif; ?>
    
  • Some javascript/jquery image galleries have an option to automatically crop or resize thumbnails -- if so, it's probably better to disable this and handle it with C5's built-in thumbnailing instead, as performance will be better that way.

  • I believe Concrete5 auto-loads js and css files in alphabetical order, so if you have more than one js or css file and need to load them in a specific order, you'll have to rename them to force the proper order.

  • IE "filters" in css won't work if they refer to images with paths (because unlike image url's, those paths are relative to the page, not to the css file). There's a workaround that involves adding code to the controller, but it's a bit messy (let me know if you need it).

  • If site exists in a subdirectory (for example, http://example.com/myc5site/), your stylesheets won't be loaded the very first time the block is added to a page -- but all subsequent page views will be fine so this is not a major problem, just something to be aware of when editing your site.

Titles, Captions, Links

All meta-data about images must be managed through the dashboard File Manager.

Titles and Descriptions are set via file "Properties" in the File Manager (click on an image, choose "Properties" from the popup menu). Note that Concrete5 sets the Title property to the file name when files are first uploaded, so if you want to use titles in your template you might want to change these.

Reordering the images can be done by clicking the "Sets" tab above the file list in the File Manager, clicking on the appropriate File Set name, and dragging-and-dropping the icons around.

When this package is installed, it will check to see if you have the "Page Selector Attribute" addon installed -- and if so, a new "Gallery Link To Page" file attribute (property) will be created that lets users choose a page that the image will link to when clicked from the gallery. If you didn't have the "Page Selector Attribute" installed when you installed this package, and want to install it now so you can use the image link feature, either uninstall and re-install the package after installing the "Page Selector Attribute", or follow these steps:

  1. Install the free Page Selector Attribute addon from the marketplace.
  2. Allow the new attribute type to be associated with files by going to Dashboard -> Sitewide Settings -> Attributes, and checking the box under the "File" column for the "Page Selector" row.
  3. Add a new "Page Selector" attribute: go to Dashboard -> File Manager -> Attributes, find the "Choose Attribute Type" dropdown at the bottom, choose "Page Selector" from the dropdown menu, click the "Go" button. Enter "gallery_link_to_cid" (no quotes) for the handle, "Gallery Link To Page" for the name, and leave the "Searchable" checkboxes unchecked. Then click the "Add Attribute" button.

Back-End Configuration Options

You (as the designer / developer) can choose whether to show end-users the "large image" resize controls, the "thumbnail image" resize controls, both, or neither. Do this by setting the $showLargeControls and $showThumbControls variables in the block's controller.php file. For example, if you are creating a slideshow for which you don't show thumbnails, you can hide the thumb controls so the user doesn't see them and get confused. Another example is if you always want your gallery to show full-size images (without any resizing or cropping), you can hide both sets of controls, so the user only chooses a file set and a display order, but nothing else. Another option is if you are creating a very specific design for your gallery and you want to "hard-code" the width and height of the images (you do not want to give the user the ability to change these settings). This can be achieved by disabling both sets of controls, and setting the desired "hard-coded" values for width/height/etc. in the block's controller defaults (e.g. $defaultLargeWidth, $defaultThumbWidth, etc.)

Size / Cropping Notes

  • Images will never be scaled up in size (i.e. an image smaller than the given size settings will not be enlarged).
  • If cropping, the width and height determine the exact size of the resized image.
  • If not cropping, the image is resized proportionally, so width and height determine the maximum possible size.
  • Setting a width or height to 0 means "ignore this size in our calculations" (as opposed to "make this invisible"):
    • if cropping, setting one dimension to 0 means that only the other dimension will be cropped.
    • if not cropping, setting one dimension to 0 means that the image will be scaled down proportionally according to the other dimension.
    • if both width and height are set to 0, resizing/cropping will be disabled for that size. (Do this if you're not using a particular size of image in your template, for example if you are not displaying thumbnails in your gallery, disable them by setting $thumbWidth and $thumbHeight to 0.)
Something went wrong with that request. Please try again.