Re: [Zope] Zope management screens and OmniWeb (on OS X)
tom smith writes:
just reporting a strange bug when trying to manage zope using OmniWeb ( a non too shabby (non-MS) browser on OSX). The left-hand and top frame work fine, but in the right-hand frame where my DTMLMethods and Folders should be I get the results of the index_html for that folder. That is...what the folder would look like if I was viewing it. It may help, if you address the right frame directly:
localhost:8080/manage_main instead of localhost:8080/manage If you are lucky, you need to do this just once (per session) and can afterwards use the normal "manage". Dieter
tom smith wrote -
just reporting a strange bug when trying to manage zope using OmniWeb ( a non too shabby (non-MS) browser on OSX). The left-hand and top frame work fine, but in the right-hand frame where my DTMLMethods and Folders should be I get the results of the index_html for that folder. That is...what the folder would look like if I was viewing it.
I had that same problem in Windows using Internet Explorer until I upgraded to to a more recent version (IE5.5). You may need to change your browser. It isn't just IE that can cause trouble, though. I've had trouble with POSTed forms whose target is a different window or frame using Netscape 4.7. Going to a GET fixed that problem. Cheers, Tom P
On Thu, Apr 26, 2001 at 04:04:05PM -0400, Thomas B. Passin wrote:
tom smith wrote -
just reporting a strange bug when trying to manage zope using OmniWeb ( a non too shabby (non-MS) browser on OSX). The left-hand and top frame work fine, but in the right-hand frame where my DTMLMethods and Folders should be I get the results of the index_html for that folder. That is...what the folder would look like if I was viewing it.
I had that same problem in Windows using Internet Explorer until I upgraded to to a more recent version (IE5.5). You may need to change your browser. It isn't just IE that can cause trouble, though. I've had trouble with POSTed forms whose target is a different window or frame using Netscape 4.7. Going to a GET fixed that problem.
For that matter, I've always experienced the same situation with w3m ( a not too shabby text browser ) Zac -- $name="zachery bir"; $email="zbir@urbanape.com"; $position="systems administrator"; $altposition="witch doctor"; $voice="804.353.3742"; $web="http://www.urbanape.com";
participants (3)
-
Dieter Maurer -
Thomas B. Passin -
Zachery Bir