Re: [pyblosxom-users] Pyblosxom permalinks are not permanent

[Steve H. <sho...@gm...>]

On Fri, Jul 17, 2009 at 4:22 PM, Steve Hoelzer<sho...@gm...> wrote:
> On Fri, Jul 17, 2009 at 2:42 PM, will<wi...@bl...> wrote:
>> Steve Hoelzer wrote:
>>>
>>> What I'd really like to do is organize my files in folders like:
>>> /2009/Jul/17/filename. That would give me true permalinks and prevent
>>> the duplicate slug problem. But doing this interferes with PyBlosxom's
>>> date based archives, so it's not possible right now.
>>
>> Are you sure about that?  I'm pretty sure we solved that issue a few
>> versions ago.
>
> No, I'm not sure. I tried this a long time ago with PyBlosxom 1.4.1 (I
> think) and it didn't work then. I'm still on 1.4.1 now but I'll
> upgrade if this issue is fixed. If I get some time I'll experiment and
> report back.

I finally gave this a try and it does not work for me using the
current trunk (r1333). I had a very simple test case with three
entries in /2009/09/, py["num_entries"] = 2, and date archives with
month numbers turned on.

$ python pyblosxom-cmd staticrender
pyblosxom-cmd version 1.5 dev
Trying to import the config module....
Performing static rendering.
rendering 3 entries.
rendering 3 category indexes.
rendering 3 date indexes.
rendering 0 arbitrary urls.
(before) building 9 files.
building 9 files.
rendering '/2009/09/firstpost.html' ...
rendering '/2009/09/secondpost.html' ...
rendering '/2009/09/thirdpost.html' ...
rendering '/index.html' ...
rendering '/2009/index.html' ...
rendering '/2009/09/index.html' ...
rendering '/2009/index.html' ...
rendering '/2009/09/index.html' ...
rendering '/2009/09/09/index.html' ...

All of the index.html files contain the 2nd and 3rd post but not the
first. Date based archives should not be limited by py["num_entries"].

It also seems wasteful to render some pages twice (ex:
/2009/index.html). It would be nice to detect the duplicates and get
rid of them.

Steve