Submitted by : simon at: 2003-10-26T21:31:50+00:00 (14 years ago)
Name :
Category : Severity : Status :
Optional subject :  
Optional comment :

We recently upgraded an existing ZWiki web from 0.9.x to 0.15.

As expected, some free-form page names have since been observed with their ids as a proper WikiNames, and titles as free-form. (e.g. [Meeting today]? -> id=MeetingToday? title="Meeting today")

The problem is that the context rendering in the header is Meeting today (WRONG!)

Usually this is compensated for by a redirect, but for some reason this is broken on our site (any suggestions?).

I have put in place a temporary fix in our copy of, but I don't really know what I'm doing, or what else I may have broken with this:

 diff .orig/
 <                   # Following line & use of nrealid below hacked locally 10-Feb-2003
 <                   nrealid=self.pageWithName(n[0]).id()
 <                         % (indent, rel, nrealid or quote(n[0]), quote(n[0]),
 >                         % (indent, rel, quote(n[0]), quote(n[0]),

2003/02/09 18:04 GMT
Couple quick thoughts:

  1. Did you upgrade/replace the standard_error_message and SeachPage??
  2. Do incorrectly cased (or partial id's) in a URL redirect properly?

So long, and thanks for all the fish! ;-)

In reply (from original poster) --2003/02/10 01:29 GMT
Thanks for that. Answers

  1. Yes - both upgraded
  2. No - they don't

However, you have triggered a clue here. When a page isn't found, our zope log contains:

2003-02-10T14:17:43 BLATHER(-100) OFS Exception while rendering an error message
Traceback (innermost last):
  Module OFS.SimpleItem, line 201, in raisestandardErrorMessage
  Module OFS.DTMLMethod, line 126, in __call__
  Module DocumentTemplate.DT_String, line 474, in __call_
  Module DocumentTemplate.DT_Let, line 75, in render
  Module DocumentTemplate.DT_Util, line 195, in eval
   - __traceback_info__: SearchPage
Unauthorized: You are not allowed to access SearchPage in this context

This is from a session with the Manager role, so it appears not to be a simple authorization problem.

In any case it would seem preferable to render the correct URL rather than force a gratuitous redirect. Is there any reason why this cannot or should not be done?

fixed, cf similar issue --simon, 2003/05/10 01:40 GMT
Status: open => closed