Download views_slideshow-6.x-3.0-beta1.tar.gztar.gz 285.63 KB
MD5: 3b6bebd6caeca819b81c2fc561f30193
SHA-1: 267bfb39617f2b78179853fce2d4a9b9418b0437
SHA-256: 0f6fc4dd41c5ea1968c6f39aeb6c74b794a36c12cb3c673aa46c41c684f0544f
Download views_slideshow-6.x-3.0-beta1.zipzip 324.67 KB
MD5: eaeff42dae493d791989ccf18f0c7538
SHA-1: e25d9ca50e0a8dd8c54c204f344f233205e2785e
SHA-256: 2f6db7e24dad5c5ea3f7782f7a53b957b48c6de9081b219ad1d3567786c27e68

Release info

Created by: redndahead
Created on: 29 Sep 2010 at 22:13 UTC
Last updated: 29 Sep 2010 at 22:16 UTC
Core compatibility: 6.x
Release type: New features

Release notes

This is the newest version which will only work on views 3.

Changes Since Version 2

  • Singleframe and Thumbnailhover have been combined into the Views Slideshow Cycle module. Singleframe and ThumbnailHover are still available, but are marked as legacy modules. They will be removed in the next major release. There is no migration path from singleframe/thumbnailhover to cycle.
  • Support for plugin-able pagers. So other modules may add their own pager types. You can see an example on how to do this here
  • Support for skins. You may now create a module that allows you to add your own skins so one can easily change the layout of the slideshow through the settings. You can see an example on how to do this here
  • More templates. If you look in the views_slideshow/contrib/views_slideshow_cycle/theme directory you can see there are numerous tpl.php files you can use to override the default style of the slideshow.
  • Redesigned settings page. The settings page has been redesigned to offer the most used features by default so one can quickly get going. You can find additional options under the advanced settings checkboxes.
  • Significantly re-factored advanced options. Each advanced option has it's own textarea. This will allow you to enter multi-line settings without problems.

Things still may change so although this release is stable enough to use there may be api changes in future beta releases. The api and settings will not be considered stable until a final release is completed.


The selected release is the release that will be used for automated testing. Optional projects are only used for testing.



No optional projects