Adaptive Grid inside Lightbox not working inside Poster Stack Main Page

I swear this was working before. I’ve done a lot of updating, but no idea what is keeping the Lightbox from working with Adaptive Grid… You should be able to click an image and they will activate Lightbox.
https://www.lisasandlerphotography.com/blog/?post=married-couple-from-out-of-town&tag=engagement#poster-top

Using Sections Pro, Grummage, Foundation, Adaptive Grid, Poster.

@willwood @instacks @tav @joeworkman @zeebe… anyone? Thx!

p.s. Refresh or clear cache if you’ve been to my site recently. I’m constantly updating :slight_smile:

Gotta get that SEO in lol. You try naming a gazillion photos of the same subjects :wink:

Yes, it does. But why “dodgy”? I thought that’s what all the cool Brits do these days. Especially since Brexit. :slight_smile:

1 Like

JavaScript error in foundation:

foundation.min.js:20 Uncaught TypeError: Cannot read property ‘sticky_class’ of undefined
at Object.is_sticky (foundation.min.js:20)
at HTMLElement. (foundation.min.js:20)
at Function.each (jquery-2.2.4.min.js:2)
at e.fn.init.each (jquery-2.2.4.min.js:2)
at Object.resize (foundation.min.js:20)
at foundation.min.js:20
at foundation.min.js:17

1 Like

:smile:

an the obligatory fill to make up 20 characters

Jannis @instacks -

Would you please stop speaking in code!?!? :wink:

So what does this mean, it’s Foundations fault? @joeworkman or @zeebe can you please help?

thanks, Lisa

Well, you combine many different stacks from different developers…

Poster Stack works without any problem with Foundation. Just to state that, I tested this several times and have a lot of customers running with that.

That JavaScript error might just be the outcome of some other misbehavior. I doubt that there is an error in Foundation. Best is you update all Stacks to their latest version and test step by step which stack causes the error.

There are no JS errors on the page. The following CSS will fix it…

.poster-main-content > .stacks_out {overflow:hidden!important;}

1 Like

Yep, that did it! BTW… I didn’t see the error either… must have needed to refresh the page or clear cache.

thanks, @joeworkman :slight_smile: