Image component rendering causes 404 page if referenced image is not available

[sigdestad]

Customer struggled with a front page showing 404, even if everything seemed normal - and the page was published. It turned out the error was caused by the image component (no info in logs etc). The linked image had (due to a different bug) wrong permissions, and was thus not accessible from the live front-end.

Solution: Image component must be able to handle "null" for the referenced image "silently" by not rendering the image. It should not fail.

Also investigate how/why the page returned 404? Can a part override the errorcode of the entire page? Should this even be possible? It was hard to debug and figure out this one.

[rymsha]

Isn't Image component deprecated?

[sigdestad]

Yes, but still in use by many. This should be a very simple "if null" check that we seem to be missing now.

[alansemenov]

@rymsha wouldn't this be solved after your changes in rendering error handling?

[rymsha]

No.