RE: Bizarre error with standard_html_header
well if you use that script ? --> <meta http-equiv="refresh" content="0 ;URL=http://www.apple.com/enterprise/"> It will fix your problem ? ---------------------------------------------------------------------------- ---- Ok... this one has me flummoxed. I just can't make ANY sense of it. I am taking advantage of Acquisition to save me from having to have two copies of a page... fine.. common... well understood, etc. Problem is, when i go to the page from the lower directory, it throws some bizarre Type error, complaining about too many parameters to standard_html_header. I dug about, i insterted a redirect to try to find WHEN it was hitting. What got me was this: I put <dtml-call "RESPONSE.redirect('index_html')"> as the VERY FIRST LINE of the DTML Document. But the problem still occurrs!! This just makes NO sense. System: RedHat 6.1 Zope 2.1.6 Have a better one, Curtis.
On Wed, 12 Jul 2000, Jonathan Desp wrote:
well if you use that script ? -->
<meta http-equiv="refresh" content="0 ;URL=http://www.apple.com/enterprise/">
It will fix your problem ?
I think you've completely missed the point of my post. Firstly: I don't use those meta tags unless i absolutely have to. The redirection I have in place works fine, when it gets parsed. Secondly: My problem is NOT redirecting the page. I added the redirect as a debuging tool, to find out if the DTML parser was getting that far. In case you've not noticed, any time you get an error, that object is not rendered at all, instead the error report is put in its place. What it showed me was that the page in question was not being parsed at all, even tho the traceback shows it is.
--------------------------------------------------------------------------- - ----
Ok... this one has me flummoxed.
I just can't make ANY sense of it.
I am taking advantage of Acquisition to save me from having to have two copies of a page... fine.. common... well understood, etc.
Problem is, when i go to the page from the lower directory, it throws some bizarre Type error, complaining about too many parameters to standard_html_header.
I dug about, i insterted a redirect to try to find WHEN it was hitting.
What got me was this: I put <dtml-call "RESPONSE.redirect('index_html')"> as the VERY FIRST LINE of the DTML Document. But the problem still occurrs!!
This just makes NO sense.
System:
RedHat 6.1 Zope 2.1.6
Have a better one, Curtis.
On Wed, Jul 12, 2000 at 04:05:08PM +1000, Curtis Maloney wrote:
On Wed, 12 Jul 2000, Jonathan Desp wrote:
well if you use that script ? -->
<meta http-equiv="refresh" content="0 ;URL=http://www.apple.com/enterprise/">
It will fix your problem ?
I think you've completely missed the point of my post.
Firstly: I don't use those meta tags unless i absolutely have to. The redirection I have in place works fine, when it gets parsed.
Secondly: My problem is NOT redirecting the page.
I added the redirect as a debuging tool, to find out if the DTML parser was getting that far. In case you've not noticed, any time you get an error, that object is not rendered at all, instead the error report is put in its place.
What it showed me was that the page in question was not being parsed at all, even tho the traceback shows it is.
You are seeing transactions at work. Your DTML Method _is_ being processed, only an exception caused the publishing process to stop, roll back the transaction, and return the error message to you. DTML is not a linear language like ASP, it is not processed one line at a time and bails out at the first error. DTML is parsed into an object tree when entered, and this tree it then later on asked to render itself. An exception in this tree will propagate down to the publishing level, and then turned into an error response. So DTML is, like Python and Java, object oriented and exception driven. If you want to see how far a page gets, try using <dtml-try> blocks around parts of your code. You can then catch the exception higher in the object tree, and generate your own messages in reaction to this. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ | ZopeStudio: http://www.zope.org/Products/ZopeStudio -----------------------------------------------------
On Wed, 12 Jul 2000, Martijn Pieters wrote:
You are seeing transactions at work. Your DTML Method _is_ being processed, only an exception caused the publishing process to stop, roll back the transaction, and return the error message to you.
DTML is not a linear language like ASP, it is not processed one line at a time and bails out at the first error. DTML is parsed into an object tree when entered, and this tree it then later on asked to render itself. An exception in this tree will propagate down to the publishing level, and then turned into an error response. So DTML is, like Python and Java, object oriented and exception driven.
If you want to see how far a page gets, try using <dtml-try> blocks around parts of your code. You can then catch the exception higher in the object tree, and generate your own messages in reaction to this.
Fine... so my debuging techniques are less than perfect. I will change them in future. Thanks. That doesn't change my original problem, which everybody has so far decided to ignore. Curtis.
On Wed, Jul 12, 2000 at 05:00:45PM +1000, Curtis Maloney wrote:
Fine... so my debuging techniques are less than perfect. I will change them in future. Thanks.
That doesn't change my original problem, which everybody has so far decided to ignore.
Well, I can't really see what is going wrong, and can only suggest techniques of honing in on the problem. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ | ZopeStudio: http://www.zope.org/Products/ZopeStudio -----------------------------------------------------
On Wed, 12 Jul 2000, Martijn Pieters wrote:
On Wed, Jul 12, 2000 at 05:00:45PM +1000, Curtis Maloney wrote:
Fine... so my debuging techniques are less than perfect. I will change them in future. Thanks.
That doesn't change my original problem, which everybody has so far decided to ignore.
Well, I can't really see what is going wrong, and can only suggest techniques of honing in on the problem.
At your suggestion, i've wrapped any contentious parts of the internal/standard_html_header in a dtml-try, which has had no effect. Firstly: what would cause Zope to give me that type error? Too many arguments? I'm not doing anything fancy. This worked until i changed the standard header, which is why i'm digging about in it. but since the only parts of that now that are not in a try statement are raw HTML, how could it go splat?
From what I understand of the traceback, the problem is occurring in the header, but it's not clear WHERE, or, tbh, WHY.
Any more help much appreciated. If you want to see the actual DTML, just ask. Curtis Maloney.
On Wed, Jul 12, 2000 at 05:14:57PM +1000, Curtis Maloney wrote:
At your suggestion, i've wrapped any contentious parts of the internal/standard_html_header in a dtml-try, which has had no effect.
Firstly: what would cause Zope to give me that type error? Too many arguments?
I'm not doing anything fancy. This worked until i changed the standard header, which is why i'm digging about in it.
but since the only parts of that now that are not in a try statement are raw HTML, how could it go splat?
From what I understand of the traceback, the problem is occurring in the header, but it's not clear WHERE, or, tbh, WHY.
Where _is_ the traceback? It may well be that the call _to_ the header is botched. I also see that you are making assumptions about acquisition context. An acquired message does not autmatically also acquire the context of the caller. See several articles and How-To's by Jim Fulton and Shane Hathaway on Zope.org. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ | ZopeStudio: http://www.zope.org/Products/ZopeStudio -----------------------------------------------------
Forgot to include: Zope Error Zope has encountered an error while publishing this resource. Error Type: TypeError Error Value: too many arguments; expected 2, got 3 Curtis.
participants (3)
-
Curtis Maloney -
Jonathan Desp -
Martijn Pieters