The Isis and Protostar templates are missing support for rendering the stack trace on the error template. This PR adds it.
Testing Instructions
1) Ensure debug mode is enabled
2) With Isis and Protostar active, trigger an error page on both site and admin, note no trace exists
3) Change the templates to Hathor and Beez3 and again trigger an error on both sides; there should be a stack trace
4) Apply the patch and make Isis and Protostar the active templates again
5) Once again, trigger an error page; there should now be a stack trace
Why render this information?
A stack trace is a useful debugging tool to show how we got to a point in the execution cycle. Supporting this allows quicker troubleshooting by instructing users to enable debug mode and trigger the error; if their template supports this feature then there is a clear step-by-step output of what was called to trigger the error and isolate the problematic extension.
joomla-cms-bot
- 
here.
zero-24
- 