There was a recent mention of using Lynx to access the management interface of Zope. I'd like to use w3m. It produces a more pleasing page given all those little spacer images Zope uses. Also, it automatically launches vi for me when I hit return on the edit screen's text input area, which is *way* cool <grin>. However, it doesn't seem to be handling the management interface correctly. If I descend into a management link, I get the 'view' panel for the link instead of the manage_main screen. Worse, I tried to 'rename' an index_html method, and it renamed the index_html in the *parent* folder! This is most weird. Anyone know what Zope could be emitting that w3m is not handling correctly? I'd guess redirects, but I'm surprised I end up in the view screen in that case... I'm currently running w3m beta-991203. Anyone know if whatever-it-is is fixed in a later version, assuming there is one? --RDM
"R. David Murray" wrote:
There was a recent mention of using Lynx to access the management interface of Zope. I'd like to use w3m. It produces a more pleasing page given all those little spacer images Zope uses. Also, it automatically launches vi for me when I hit return on the edit screen's text input area, which is *way* cool <grin>.
However, it doesn't seem to be handling the management interface correctly. If I descend into a management link, I get the 'view' panel for the link instead of the manage_main screen.
This is w3m's fault, it does not send the Authentication header to frames in a frameset, just to the frameset. Zope calculates 'manage_workspace' based on various factors, including whether or not you are authorized to access the managment view. Since you are effectivly 'anonymous' in the frame it shows you the anonymous view. Uncheck 'View' for anonymous and you will probably get a 401 Unauthorized.
Worse, I tried to 'rename' an index_html method, and it renamed the index_html in the *parent* folder! This is most weird. Anyone know what Zope could be emitting that w3m is not handling correctly?
I don't think it's Zope's fault. In this case, w3m is probably ignoring or not understanding the <base> tag. -Michel
On Sun, 19 Mar 2000, Michel Pelletier wrote:
This is w3m's fault, it does not send the Authentication header to frames in a frameset, just to the frameset. Zope calculates
I knew it was all w3m's fault, since it all works in other browsers <grin>. Thanks for letting me know what the likely problems are. Whether or not I'll have time to do anything with the information remains to be seen. I wonder, though...I'm starting from the manage_main URL, not the manage URL, so the page I'm starting from doesn't have a frameset as far as I can see. Descending into a folder works, but descending into, say, a DTML_method gets me the view. Well, I'll have to just ignore the whole thing for now. w3m is a nice browser, I hope they get these bugs worked out soon. I do still find w3m useful, though. Since it's U command to go to a new URL does accept relative specifications, it's pretty easy to use that to descend into the 'manage_main' view of the items I'm interested in. --RDM
participants (2)
-
Michel Pelletier -
R. David Murray