Hi Peter-a you don’t have to revert back to version 3.7.9. Disabling Hotlink protection is all you need to do until one of the developers looks into this minor issue for you.
Kind regards
@peter-a,
Are you saying that when you had hotlink protection enabled in the previous version (3.7.9) you weren’t seeing that issue?
ps: We never made any changes to this feature.
@wpsolutions,
Yes, that is correct. We had hotlink protection enabled in the previous version (3.7.9) and we weren’t seeing that issue.
After you upgraded to the latest version (3.7.9.1), did you by any chance enable some other firewall rules which weren’t previously enabled when you had version 3.7.9?
I can’t see any other way that the changes we made in 3.7.9.1 would affect the hotlink feature.
I apologize — I was mistaken: The problem exists in 3.7.9 as well (I just rolled back to check). I must not have noticed it.
I also tried the 3.7.9.2 update and it still has this issue, so for now I have hotlink protection switched off.
Our images are served by nginx, and I see that hotlink protection is handled by an .htaccess rule, so this might be beyond your control.
But it’s strange that most of our images are not affected — only icons and sprites.
