Lightbox stopped working

Hi @billrodgers2013, can you provide an example of page with this bug on your website?
Thanks

Hi nikeo,
It happens on the front page at https://thmcec.org.au
I click on the image in the first post with the title “You Have Got To Be Kidding Me!” and the image opens below the footer.
Same with the image in the next post.
W3 Total Cache is being used but I’ve never had an issue with it before and it happens regardless of whether I am logged in (and therefore bypassing the cache) or not.

Also happens on every other page (example https://thmcec.org.au/charities-thmcec-supports/ ) where a single image has been inserted. Those previously opened in a lightbox. Galleries are not affected.

Ok, I have seen the problem on your website. Pretty weird!
Please confirm :
– that you have the latest version of the theme installer : v3.1.24
– your version of WP

And try to do the following : temporarily desactivate all your plugins and see what you have.

By the way if you open your console (press f12 + and click on console), you’ll see that you have 50+ warnings / errors, most of them are related to https insecure content.

Thanks.
Customizr is 3.1.24
Am using a child theme.
No changes made to that though. Only change was setting up Connections Business Manager and then disabling Spider Cataolog because it caused a conflict with it. Spider Catalog used lightbox for images.
I might try activating Customizr alone first instead of the child theme and then try for a plugin conflict.

The insecure content is mostly due to All In One Event Calendar. A theme change for that will stop the warnings for a while. I moderate in their forums and test their software and that issue is on the list to be fixed for the next release.

It worked with going back to the Customizr theme alone but not with my Child theme. Will try and remove all the Child customisations and add them back and see what happens.

This was fixed by recreating a Child theme. All customisations were added back except the header image which I decided to do without for now.
I still have no idea why it happened. Only assumption is that a script left by Spider Cataolog was still being loaded despite purging W3 Total Cache.

Ok, well done glad to read this.
No idea too…the browser cache could it be also a lead?

Could be. I had deleted that too though.
It will remain a mystery unless it happens again in which case I’ll get frustrated again.
Hopefully with that plugin now gone it won’t happen again.