.pt Compile Errors Masked in Skins
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Zope 3 | Status tracked in 3.4 | |||||
| 3.4 |
Fix Released
|
Critical
|
Unassigned | |||
| zope.pagetemplate |
Won't Fix
|
Undecided
|
Unassigned | |||
Bug Description
If a skin under development has a syntax error, attempts to display a page that uses the skin will get a misleading KeyError, where the referenced macro name is not found (although the thrown exception does show the name of what wasn't found). But the log output shows no syntax errors, so you don't know what to look for.
Then, if you instead try to display the skin itself (URL @@standard_
TypeError: unsubscriptable object
------
2005-12-03T12:19:36 ERROR root PageTemplateFile: Error in template: Compilation failed
HTMLParser.
------
2005-12-03T12:19:36 ERROR root PageTemplateFile: Error in template: Compilation failed
HTMLParser.
The problem is that something is catching and eating the thrown exception in the first case, making it hard to debug a template syntax error that masquerades as a logic error. Anytime there is a template compile error, it should be logged.
| Christian Theune (ctheune) wrote | #1 |
| Jim Fulton (jim-zope) wrote | #2 |
| Changed in zope3: | |
| status: | Unconfirmed → Confirmed |
| Dmitry Vasiliev (hdima) wrote | #3 |
| Benji York (benji) wrote Re: [Bug 98254] Re: .pt Compile Errors Masked in Skins | #4 |
| Tres Seaver (tseaver) wrote | #5 |
| Changed in zope.pagetemplate: | |
| status: | New → Won't Fix |
This might be two problems. One of them was solved recently when
I added the filename of the template which is broken to the error
message. This might then do what you need.