Closed (fixed)
Project:
Blazy
Version:
3.0.13
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Mar 2025 at 20:19 UTC
Updated:
12 Apr 2026 at 15:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
skymen commentedPatch
Comment #3
gausarts commentedGood find, thank you.
Please provide the repro, what pages you see it, and also the entire error message.
Once provided, you may want to wrap $route_name line as a condition instead.
Comment #4
skymen commentedThis warning appears on log when microsoft bot from IP 52.167.144.17 scan my site. The target page is article with images.

In one minute more than 300 lines in dblog. If users are visited this page, the log is empty.
Error trace:
Comment #5
gausarts commentedWondering why bots would bypass, or have different output from, human visitors.
Not questioning your report, I would love to understand the heart of the problem.
Please clarify, when having such an error, did you enable caching at performance page?
Comment #6
gausarts commentedBugs must have a consistent reproduction.
Feel free to re-open if any further explanation as requested in the previous comment. And only if you see other bots such as Google's, etc. result in the similar errors. Or alternatively use robots.txt to block useless bots.
Comment #7
jura.khrapunov commentedSame warning appears for some nodes which contain Blazy-enhanced images while they are being rendered for indexing via drush:
strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated BlazyManagerBase.php:220Comment #8
jura.khrapunov commentedComment #11
gausarts commentedI couldn't reproduce it, but your confirmation as requested makes this in.
Thank you all for contribution.
Comment #14
anybody@gausarts thanks! We're now seeing lots of these messages in production using 8.4. Could you maybe tag a new stable release?
Comment #15
gausarts commentedPlease test out DEV if any issues. I haven't thoroughly reviewed things. That is why no new releases yet.
We'll release it after any review on DEV in case any regressions.
Thanks.