search

symphonycms / debugdevkit

Debug DevKit for Symphony CMS
http://symphonyextensions.com/extensions/debugdevkit/
Other
8 stars 14 forks source link

XSLT Processor Error display #24

Open designermonkey opened 12 years ago

designermonkey commented 12 years ago

This is something that has bugged me for a while, but I never thought of logging it. It's not so much bug, but a feature request.

When I have fuffed up my XSL, the frontend displays a nice error message. If I'm logged in the the debug view, I don't get to see it on the result page. Is it possible to add this error output into the results view?

brendo commented 12 years ago

What exactly are you asking? To have the HTML of the error page shown in the result panel of the devkit?

designermonkey commented 12 years ago

Well, not so much the whole html, but an error string at least, with the same details as the front-end.

Unless this is silly.

nilshoerrmann commented 12 years ago

Wouldn't it be nicer to show a little bit more context and the front-end error pages itself? The XSLT errors are quite verbose, they are quite repetitive. Less text and more context would be nice in my eyes.

One thing I noticed when working on the 2.3 error styles is that we take it for granted that the debug devkit is installed – but this is not a necessity. We have a lot of hardcoded links in there. Another thing is that Symphony doesn't bundle a code highlighting script which would be useful in other areas (events documentation, error messages). Bitter is part of the Debug devkit.