When an error is thrown (i.e., Core::throwError()) but there is no message, the error page will refuse to render and redirect to the default page. When the default page generates the error (with no explanation) a weird loop situation arises.
A possible solution would be to change the error page so that a default error message is shown when there is no message.
When an error is thrown (i.e.,
Core::throwError()) but there is no message, theerrorpage will refuse to render and redirect to the default page. When the default page generates the error (with no explanation) a weird loop situation arises.A possible solution would be to change the
errorpage so that a default error message is shown when there is no message.