Slides not working after update!

If you look at the project page you will see:

• There is no upgrade path from 1.0 to 2.0. You will need to recreate your settings.
• Views Slideshow 2.x requires Views 2.
• Views Slideshow ThumbnailHover 2.1+ requires Views 2.7+.

Can you show the Drupal.settings javascript that is outputted on the slideshow page and the HTML output?
Look here to see what i mean: http://drupal.org/node/add/project-issue/views_slideshow

Do not forget to paste the code between code tags (see Allowed HTML tags below the comment form), otherwise it will not be visible.

I feel your pain. I had a nice front page slide show with a crapload of custom theming and preprocessing going on to make it look good. I run drush update and BAM! two weeks of tweaking in my free time in order to get all the stuff working again. Not really the module maintainers fault, I should have been more careful when running drush update, but oh well it's all good now I got it working again.

Please set back to active when you have replied.

Marking as fixed.

Hi there,
I have a similar issue seems to be the same thing.

Using Views Slideshow 6.x-2.2 and Views 6.x-2.11

I have tried clearing Drupal site cache (global cache) and views cache twice.

I have tried changing the settings in my view (which is a block).

The block returns empty, there is no HTML markup or images (my view is the latest image in the latest articles in a slideshow).

If I change the view style from Slideshow to say unformatted, table, grid etc.. The images appear, but as soon as I change it to slideshow it stops showing the images, infact nothing outputs. I also have fields for title, and teaser output in the view, but I get nothing returned in slideshow mode.

Any idea what it could be?

Firebug / Web Developer toolbar for Firefox returns no JS errors.

I also updated to Drupal 6.17 today not sure if it's relevant or not.

Address of website is www.viczcar.com slideshow should be on homepage, but as you can see the block above the content is returning nothing just the block markup. (Will leave it like that, if it helps for now).

It is not adding the views slideshow javascript at all so it doesn't know there is supposed to be a slideshow on that page. How are you creating the block? Are you using the block created by the views module or are you using views_embed_view()?

I just checked and I'm using the block generated by views.

Even when I preview the view in the views interface, using say unformatted style will output something, but as soon as I switch to slideshow style. It stops outputting any preview.

Did you update from 1.x? Is views slideshow thumbnailhover module or views slideshow singleframe module enabled?

I couldn't remember what version I upgraded from, but I looked through the list of modules and noticed "views slideshow singleframe module" in my list and it was not enabled.

So yeah I feel a little bit silly right now, but at the same time I'm very grateful for your help.

Also kudos on the new features, some really good improvements here.

marking as fixed.

I experienced this issue and wanted to note that in addition to enabling the Views Slideshow SingleFrame module, I had to change between the old "Single Frame" setting, which results in no slides displaying, and the new "SingleFrame" setting for "Slideshow mode".

This duplicate setting situation seems likely to add some extra head scratching and clicking around for folks and might be worth addressing. Here's a screenshot for reference:

Hmm What version were you upgrading from? I've never used 1.x so could it have been from that?

Ok, updated from 2.0 to 2.3 (I know, way out of date) and slideshow just stopped working. I checked ezra-g's thing and views doesn't even *show* me the new options. I have "SingleFrame", but no "Single frame" and the latter (older) one is not doing anything. I'm not getting any errors, but the whole thing is just not working at all. Any suggestions, beyond clearing cache (done a million times, including Views cache in the Views tools section)?

Weird. Works now. No idea why. Browser cache maybe?