If you're using "row style: fields"

Experiencing the same problem. The slideshow is only displayed once right after flushing caches.

Not sure why this would happen. Just to make sure I wasn't doing anything weird I checked views_cycle and views_rotator modules and they add the settings in the same exact place. So not sure why it's not working. Would need to figure out in what cases does template_preprocess_ not get fired, but the page is rebuilt. Are you using panels or anything special?

If the view is added via ajax, but the settings aren't (which is, unfortunally, quite useful with ajax), it errors out due to undefined index -- ie views preview, context ui drag and drop. Then usually breaks the rest of the ajax on the page, caused a enternal error loop for me somehow, was up to 2k js errors >.O

Reproduce: use views preview on the view.

It's cause the files are added to every single page, but the settings only as needed, so if the html with the classes it recongizes get added, it tries looking for the corresponding settings, and bam, js error.

Patch attached only add settings when js settings is added.

There's another issue when the setting is set and it does not recongize it as a string; also need to do it for the other submodule that has the same issues

#7 works for me thanks

I'll try to look at this as soon as I can. I believe it was moved to init because if you cached the views it wouldn't work. Does this allow the view to be cached and still work?

I haven't tested all caching, but with views caching it appears to be working with what caching we have enabled; I'm not sure what step in the process views caches the javascript file/settings but it appears to they are cached

I'm still getting this error, even with running the patch in #7.

Firebug reports it to be on line 15 of views_slideshow.js:

settings.targetId = '#' + $(fullId + " :first").attr('id');

This is what fb says in the scopechain:

[Call { fullId="#views_slideshow_singleframe_main_1"}, Call { context=}, Window node]

This is a screengrab of my fb session: http://grab.by/6G3P

****
Edit: I downgraded Views Slideshow to version 2.0 and now it works fine.

I have this error only on my front page :/

This is happening on my frontpage only. If I go to the page display for my view, the slideshow works fine. I'm adding it to the frontpage template like this:

$featured_view = views_get_view('frontpage_featured');
print $featured_view->execute_display('default', $args);

and I get the same message as OP: viewsSlideshowSingleFrame is undefined. I stepped through the page load in NetBeans and far as I can tell, it's adding the viewsSlideshowSingleFrame variable to Drupal.settings. I applied #5 above, which broke my slideshow (all images appeared inline). I applied #7 by doing:

patch --verbose -p0 < 893428_views_slideshow_advanced_issues_0.patch

in the module's root folder. It complained:

patch: **** malformed patch at line 86:    // to the id to make it unique.

Okay, so I've done some more hacking around on this and have come to the end of my Drupal knowlege. I can see that during page load for my frontpage, this line is executed:

drupal_add_js(array('viewsSlideshowSingleFrame' => array('#views_slideshow_singleframe_main_' . $vss_id => $settings)), 'setting');

and it appears to work. viewsSlideshowSingleFrame is added to $javascript['settings'] in drupal_add_js(). But somewhere between there and the page load finishing, that variable is not added to Drupal.settings. I'm not sure where to look next.

@mdm have you followed the instructions here: http://drupal.org/node/823056

@redndahead That solved my issue and taught me something new about Drupal, thanks! :)

(I was thinking about it again, and think the file should also check for viewsslideshowsingelframe being defined, and not rely on the file only being included as needed; was thinking of the different situations and, while ideally the settings would always be there when the html is, there's too many chances, considering ajax that would not be so. Going to leave this needs work till can update the patch, and make sure it actually applies via patch and not manually. )

Any chance of re-rolling the patch? So close... :)

@hefox: Whoops, sorry — left the page open too long before posting that comment.

Apparently we're still using the 1.x branch >.O, but looks like the 2.x branch still has this issue.

Restored the slideshow js being added in init*, but added the checks mentioned above.

*Views does have an issues with caching files; if a file is added in the first view, it caches that it needs that file; however if another view WOULD have added the file, but don't cause it's added by first, bam, file no be added if second view viewed alone. Technically a views issue, but :/.

#962592: Drupal.settings.viewsSlideshowJCarouselThumbs is undefined for jcarouselthumbd issue.

From what I can tell turning off caching for the Views Slideshow Block works a treat.

#5 worked for me, Many thanks

Awesome! These patches fixed some other issue - you could not drag and drop Views Slideshow block with Context UI/Admin modules. I went nuts! It just showed block for split second and then it was gone. Now it works as expected. Thank you hefox and others!

Also I didn't find any problems so far, so changing status.

and 3.x -dev probably needs same fixes...

3.x won't need it as it handles advanced options in a complete different way.

this has been committed. Thank you

i have also this kind of problem "settings is undefined" appear in my firebug in javascript error, my views slideshow does not display correctly paused in the last content i made in that views. When i login as user1 it goes well as it should what i notice is all on my site uses a javascript does not work properly even my navigation menu, wibiya and the views. I am a newbie, if i use this patch 893428_slideshow_undefined.patch where should i paste it?

If you haven't you should be using the dev version.

Thank you rednahead, i have already installed the dev version and it works only one thing does not have the thumbnail feature like on the recomended version, but anyway the important is now working, again thank you
John Gorospe

Then edit your field in the view and clear the checkbox for "Group multiple values".
worked for me.

This #22 works for me.

Thanks.

I've come on this situation only after using the slideshow in at least 10 sites, where it worked perfectly. Analyzing the differences, I've realised that this situation occurs only when you embed the slideshow in the page.tpl.php template file.
If you create a special type for the home page and the home page is of this type, the slideshow is embedded at node.tlp.php level and this problem does not occur...
Also, the solution described at #16 worked for me in embedding the slideshow at page.tpl.php level.
Thank you.

Thanks for the tip, i also used a print function to get my views blocks on screen, i was stuck on a other project with this. Now my second project has it to, but the projects before didn't. Like you say, because the you have to use the blocks regions.

The patch #21 doesn't work for me.
Any issue about that ?

I was hitting this problem as well, but I was not using views_embed_views within page.tpl.php.

What my problem was is that within the view itself I had caching turned on "per user". I flipped this off (am using Drupal's block caching anyway, and my slideshow is a block, along with normal page caching) and things seem to be fine now.