The slideshow section is positioned in front of the pager section, as if separate layers are involved.
You can either move the pager to some other location, such as above the slideshow, or use CSS to affect the page so that the two different sections don’t overlap. Or if you want to keep the pager where it currently is, you can use z-index to bring the pager forward in front of the slideshow section, so that the pager can then accept click events.
When you investigate the rendered page, you’ll see that the cycle plugin sets the slide to a z-index of 8. So, you’ll want to set a z-index of something greater than 8 to the pager if you want to interact with the pager that’s in the same place as the slide.
By the way, you should know that you can use CSS styles to make the numbered pager links look a lot prettier. Space them out, with borders, or other aspects like that.
They are. See the example at intermediate demos 2 page.
It’s just a couple of links, or buttons if you like, which you refer to from the cycle properties.
A better way though may be to update the pagerAnchorBuilder method instead so that it can create both images and numbers, then to use CSS to disable the appearance of one or the other. That way, both #nav and #pager can then be referred to as being pagers in the cycle setup, and things automatically work as they should.
There isn’t on the initial page load due to the updateActivePagerLink code running long before the numbered pager even exists.
Once the image changes though, the class is there.
You can solve that by, and this shouldn’t come as much of a surprise, by creating the numbered pager section first before the updateActivePagerLink is run by the cycle plugin.
There is already one that exists on the current number, but only after the slide has changed.
To have it also appear when the page first loads, you need to create that numbered pager section first, before the cycle plugin uses the updateActivePagerLink function.