#330: Lazy evaluation of req.chrome
--------------------------+--------------------
Reporter: peter | Owner: nobody
Type: enhancement | Status: closed
Priority: minor | Milestone:
Component: dashboard | Version:
Resolution: fixed | Keywords:
--------------------------+--------------------
Comment (by rjollos):
Replying to [comment:7 olemis]:
> Notice that another check for `sys.exc_info` is needed (see [http
://trac-hacks.org/changeset/12540 this fix for ThemeEnginePlugin] for
further details) . Otherwise error pages seem not to get the proper
styling info .
>
> I was tempted to reopen this ticket , but I didn't . First we should
check whether error pages will be broken after r1437967 .
I had noticed the other day that !TracError pages weren't rendering
correctly. I tested again today in an environment created last week, and
saw that the !TracError page was rendering correctly, but the theme had
gone away. I then created a new environment in order to get the latest
version of [trachacks:ThemeEnginePlugin] with Olemis' fixes, and now I see
something that looks nice:
[[Image(TracErrorAfterRevision1437967.png,100%)]]
I invoked the !TracError by replacing `data` with `None` in
`trac.wiki.web_ui._render_view`. I wanted to force an exception when the
template was rendered. Are there other ways good ways to test this?
Clicking the **Create** button leads to an interesting error:
[[Image(RequestUriTooLarge.png)]]
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/330#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
