WP Photo Albums Plus, slideshows, images other than the first…

1. Firstly, i recommend you upgrade to the lastest WP (4.3.1) since 3.4.x had some critical security vulnerabilities.

2. I only found 1 image link on the url u gave above. It was only when i clicked it, it showed a larger version but then i could use the navigator arrows to go to the next images. Where are the other image placeholder links on this page for me to see your problem?

1. My mistake. I use WP 4.3.1 of course. All plugins are up to date also.

2. The image is a Photo Albums slideshow. You can use links on image sides (not visible) or below image: Nastepne zdjecie

I’ll have a look later tonight/tomorrow. In the mean time i notice you have compressed your html but also have:

<script> jQuery(document).ready(function( $ ){ //jQuery(

Note the “//”. This will trigger a javascript error because your comment indicator (//) is preventing the closing “})”. I personally prefer to use /* */ instead so when i end up compressing my html these errors wont accidentally happen (assuming compressors leave comments).

This likely isnt what is causing your problem but just wanted to let you know.

Anyway, ill get back to you when i figure things out.

Kimberly

Kimberly is right, you have a syntax error:

Error: SyntaxError: missing } after function body
Line: 1, Column: 37
Code:
jQuery(document).ready(function( $ ){ //jQuery(‘.yuzo_related_post’).equalizer({ overflow : ‘rel

OK. Thx for tip. I changed Yuzo plugin settings (no scripts from Yuzo) and I turned off html compression (for a while).

Now line:
jQuery(document).ready(function( $ ){ //jQuery(‘.yuzo_related_post’).equalizer({ overflow : ‘rel
not exists.

Problem with Responsive lightbox remained ??

Seems to be working fine now Piotr. Resolved?

No.
I installed all updates (5 minutes ago) and no change.
Still: When you try to open lightbox on other than the first image then you will have black screen ??

Looks like kind of javascript conflict. Your image are not ajax load so all should be available at the moment of page load.

Maybe you have some lazy load script?