Re: Re: Re: genericwiki with PB 1.1?
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 3 May 2005, Matej Cepl wrote:
>
> Well, apparently the problem is that wikibaseurl variable, which is a
> parameter of parse is empty (or undefined).
>
> The only method how to make it work, was to set
>
> py['parser'] = 'genericwiki'
>
> and then change the end of initialize function in
> pyblosxom/Pyblosxom/pyblosxom.py to this:
>
> # entryparser callback is run here first to allow other plugins
> # register what file extensions can be used
> data['extensions'] = tools.run_callback("entryparser",
> #{'txt': blosxom_entry_parser},
> {'wiki': blosxom_entry_parser},
> mappingfunc=lambda x,y:y,
> defaultfunc=lambda x:x)
Oh... well, that could be part of the problem. I don't think genericwiki
is an entryparser--it's a preformatter. So your setup isn't correct here.
The genericwiki doesn't register itself as an entry parser whic is why in
order to make it "work" like an entryparser, you you have to do it by
adjusting the code that you've adjusted.
> However, that is of course suboptimal.
Definitely. It should probably be changed to be an entryparser. I have
no idea why whoever wrote it did it the way they did. It also looks like
a very unmaintained plugin.
Anyhow, I'm pretty sure this has nothing to do with API changes, but
rather has to do with the plugin itself. Beyond that, I can't really say
since I neither use the plugin nor do I run PyBlosxom 1.1.
Sorry bout that.
/will
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20