Image links not working

It is probably ‘just’ a timing issue. Sometimes it works, see:
https://wppa.nl/wp-content/wppa-pl/Screenshots/jasondeangelo.PNG

I made some changes, please install the current dev version as described on this documentation page and try again.

Please tell me what other plugins you have activated. It could be a compatibility issue with an other plugin/feature.
Can you tell me where the following js files come from?

<script type='text/javascript' src='https://www.jasondeangelo.com/wp-includes/js/imagesloaded.min.js?ver=3.2.0'></script>
<script type='text/javascript' src='https://www.jasondeangelo.com/wp-includes/js/masonry.min.js?ver=3.3.2'></script>
<script type='text/javascript' src='https://www.jasondeangelo.com/wp-includes/js/jquery/jquery.masonry.min.js?ver=3.1.2b'></script>
<script type='text/javascript' src='https://www.jasondeangelo.com/wp-content/themes/twentythirteen/js/functions.js?ver=20160717'></script>
<script type='text/javascript' src='https://www.jasondeangelo.com/wp-includes/js/wp-embed.min.js?ver=4.9.5'></script>

hi! Thank you so much for getting back to me! I will follow the instructions now.

Do you mind going private and I will just give you access to the site? I dont mind at all. I’ve been going crazy trying to figure this out, and would be willing to pay you to fix it!

Thank you again!

Hi…I just went through the steps you outlined, but it did not work. ??

Clearly I think there is something seriously wrong with my site. When I thought it was just your plugin issue, I got the I got the Envira gallery, but there seems to be severe issues with that, as well. It makes the paged associated with that gallery run extremely slow! I mention that only bc I think it may relate to the overall issues with the site. Any help would be very much appreciated. TY!!!

Also, I was told by my hosting compnay to run a PHP 7.0 scan. it comes back with lots of errors for your plugin. The galleries have been so slow lately, so I’m wondering if that is part of the issue.

here is the log from that scan:

FILE: /home/content/p3pnexwpnas03_data02/78/2326778/html/wp-content/plugins/wp-photo-album-plus/wppa-photo-admin-autosave.php
—————————————————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————————————————————–
1 | WARNING | File has mixed line endings; this may cause incorrect results
—————————————————————————————————————————–

FILE: /home/content/p3pnexwpnas03_data02/78/2326778/html/wp-content/plugins/wp-photo-album-plus/wppa-admin-functions.php
——————————————————————————————————————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
——————————————————————————————————————————————————–
499 | WARNING | Function name “__wppa_sanitize_files” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
——————————————————————————————————————————————————–

FILE: /home/content/p3pnexwpnas03_data02/78/2326778/html/wp-content/plugins/wp-photo-album-plus/wppa-exif-iptc-common.php
————————————————————————————————————————————————-
FOUND 27 ERRORS AFFECTING 27 LINES
————————————————————————————————————————————————-
311 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x0’
313 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x1’
315 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x5’
317 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x7’
319 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x8’
321 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x9’
323 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0xd’
325 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0xf’
327 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x10’
329 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x14’
331 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x18’
333 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x19’
335 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x1d’
337 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x1f’
339 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x20’
341 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x30’
343 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x41’
345 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x45’
347 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x47’
349 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x49’
351 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x4d’
353 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x4f’
355 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x50’
357 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x58’
359 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x59’
361 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x5d’
363 | ERROR | The behaviour of hexadecimal numeric strings was inconsistent prior to PHP 7 and support has been removed in PHP 7. Found: ‘0x5f’
————————————————————————————————————————————————-

FILE: /home/content/p3pnexwpnas03_data02/78/2326778/html/wp-content/plugins/wp-photo-album-plus/wppa-styles.php
—————————————————————————————————————————————-
FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
—————————————————————————————————————————————-
680 | WARNING | Function name “__wis” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
694 | WARNING | Function name “__wcs” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
—————————————————————————————————————————————-

Thanx for the info. This can not be the problem.

Please do the following:

1. Do NOT panic, we will fix this.
2. Mail me admin login details. Mail to (spelled out) opajaap at opajaap dot nl
3. Do NOT panic. I will help you.

The php errors you show me do no longer appear in the current version. They have been fixed in steps in various versions of the plugin between july 2017 and january 2018.

I noticed that it is currently ‘almost’ working.
However, I have four important recommendations:

1. Set Table VI-B1: Cover Image: The link from the cover image of an album to anything other than lightbox. This is to improve performance and possible processing and/or memory problems in the visitors browser. Use lightbox on cover images only on single albums that contain no more than 100 photos.

2. I see near the bottom of the page in the page source:

<script type="text/javascript" defer src="https://www.jasondeangelo.com/wp-content/cache/autoptimize/js/autoptimize_4b51cc97b9d308f1891cabd47b1a3f0f.js"></script></body>

This may be lethal for your site. Find the feature that ‘optimizes’ and defers javascript and de-activate this feature. all js files are already minified, and this kind of ‘optimisation’ gives troubles most of the times in various ways. Please do not use this function!!!

3. Set Table I-B8: Slideshow pagesize to a value not larger than 50.

4. Set Table I-C7: Thumbnail pagesize to a value not larger than 100.

• This reply was modified 6 years, 11 months ago by Jacob N. Breetvelt.

This may be lethal for your site. Find the feature that ‘optimizes’ and defers javascript and de-activate this feature. all js files are already minified, and this kind of ‘optimisation’ gives troubles most of the times in various ways. Please do not use this function!!!

Given that Autoptimize is active on over 600 000 sites, one could argue it does not give trouble most of the time. Moreover any problem originating from Autoptmization can be fixed in the configuration-screen as explained in AO’s FAQ @opajaap. ??

Feel free to contact me at frank-at-optimizingmatters-dot-com if you’d like to better understand how to make your plugin work with AO out of the box (which it may already, as the site from the OP seems to work)!

Groetjes uit Belgi?,
frank

@optimizingmatters

it does not give trouble most of the time

Good! But there may be exceptions and there are obviously problems on the site (lightbox starts but hangs before completing to show the first image – never seen before).

My strategy is always: First: the functionality must be good, Second: optimize, and know what you are doing.

I have seen so many issues due to bad cahcers/compressors that the first thing i recommend when there are problems to switch off any of them.

Many site builders add optimizers without knowing how they work and what the side-effects may be.

I will give Autoptomize a try (like i did with Cometcache) an will test it if it does not affect wppa functionality and i will come back to you if i find any complications, but my first concearn is the proper functionality of this site.

@optimizingmatters

Fail at the first test:
I explicitly load wppa.js in the header. It contains definitions like
var wppaAutoColumnWidth = [];
In the middle of the page is added: <script ...>wppaAutoColumnWidth[1]=true;</script>
This causes an error: ReferenceError: wppaAutoColumnWidth is not defined.

Apparently optimizing js moves wppa.js to the bottom.

This problem within one minute after installation of autoptimize and switching optimize js on.

So you learned a couple of things already, great! ??

So;
1. optimizing CSS & HTML is not a problem
2. for JS optimization you’ll have to exclude wppa.js (which you can ask your users to do or you could do through the API
3. alternatively you could use the API to excluda all of wppa’s pages from JS optimization

Tell me if you’d like example code for 2 and or 3 and I’ll whip something up ??

frank

hi ALl! Thank you so SO much for helping me! I am so ignorant when it comes to any of this. i thought WP was supposed to be easy! ha

Yes…please do whatever you need to make this all work. You will see the Envy (?) photo plugin. I was trying that to see if its was your gallery that was causing the issue, but clearly, it’s the site. I will not lie…I actually like some of the options with that new photo gallery (we can discuss later, if some could be implemented!…one is the way it renders on mobile), and I say that just for full disclosure. you have been so kind and I do not want you to think i would take advantage. i TRULY do want to pay you for your time. AND, even if I were to go with another option down the road, I would love to keep your contact info and pay you if anything comes up in the future, which I KNOW it will!

Again…thank you both! i will email the credentials. ??

I did some setting changes and some album re-organisation.

This speeds up your site, make it more comprehensive, and you can use autoptimize js compression.

Hope you like it,

@optimizingmatters
I have a setting that moves all inline script to an ad-hoc js file and loads it in the footer. This works with autoptimize.
Html works if you do not remove comments.
Css: i did not yet found problems.

To be clear: I have different opinions about delaying js (e.g: I do not want to wait until load and process complete before scripted onclick events get working or lay-out is adjusted), but that is up to the user. My concern is that a lot of users install optimizers because of hear-say that it gives performance improvements, without knowing what they do. My default settings (Also have a setting that allows optimizers to remove html comments but that slowes down the filmstrip under slideshows dramatically) are the best to my opinion when no optimizer is used. So, in case of problems, I always recommend to switch optimizers off. Also, I can not dig into the huge amount of available optimizers to see if there is an api to deal with potential issues. Yes, i learned a bit. My first programs were around the start of the unix timestamp in a language called ALGOL60 and ran on a multi cubic meters sized system with 4KB memory on the technical university in Delft. During my professional it job i was systems support consultant and specialized in system configuration and performance tuning in the super mini computer business, so, although web programming is relatively new to me (only 6 years experience up to now), i think i may say that at least i know a bit what i am talking about…