That looks like a website configuration issue and nothing to do with the plugin, you should check configuration first including caching plugins/systems which look like they might be interfering with things. The image name is not from this plugin and looks like it has been modified in some way.
Did you get a chance to check? I’d be interested to know the outcome
Hello richadsahby. Thanks for your reply. You must be right but we don’t know what’s interfering or bad configured. If we fix it, I’ll write you back telling the solution.
Cheers
I would start by looking at the image itself- there is a single image in the CSS file “overlay.png” but in your install it has been renamed “xoverlay.png.pagespeed.ic.7HAmKqrsoP.png” so my guess would be that whatever is doing that is where the issue lies.
The security certificate if applied to the whole domain should mean that the location of the image (i.e. the cookie-law-info/images folder) is not an issue- however in your case it is, which is why I think it’s website configuration on your side.
Hope that helps. Good luck!
p.s. if it were me and this was the only thing in the way, I would probably hack the CSS file to remove the reference to the image. A quick and dirty fix, the underlying problem hasn’t gone away, but this might not be worth you spending a lot of time investigating for very little benefit. Just my opinion anyway… 🙂
Hello richadsahby. I’ve searched both “overlay.png” and “xoverlay.png.pagespeed.ic.7HAmKqrsoP.png” in my server and I’ve found there are copies of “xoverlay.png.pagespeed.ic.7HAmKqrsoP.png” in “/var/cache/mod_pagespeed/rname/…/wp-content/plugins/cookie-law-info/images/xoverlay.png.pagespeed.ic.7HAmKqrsoP.png”. “overlay.png” is under “/var/www/gremyo.com/htdocs/wp-content/plugins/cookie-law-info/images/overlay.png” as expected.
So, yes, we have apache mod_pagespeed enabled and caching files. It keeps them to a directory (var/cache/) wich could not being covered by the SSL certificate as I didn’t install it and don’t know much about it.
Excellent debugging work there 🙂 That’s the root cause of your issue then, so now the question is how do you get apache mod_pagespeed to play nicely with SSL. I’d be very interested to know the answer.
Try: http://stackoverflow.com/questions/14372847/how-to-configure-mod-pagespeed-for-ssl-pages
As this isn’t a plugin issue I’m marking this resolved. If you do find the solution post it here.
I solved it following the official PageSpeed documentation where I found they specified a case like mine: running behind a load-balancer.
https://developers.google.com/speed/pagespeed/module/https_support
I enabled:
ModPagespeedRespectXForwardedProto on
in /etc/apache2/mods-available/pagespeed.conf
Thank you for your help Richard.
Best,
Miguel
Hi Miguel, that’s a pretty obscure bug, must have taken a while to find- thanks for posting the fix! Cheers, Richard
