You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If getimagesize() runs into trouble, a NOTICE is thrown and code execution continues, no biggie. But, Magento assumes the operation went fine. But we all know that images can go missing or get corrupted.
Agreed, ideally each instance should be checking the return value to ensure it is not FALSE and then throwing an error early if so, like "Could not get image size for provided file.". In developer mode these errors are thrown as exceptions so it would only have an effect in production mode.
)
* Cache all attribute options for display in layered navigation
This will improve performance by reducing the amount of SQL Queries when fetching all possible attributes to display in the layered navigation
* Use the attribute's own cache tags
Co-authored-by: Ricardo Velhote <ricardo@caretobeauty.com>
edannenberg
pushed a commit
to edannenberg/magento-lts
that referenced
this issue
Aug 20, 2020
If
getimagesize()
runs into trouble, aNOTICE
is thrown and code execution continues, no biggie. But, Magento assumes the operation went fine. But we all know that images can go missing or get corrupted.There are 14 usages of
getimagesize()
at this time: https://github.com/OpenMage/magento-lts/search?q=getimagesize&unscoped_q=getimagesize. Some are handled, some are surpressed (should@
be abolished in the codebase?), some are unhandled.Magento should handle these situations more gracefully IMO.
The text was updated successfully, but these errors were encountered: