Re: static rendering

>
> I apologize it's taking me so long to get to this.  I've had a pretty   
> busy
> weak and most things ended up getting back-burnered.

No problem. I don't expect instant replies.

>
> Anyhow, I'm not really sure what the problem is off the top of my head.   
> I'm
> assuming that your lack of setting the second base_url is a typo in your
> email and that that isn't the issue.

Yep, that isn't it.

>
> I've both never used static rendering on a Windows platform, nor have I  
> used
> the file:// protocol.  So I have no clue what that would do to the code  
> and,
> I'm really sorry to say, I don't have time right now to set it up like  
> you've
> got it and figure out what the issue is.
>
> So, if you know Python, the static rendering code is mostly in
> pyblosxom/Pyblosxom/pyblosxom.py in runStaticRenderer (I think that's the
> method).  It figures out what needs to be rendered and then calls a  
> rendering
> function in the tools module to do the actual work by creating  a new
> PyBlosxom request with the necessary path_info information.  I  suspect  
> that
> the values you've entered into config are causing PyBlosxom to try  to
> generate pages that don't exist.  Could be related to your base_url, but  
> I'm
> not really sure.
>
> Hope that helps.  Sorry I can't be of more use.
>

Thanks Will, I had thought that I might be doing something obviously  
idiotic,
but it seems not. I am a python fan, so I'll mess around and see what I can
find. If I come up with anything useful, I'll let you know.

Cheers,
Brett



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com