Am 16.09.2008 um 12:44 schrieb Richard Ash:
> I've been seeing this on an internal set-up hosted on Centos 5 for a  
> while. When I tried the command line version for a PDF ($ mw-render - 
> c http://your/wiki -w rl -o test.pdf "Some Article") it told me it  
> couldn't load the rl writer because there was no module "hashlib".

hashlib shouldn't be used in the current (Mercurial) version of mwlib  
any more, if the latest release on PyPI still references hashlib  
somewhere, this is to be considered a bug (we do support Python 2.4)  
which should be fixed in the next release.

> In the apache logs I get a
> PHP Notice: Udefined property: stdClass::$is_cached in  
> Collection.body.php on line 638

Could you update the Collection extension? The line looks different  
now, so the error might be gone.

> At this point I noticed the the name of the variable holding the URL  
> of the render server has changed from wgPDFServer to  
> wxCollectionMWServeURL (when did this happen - trac still has the  
> old name in places?),

Thanks for the report: I adjusted the Trac page and fixed the  
README.txt for the Collection extension, which contained a typo in  
that variable name, too. This change is quite old (I think at least a  
few months).

> so my LocalSettings.php contained the wrong line, and so the  
> collection was trying to use the public server even though it wasn't  
> supposed to.

Which explains the non-existant logfiles, I guess :)

> At this point the error message bucks up and I get something useful:
> The POST request to https://lightning.eatechnology.com:8443/cgi-bin/mwlib.cgi 
>  failed (SSL certificate problem, verify that the CA cert is OK.  
> Details: error:14090086:SSL  
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed).
> which is presumably because the server is on a self-signed  
> certificate. Any ideas how to tell the collection extension that the  
> certificate is OK (I'm sure I've been here before, but can't find  
> anything in the mailing list archive or trac)?

Seems to be a problem with curl for PHP. You could apply the two lines  
from this blog post:

   http://ademar.name/blog/2006/04/curl-ssl-certificate-problem-v.html

to Collection.body.php where the curl options are set (search for  
curl_setopt). I think we shouldn't add this in the official version  
though.

Regards,
Johannes


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mwlib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mwlib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to