[Plugin: Meteor Slides] Double pagination

Hi Tim, there are two common causes for the pager links doubling.

First if there are two slideshows on the page that are the same, not two different slideshows, in this case the buttons will all be merged into the first slideshow and the second will have none.

I don’t see any evidence that you have more than one slideshow, so the other thing to look at is custom navigation. Have you done anything to the slideshow template or script? If the pager buttons are manually added in the template or setup differently in the script, sometimes the default and custom nav can both load.

When I posted I did not have any slideshow set-up, just 4 slides. I added a slideshow called ‘Home’, added those 4 slides to it and there are still 4 extra pages.

The only thing I changed from the stock CSS was positioning to center the pagination:

.meteor-slides .meteor-buttons {
bottom: -15px;
height: 9px;
left: 42%;
margin: 0;
padding: 6px 0 0;
position: absolute;
width: 100%;
z-index: 999;
}

If I change is back to stock, I still get the 8 pages so my positioning isn’t causing this.

That’s weird, it must be some kind of JavaScript conflict. I’m not seeing any errors. Pretty sure it is something with the theme, but I would deactivate Contact Form 7 and test it just to be sure.

With all the other plugins off I still have the 4 extra pages. This is a Twenty Eleven child theme and is the first time I have ever seen this sort of thing with Meteor Slides.

I can’t see anything that could be causing this, everything looks perfect, could you send me a login for the site?

Ah ha! It was because the slideshow had a double container like this:

<div id="meteor-slideshow" class="meteor-slides">
	<?php if ( function_exists( 'meteor_slideshow' ) ) { meteor_slideshow(); } ?>
</div>

So the Cycle script was trying to run the slideshow twice, once on each “meteor-slideshow” container, and you were getting two sets of navigation.

I removed the second slideshow container wrapped around the template tag and it seems to be working great now.

I knew it had to something simple. Thanks for troubleshooting and fixing it!

No problem Tim!