Glider.js

The Glider.js module lets you create sliders using the glider.js javascript library in your drupal projects. You can use the Glider.js field formatter in the image fields or entity reference fields, or create a view and use the Glider.js view style for the carousel creation.

Features

Using the Glider.js field formatter

To use the field formatter you need to create a new content type or use an existing one having an image field or entity reference field. Go to your content type manage display page in /admin/structure/types/manage/YOUR_CONTENT_TYPE/display and set the formatter for your image field or entity reference field as Glider.js and then you will be able to set the different configurations.

Using the Glider.js views style:

To use the views style you need to create or edit an existing view and select Glider.js as the format. Open the view format settings to configure the gliderjs carousel.

Recommended modules

Markdown

Improves the module help page formatting the README file into valid HTML.

Installation with Composer

The required javascript libraries are hosted with NPM's packagist so changes will need to be made to the project root's composer.json file prior to requiring this module with composer.

See the README.md for more details.

Issues

As with all contributed modules, when considering submitting an issue:

1. Read the documentation (two or three times is better). Don't forget the home page.
2. Review the existing issues list. (Don't forget to select "<- Any ->" for the "Status" field.)
3. Gather all the appropriate information. This may include (but is not limited to):
   • Drupal version.
   • Browser type and version.
   • Database type and version.
   • Error messages, if any.
   • Module settings.
4. Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.
5. If you go to provide a patch use the following naming convention:
   [gliderjs]-[short-description]-[issue-number]-[comment-number]-[drupal-version].patch

And please don't forget to use the Issue Summary Template to report an issue, if you need help to understand how the issue queue works, see the Getting Started in the Issue Queue video.

Development version status

The development versions (-dev) are where the newest stuff is, including any bug fixes and new features. We try to make sure it is tested before we commit anything, but occasionally a bug will get through from us. Your help in testing this code is greatly appreciated. The translation templates may not always be up-to-date in the dev releases.