PolarBlog User's Page

Now that PolarBlog's usage has grown beyond, oh, I don't know…me, I've been contemplating putting a "user's page" on the site.  This would basically just be a list of linked sites.  I guess a "these people use PolarBlog" sort of thing.  If you're a user and you'd be interested drop me an email (kevinp AT polarlava.com) or comment.

-klp

2/3/2005
Being that for the most part I'm the only one that reads my musings, I've gone through my referal logs and tracked down a number of sites that are currently running PolarBlog.  From this I've now added a PolarBlog Users page to the PolarBlog site.

Comments

  1. Alan said:

    Sounds good to me. Can't beat free website advertising :P.

    -Alan

  2. Alan Pope said:

    Heheh, and in a spooky related event I found this page by looking in my referrer logs.. :D

    Thanks for the linky and for creating Polarblog. I really must get around to playing with the stylesheet one of these days..

  3. Kevin said:

    Alan,

    Thanks for using PolarBlog.  If you would, can you fix your link to my blog?  My stupidity, not yours: http://www.polarlava.com/blog/?eid=212

  4. Alan Pope said:

    Done.

    In return.. Can you understand what is being asked here.. http://www.popey.com//?eid=154#5

    ..and why I have two slashes? I assume it's something to do with $base_url..?

  5. Kevin said:

    Alan,


    Thanks for the fix, but the URL above was for reference only.  The URL on the PolarLava link should be http://www.polarlava.com/blog/  without the eid parameter.

    The double slash problem was a bug in a previous version of PolarBlog.  I'd recommend you do two things, 1) Upgrade your version of PolarBlog: http://polarblog.polarlava.com/releases/ and 2) Join the PolarBlog mailing list here: http://polarblog.polarlava.com/lists/ This problem was discussed previously on the list: http://www.polarlava.com/pipermail/polarblog_polarlava.com/2004-December/thread.html  

    I'll have to look into the RSS issue a bit further.

  6. Kevin said:

    There was a bug in versions prior to V1.2.2 where the file would be regenerated everytime it was requested.  Near as I can tell you appear to be running a version that is newer than that, but less than V1.3.0 which is the release that fixed the double slash problem.

    The way this currently works, the file is valid for then number of minutes specified by $config['rss']['optional']['ttl'] in the configuration file.  The default is 60 minutes.  You may want to increase this value if you don't want it generated so often.

    It might also make sense for me to change the way this operates to an alternative mode.  That being, make the file valid unless there are entries that are newer than the current time.  Will ponder that for a future release.

  7. Kevin said:

    Obviously there can't be entries available that are newe than the current time!  Rather entries that are newer than the current file time minus the TTL value, so new within the last hour by default.