Use Firebug to expand that Stuck Stack Trace

I am pretty sure I am the only one who gets XPage errors (feels like it some days) but just in case I am not…

Sometimes the “twistie” that shows the XPage Stack Trace is collapsed and will not respond to a click.

What to do? Use Firebug of course!

Use Firebug (or Chrome of course) to change the DOM so you can see your stack trace and be on your way to error-free XPage code!

2 Comments

Paul S Withers on November 22, 2011 at 1:06 pm

Nice workaround, very useful. It gets 'stuck' when the error page gets loaded from a partial refresh error. You can get around it by creating an error page that just contains HTML, no XPages controls. I blogged about it here http://www.intec.co.uk/xpages-error-pages-partial-refresh-and-javascript/ and I've added an error page that does just this in the latest release of XPages Help Application on OpenNTF.
Russell Maher on November 22, 2011 at 2:34 pm

Thanks Paul.

For a production error page solution, your solution is excellent.