[Plugin: NextGEN Gallery] Slide show not working NEXTGEN GALLERY

I “might” have the answer to this – I was battling the same problem, and one of the things I tried was changing the settings for permalinks – I had it set to “day and month”

https://lisaandroger.com/blog2/2009/05/14/photo-blog/

and the slideshow wouldn’t work from this URL

https://lisaandroger.com/blog2/2009/05/08/photo-blog/?show=slide

When I change the permalink setting to “Default”

https://lisaandroger.com/blog2/?p=123

then the slideshow will work with this URL

https://lisaandroger.com/blog2/?p=50&show=slide

So there’s something about the way the URL is constructed for a permalink of type day month that causes this to not work?

But I did come to this forum to ask why this might be – what would I need to change to get it to work with the day month type permalinks?

Thanks

Roger

I have the exact same problem. I’m using 2 subdomains( on the same server) for 2 wordpress instalations. I instaled both WP and NextGen the same way(only dif is the themes and site content). On 1 site NextGen works just fine and on the other its like on jeff’s whambangcomics.com. I’m using on both sites permalinks set to day and name. If someone knows what is this about pls tell us.

Thank You in advance!

I am having the same problem as well. I tried changing the permalink structure back to default yet still did not yield any results. My WP installation is on a subdomain. The gallery works fine, I simply cannot get the slideshow to appear.

Are you sure that the path to imagerotator.swf is correctly specified in the settings for the Slideshow?

I’ve had trouble with that and clearing it and resetting it has fixed the problems also.

I am having the same problem–I can easily create a regular gallery, but cannot create a slideshow (nothing appears–not even the code). I have tried everything I can think of, searched this forum, and the internet.

PLEASE!! Someone help!!!! What am I doing wrong???

Same trouble here… I have recently updated Nextgen Gallery plugin and all of my slideshow don’t work anymore… And all the new too!

I am having the same problem – one slideshow loads fine on the homepage (in the side bar) but no other slideshow works, and the sidebar slide show is broken on every other page.

Currently using – WP 2.8.4 and NextGen 1.3.5

Note: My navigation bar is a little messed up from upgrading to 2.8.4, but the resolution for my slideshow not appearing still works – I hope this helps you all.

I was having the same difficulty as many who have written in in that my slideshows were not appearing at all (but everything else was working great!).

To fix it I went to:
GALLERY->Options->Slideshow and then I changed the location of the “Path to the Imagerotator (URL):” to /wp-content/uploads/imagerotator.swf and that fixed everything.

Note: the difference is that previously the “/wp-content/” was not in the URL, it was just “/uploads/imagerotator.swf”.

Good luck everyone!

Hello

I too have just managed to get this working again but slightly differently – I had to put in the complete url to the imagerotator file

i.e “https://www.domainname.co.uk/wp-content/uploads/imagerotator.swf”

And everything is working again.

I have already changed the flash file location… The problem is about the xml or something else, it’s don’t find pictures…

If thickbox isn’t displaying properly make sure you have this code in your footer.php file in the theme you are using:
<?php wp_footer(); ?>
and this should be in the header.php (before </head> )
<?php wp_head(); ?>

You can access those files in dashboard > appearance > editor (the files are on the right)

If slide show isn’t working after you uploaded the imagerotator.swf file with your nextgen plug in, go to gallery > options > slideshow > and set the path to where you uploaded the file (the default is your-site-root-here/wp-content/uploads/imagerotator.swf

@ daisybee

Thanks, this worked for me too.

i.e “https://www.domainname.co.uk/wp-content/uploads/imagerotator.swf&#8221;

Took me ages to find out the problem – inserting the entire url should have been a priority trouble shooter though really…