finferflu

I got the same notification, but upon inspection, I can’t seem to find anything wrong with the file in question: false positive?

Glad you managed to sort it out ??

Would you be able to see what the direct link to those thumbs is? You can do that by looking at the web inspector. Once you know the exact path, you may be able to find more info in the logs.

Would you be able to provide your blog URL so that I can also test it?

That looks like the access log. If you’ve been looking for errors in there, you won’t find any. You will need to check the actual error log.

If you error log is empty, then I would suggest to search for “.jpg” or “.png” entries in the access log to see if there are any interesting status codes attached to those broken thumbs.

Before suggesting anything, I would recommend going through the list of results here.

I have never done this, but this guide seems quite comprehensive.

Have tried to clear your cookies/cache to see what happens?

You can refer to my reply here.

JavaScript and PHP operate in two completely different ways. PHP is executed on the server, and by the time you see the webpage, the code has already been executed. JavaScript, instead, is executed by the browser on page load and subsequently.

This means that by the time your browser loads the JavaScript code that you need, the PHP code has already finished being executed.

As far as I can see your calendar is generated by availabilitycalendar.com and I would suggest asking their support team whether their software can provide you with a code that you can use during the PHP execution.

See my reply here.

If you have FTP access to your server you could try to remove or rename the folder /home/content/22/8653322/html/wp-content/plugins/tracking-code, which will disable that plugin.

Do you see any errors in the web server error log?

You can either follow the advice on this post, or you could hide the date via CSS, by adding the following to your stylesheet:

.polaroiddate { display: none; }

I just found that if I change the blog URL from blog.<computer hostname>.local to local.<domain>.tld, the plugin functions properly. Something must be wrong with the .local top level domain.