Re: PyBlosxom 1.0 Released!

On Friday 28 May 2004 15:27, will guaraldi wrote:
> What is the "html" entry parser?  Does it use the extension "html"?  If
> so, that's probably the crux of your problem.

Yep, ah, maybe that was one of the other tweaks I had to do. The html entry 
parser:
  http://reagle.org/joseph/blog/technology/python/pyblosxom-htmlentryparser

and yes, this is why I disliked mixing the flavours with the content. I like 
using HTML editors for my content and it seems like a bad idea to somehow 
make it a special sort of extension. 

(I also greatly dislike the "now copy this file to this directory, and that 
plugin to that directory" as a method of installing and upgrade. We already 
have to specify the plugins we want in the config.py, so it is clumsy as 
well as redundant. That's what leads me to just include all the standard 
plugins in the path

py['plugin_dirs'] = ['/home/reagle/data/2web/pyblosxom/contrib/plugins',
    '/home/reagle/data/2web/pyblosxom/contrib/entryparsers',
    '/home/reagle/data/2web/pyblosxom/contrib/plugins/comments/plugins']

)

> There are two things you could do to fix this.  The first is to switch
> the extension the html entry parser uses and then change the extension on
> all your data files (probably something you're not likely to do).

True! ;)

> The second is to grab blosxom.py from CVS and go back to your flavour dir
> setup.

Can you send it to me off list, 1.44 (2 days) is still what's in  CVS.


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click