Show Traceback in Mozilla 1.x
When I try to view the source of a Zope error page in Mozilla, it will not let me see the traceback or any source for that matter. How do I configure Zope to output debug info that will appear in Mozilla? -- -- Chad Nantais Rednaxel Interactive cnantais@rednaxel.com
Chad Nantais wrote:
When I try to view the source of a Zope error page in Mozilla, it will not let me see the traceback or any source for that matter. How do I configure Zope to output debug info that will appear in Mozilla?
Is this somethign Mozilla specific? Have you tried other web browsers? cheers, Chris
How exactly does Mozilla not let you see the source? If it's a frame, you'll need to right-click and choose "This Frame -> View Frame Source". I'm not sure if it's relevant, but I think Mozilla has a bug which means that "view source" actually re-requests the url, so you're not getting an accurate source listing, because the parameters to your query may be missing. This is obviously only relevant when you have a page that is the result of processing a form. Felix On Tue, Jul 09, 2002 at 12:09:00PM +0100, Chris Withers wrote:
Chad Nantais wrote:
When I try to view the source of a Zope error page in Mozilla, it will not let me see the traceback or any source for that matter. How do I configure Zope to output debug info that will appear in Mozilla?
Is this somethign Mozilla specific? Have you tried other web browsers?
On Tue, Jul 09, 2002 at 12:24:18PM +0100, felix@chaptereight.com wrote:
How exactly does Mozilla not let you see the source? If it's a frame, you'll need to right-click and choose "This Frame -> View Frame Source".
I'm not sure if it's relevant, but I think Mozilla has a bug which means that "view source" actually re-requests the url, so you're not getting an accurate source listing, because the parameters to your query may be missing. This is obviously only relevant when you have a page that is the result of processing a form.
A bookmarklet helps here. Add the following URL to your bookmarks and call it "Show current DOM tree as HTML source": javascript:(function(){ function htmlEscape(s){s=s.replace(/&/g,'&');s=s.replace(/>/g,'>');s=s.replace(/</g,'<');return s;} x=window.open(); x.document.write('<pre>' + htmlEscape('<html>\n' + document.documentElement.innerHTML + '\n</html>')); x.document.close(); })(); I think I found it at http://www.squarefree.com/bookmarklets/. Marius Gedminas -- Any sufficiently advanced Operating System is indistinguishable from Linux. -- Jim Dennis
On Tue, Jul 09, 2002 at 12:09:00PM +0100, Chris Withers wrote: | Chad Nantais wrote: | > | > When I try to view the source of a Zope error page in Mozilla, it will | > not let me see the traceback or any source for that matter. How do I | > configure Zope to output debug info that will appear in Mozilla? | | Is this somethign Mozilla specific? Not really. | Have you tried other web browsers? Yes. When it fails, it is invariably due to the browser acting like an idiot and re-getting the page to show the source. Of course, when the page is dynamically generated this can often result in the wrong page's source being displayed. I've found that 'links' is mostly decent when it comes to viewing source -- just press '\' to switch between rendered and source views. The problem with it comes if a line of text is wider than the terminal, since it doesn't wrap it then. -D -- A perverse man stirs up dissension, and a gossip separates close friends. Proverbs 16:28 http://dman.ddts.net/~dman/
Derrick 'dman' Hudson wrote:
On Tue, Jul 09, 2002 at 12:09:00PM +0100, Chris Withers wrote: | Chad Nantais wrote: | > | > When I try to view the source of a Zope error page in Mozilla, it will | > not let me see the traceback or any source for that matter. How do I | > configure Zope to output debug info that will appear in Mozilla? | | Is this somethign Mozilla specific?
Not really.
| Have you tried other web browsers?
Yes.
When it fails, it is invariably due to the browser acting like an idiot and re-getting the page to show the source. Of course, when the page is dynamically generated this can often result in the wrong page's source being displayed.
This reminds me with an old problem I had with Netscape Navigator (IIRC all versions < 6). Try to print a displayed page which has an expires="-1d" header. The result is funny in a sick way. It prints the page: "This page has expired. Please press reload [...]" cheers, oliver
participants (6)
-
Chad Nantais -
Chris Withers -
Derrick 'dman' Hudson -
felix＠chaptereight.com -
Marius Gedminas -
Oliver Bleutgen