Re: xmlrpc_metaweblog.py problem

Steven Armstrong <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user
Message-ID <[email protected]>
Richard Chamberlain wrote:
<snip>
> Thanks again for the reply.
> 
> I've debugged somewhat further (I'm learning fast how pyblosxom  
> works!). I tried logging the requests on both servers and they were  
> pretty much identical.
> 
>  From what I can tell xmlrpc.py or xmlrpc_metaweblog doesn't appear to  
> be getting called. Firstly I stuck some print statements in both xmlrpc  
> and xmlrpc_metaweblog which I expect to see show up in the log, but  
> nothing appeared. I then tried logging to a file in the process method  
> in xmlrpc and still nada.
> 
> I logged PATH_INFO and that shows correctly as /RPC.
> 
> I've also discovered that my original error:
> 
> File  "/home/richardc/public_html/pyblosxom/pyblosxom-1.0.0/Pyblosxom/ 
> pyblosxom.py", line 590, in blosxom_process_path_info
>     data['flavour'] = (form.has_key('flav') and form['flav'].value or
>   File "/usr/local/lib/python2.3/cgi.py", line 603, in has_key
>     raise TypeError, "not indexable"
> TypeError: not indexable
> 
> Doesn't happen on the other server because the it never gets to that  
> bit of code, again having logged it.
> 
> I've installed will's pluginfo plugin and the xmlrpc plugins are both  
> listed.
> 
> So for some reason the xmlrpc plugins are not handling the request  
> causing it to be handled as a standard request, hence the failure.
> 
> Any other suggestions how I go about debugging this?
> 
> Thanks,
> 
> Richard
> 

Hello Richard

I just stumbled over the same problem while experimenting with a cgi 
version of pyblosxom.

Have you found a solution for this?
Care to share it?

cheers
Steven


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.