pyblosxom-users — Mailing list for pyblosxom users and hackers.

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

[seanh <sea...@gm...>]

On Mon, Jul 20, 2009 at 2:11 PM, seanh<sea...@gm...> wrote:
>
> I dunno, feels inelegant. Perhaps keeping categories fixed is better.
>

I noticed that in wordpress if you change the unique slug of a post
and then visit the old slug you get re-directed to the new one. I
wonder if you could do something like that in pyblosxom? Use
categories+filename as permalinks but if you move a post leave a file
behind with an HTML redirect in it.

It could get messy. If you moved a whole category you might have to
leave a whole lot of HTML redirects, and if you moved the same post
more than once you would get a chain of redirects.

If you just move the odd post one time I guess it would work.

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

[seanh <sea...@gm...>]

On Fri, Jul 17, 2009 at 8:50 PM, will<wi...@bl...> wrote:
> seanh wrote:
> PyBlosxom lets you use whatever permalink format you want to use.  The
> format you want to use depends on how you do your blog.  If categories are
> fixed, then you can use a category based permalink.  If mtimes are fixed,
> use that.  If you want some third thing, you can write a plugin to do it
> however you want.

Actually, can you even link to a particular post by date? I think you
can link to a day, month or year, but not a post. So it looks like
it's either categories as permalinks or writing a plugin to do it
another way.

I'm not sure how best to write a plugin for this. Lets say we want
some sort of permalink IDs that are independent of either category or
date. We could use the filename or a #slug metadata line. Either way I
see two difficulties: 1. the user could potentially create non-unique
IDs and 2. I think the plugin would need to build an index of the IDs
in order to be able to respond to permalink requests quickly enough.

One way it could work is similar to the rdate utility. Before
publishing content to your blog you run a 'slug' script that adds
unique, short #slug metadata lines to any of your posts that don't
already have them. These could be numeric or based on the post title
or filename (with numbers added for uniqueness of necessary). The
script also creates an index of slugs. A pyblosxom plugin then uses
this index to handle requests for posts via their slugs.

I dunno, feels inelegant. Perhaps keeping categories fixed is better.

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

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

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.

Steve

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

[will <wi...@bl...>]

seanh wrote:
> 
> I believe that PyBlosxom (and blosxoms generally) have a fairly
> serious issue with permalinks.
> 
> Correct me if I'm wrong, but PyBlosxom provides two ways to link
> directly to a particular post: by category or by date. One or the
> other of these is what's usually referred to as a "permalink" in
> PyBlosxom blogs. But neither of these things is permanent at all.
> Re-categorise a post, which doesn't seem unusual or unreasonable, and
> that permalink is broken. Edit a post and, since PyBlosxom updates the
> date, that permalink is broken.
> 
 > This is terrible, right? Broken links everywhere.
 >

PyBlosxom lets you use whatever permalink format you want to use.  The 
format you want to use depends on how you do your blog.  If categories 
are fixed, then you can use a category based permalink.  If mtimes are 
fixed, use that.  If you want some third thing, you can write a plugin 
to do it however you want.

PyBlosxom has no internal notion of a permalink.  It's just a url in the 
story template.  It can be composed however you want or even not 
included if that suits your fancy.

Blosxom is the same way.

So...  it sounds like you see this as an architectural flaw, but I see 
this as a freeing sort of thing since it allows different people with 
different needs to implement whatever works for them.

/will

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

[will <wi...@bl...>]

Steve Hoelzer wrote:
> On Fri, Jul 17, 2009 at 12:50 PM, seanh<sea...@gm...> wrote:
>> It occurred to me after writing this that the filename (minus
>> extension) is equivalent to a slug so you wouldn't need to add a
>> metadata line. Now to imitate wordpress permalinks we'd have to be
>> able to combine pyblosxom's date-based URLs with filenames (without
>> categories) to form URLs like: /2009/Jul/17/filename.
> 
> 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.

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

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

On Fri, Jul 17, 2009 at 12:50 PM, seanh<sea...@gm...> wrote:
>
> It occurred to me after writing this that the filename (minus
> extension) is equivalent to a slug so you wouldn't need to add a
> metadata line. Now to imitate wordpress permalinks we'd have to be
> able to combine pyblosxom's date-based URLs with filenames (without
> categories) to form URLs like: /2009/Jul/17/filename.

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.

Steve

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

[seanh <sea...@gm...>]

On Fri, Jul 17, 2009 at 6:36 PM, seanh<sea...@gm...> wrote:
>
> PyBlosxom could do slugs using a #slug metadata line in each post
> file. A slight problem is that you're expecting the user to come up
> with unique slugs, but you have no way of telling them, when they're
> just typing the slug in their text editor, that it's not unique.
> Another problem is that when a visitor requests a slug PyBlosxom would
> have to inspect the contents of every post file, so clearly some sort
> of index or cache is going to be needed.
>

It occurred to me after writing this that the filename (minus
extension) is equivalent to a slug so you wouldn't need to add a
metadata line. Now to imitate wordpress permalinks we'd have to be
able to combine pyblosxom's date-based URLs with filenames (without
categories) to form URLs like: /2009/Jul/17/filename.

[pyblosxom-users] Pyblosxom permalinks are not permanent

[seanh <sea...@gm...>]

Hi,

I believe that PyBlosxom (and blosxoms generally) have a fairly
serious issue with permalinks.

Correct me if I'm wrong, but PyBlosxom provides two ways to link
directly to a particular post: by category or by date. One or the
other of these is what's usually referred to as a "permalink" in
PyBlosxom blogs. But neither of these things is permanent at all.
Re-categorise a post, which doesn't seem unusual or unreasonable, and
that permalink is broken. Edit a post and, since PyBlosxom updates the
date, that permalink is broken.

This is terrible, right? Broken links everywhere.

As a file-system based weblog engine the file path seems like the
natural thing to use as a unique identifier. But I feel that this is
probably a mistake in the same way that it's a mistake to use the
mtime as the date of a post even if it seems like the natural thing to
do. There are several plugins that do dates in a different way, but I
don't see any to fix permalinks.

Solutions?

Never re-categorise a post. You could use tags instead, and can change
those without breaking the permalinks. I think additional tools are
necessary to make tags manageable though. PyBlosxom isn't very good at
tags though because it's filesystem-based and the filesystem doesn't
do tags. Without a lot of custom scripting you aren't going to get tag
auto-completion and suggestion, splitting, joining, renaming and
deleting tags, etc.

Jekyll [1] has a neat way of doing it. The user can specify, in the
configuration file, what the format of permalinks should be based on
various metadata about the post: date, title, and categories.

[1]: http://wiki.github.com/mojombo/jekyll/permalinks

Use unchanging "published" dates. PyBlosxom can already do this. In
combination with one of the plugins that prevents the date from being
modified when you edit a post, that ought to fix it. I think PyBlosxom
could do with a plugin that lets a post have both a published date and
a modified date. The original published date never changes and can be
used as a permalink, the modified date changes and can be used to
inform readers of when the post was last modified.

Wordpress seems to put original publication dates in permalinks also,
followed by a user-configurable "slug", e.g. 2009/05/23/hello-world.
"hello-world" is not the title of the post (or the categories or
tags), it's a slug that's there purely for the purpose of the
permalink. Change the slug and (in theory) you've broken the
permalink, although in fact if you visit an old slug wordpress seems
to be able to redirect you to the new one. Still, even without the
redirect, this enables you to edit, rename and re-categorise a post,
the only thing you mustn't change is the slug.

PyBlosxom could do slugs using a #slug metadata line in each post
file. A slight problem is that you're expecting the user to come up
with unique slugs, but you have no way of telling them, when they're
just typing the slug in their text editor, that it's not unique.
Another problem is that when a visitor requests a slug PyBlosxom would
have to inspect the contents of every post file, so clearly some sort
of index or cache is going to be needed.

[pyblosxom-users] Blog farming with pyblosxom and apache2

[Todd A. J. <no...@co...>]

I'm having some trouble figuring out how to get multiple pyblosxom
instances workingi on the same server. I thought I could do it like so:

    <VirtualHost *>
	    ServerName foo.example.com
	    ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
	    DocumentRoot /var/www/foo
	    RewriteEngine On
	    RewriteRule   ^/blogs/([^?]+)(.*)$ /cgi-bin/pyblosxom.cgi$2 [E=SCRIPT_FILENAME:/etc/pyblosxom/$1]
    </VirtualHost>

with files in /etc/pyblosxom named for each blog. For example,
/etc/pyblosxom/foobar would serve up http://foo.example.com/blogs/foobar
once the elements of /etc/pyblosxom/foobar were all configured.

This doesn't seem to work for me; I just get apache errors saying:

    File does not exist: /var/www/foo/cgi-bin

when I can clearly stat /usr/lib/cgi-bin/pyblosxom.cgi from the command
line.

Can anyone point me to some information on how to do this correctly?

-- 
"Oh, look: rocks!"
	-- Doctor Who, "Destiny of the Daleks"

[pyblosxom-users] Bloxsom in Django

[Chris M. <ch...@mc...>]

Hi,

I present for you, a half-implemented, possibly buggy implementation of the
text-file based blogging engine PyBloxsom, re-done in Django. Maybe this will
be useful to someone else who has a pybloxsom blog and wants to transition to
something more manageable/hackable (with no offense to the PyBloxsom
developers, and thanks for their software which gave me a year of good
service!).

<http://mccormick.cx/news/entries/django-bloxsom>

Best,

Chris.

-------------------
http://mccormick.cx

[pyblosxom-users] need help with comments.py

[sha <sh...@ma...>]

Hi,

I installed Pyblosxom 1.4.3 on a Debian Lenny System. Works great so
far and I'm having much fun with it, but unfortunately there is one
thing I can't get to work: support for comments.

When I'm trying to submit a comment, the response is "an internal
server error occured". The comment file gets written, but the article
page will never load again. From apache error-log: 
"[ERROR] comments: bad comment
file: /home/sha/myblog/entries/comments/perfect-privacy-12434773"
more output: http://pastebin.com/fdf1e098

I'm using the comment-plugin from the contrib-1.3.3 tarball.

Any ideas..?

[pyblosxom-users] pyblosxom doesn't seem to manage utf-8 with french language

[chaica <ch...@oh...>]

Hi everyone,

I have filled the #2781177 bug.

I'm using the following configuration : 
py["blog_language"] = "fr"
py["blog_encoding"] = "utf-8"
py["locale"] = "fr_FR.UTF-8"

When executing pyblosxom : 
# pyblosxom-cmd staticrender
pyblosxom-cmd version 1.5 dev
Trying to import the config module....
Performing static rendering.
rendering 2 entries.
rendering 1 category indexes.
rendering 4 date indexes.
rendering 0 arbitrary urls.
(before) building 7 files.
building 7 files.
rendering '/firstpost.html' ...
rendering '/maparticipation.html' ...
Traceback (most recent call last):
  File "/usr/bin/pyblosxom-cmd", line 5, in ?
    pkg_resources.run_script('pyblosxom==1.5', 'pyblosxom-cmd')
  File
"/usr/lib/python2.4/site-packages/setuptools-0.6c7-py2.4.egg/pkg_resources.py", line 448, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File
"/usr/lib/python2.4/site-packages/setuptools-0.6c7-py2.4.egg/pkg_resources.py", line 1166, in run_script
    execfile(script_filename, namespace, namespace)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/EGG-INFO/scripts/pyblosxom-cmd", line 25, in ?
    sys.exit(command_line_handler("pyblosxom-cmd", sys.argv))
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/commandline.py", line 392, in command_line_handler
    return f(command, argv)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/commandline.py", line 300, in run_static_renderer
    return p.runStaticRenderer(options.incremental)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/pyblosxom.py", line 426, in runStaticRenderer
    tools.render_url_statically(config, url, q)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/tools.py", line 929, in render_url_statically
    response = render_url(cdict, url, q)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/tools.py", line 982, in render_url
    p.run(static=True)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/pyblosxom.py", line 201, in run
    blosxom_handler(self._request)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/pyblosxom.py", line 1046, in blosxom_handler
    renderer.render()
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/renderers/blosxom.py", line 315, in render
    self.write("".join(self.renderContent(self._content)))
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/renderers/blosxom.py", line 262, in renderContent
    outputbuffer.append(self.renderTemplate(vars, "story", override=1))
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/renderers/blosxom.py", line 358, in renderTemplate
    finaltext = tools.parse(self._request, entry, template)
  File
"/usr/lib/python2.4/site-packages/pyblosxom-1.5-py2.4.egg/Pyblosxom/tools.py", line 478, in parse
    return _VAR_REGEXP.sub(replacer.replace, template)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 60:
ordinal not in range(128)

It seems to be a utf-8 issue because my entry file contains utf-8
special french characters.

Best regards,
Carl Chenet

Re: [pyblosxom-users] Updated markdown plugin

[will <wi...@bl...>]

I'll try to get to this (and a handful of other web-site related 
changes) in the next few weeks.


tchomby wrote:
> New markdown plugin for pyblosxom that uses python-markdown 2.0:
> 
>     http://gist.github.com/93153
> 
> Can this be added to the plugin registry?
> 
> The old markdown plugin that is still linked to in the pyblosxom
> plugin registry is a very old one. It contains a complete
> implementation of markdown inside the plugin itself, it's buggy, and
> it's unmaintained.
> 
> A while ago Benjamin Mako Hill posted a better plugin that uses
> [python-markdown], the leading implementation of markdown in python,
> rather than implementing markdown in the plugin itself. I've now
> updated that plugin to use the new python-markdown 2.0. This is much
> less buggy than the old markdown plugin that's in the registry,
> python-markdown is actively maintained, and python-markdown has a
> _lot_ of nice extra features in the extensions that come with it.
> Since we (the pyblosxom community) need only maintain a pyblosxom
> plugin that uses python-markdown via python-markdown's stable API, we
> will not need to release new versions of the plugin when bugs are
> fixed and features added to python-markdown, users can update their
> versions of python-markdown and the pyblosxom plugin will continue to
> work.
> 
> [python-markdown]: http://www.freewisdom.org/projects/python-markdown/

[pyblosxom-users] Updated markdown plugin

[tchomby <tc...@go...>]

New markdown plugin for pyblosxom that uses python-markdown 2.0:

    http://gist.github.com/93153

Can this be added to the plugin registry?

The old markdown plugin that is still linked to in the pyblosxom
plugin registry is a very old one. It contains a complete
implementation of markdown inside the plugin itself, it's buggy, and
it's unmaintained.

A while ago Benjamin Mako Hill posted a better plugin that uses
[python-markdown], the leading implementation of markdown in python,
rather than implementing markdown in the plugin itself. I've now
updated that plugin to use the new python-markdown 2.0. This is much
less buggy than the old markdown plugin that's in the registry,
python-markdown is actively maintained, and python-markdown has a
_lot_ of nice extra features in the extensions that come with it.
Since we (the pyblosxom community) need only maintain a pyblosxom
plugin that uses python-markdown via python-markdown's stable API, we
will not need to release new versions of the plugin when bugs are
fixed and features added to python-markdown, users can update their
versions of python-markdown and the pyblosxom plugin will continue to
work.

[python-markdown]: http://www.freewisdom.org/projects/python-markdown/

Re: [pyblosxom-users] support multiple comments per file

[Ryan B. <pyb...@ry...>]

heh, that was from rietveld. disregard. :P

On Fri, 6 Mar 2009, he...@gm... wrote:

> Reviewers: pyblosxom-users,
>
> Message:
> hi all! this change added support for multiple comments in a single
> file. it also added a script for "compacting" all comments for an entry
> into a single file.
>
> this improves performance for entries with large numbers of comments,
> which otherwise have to glob, stat, and read a large number of comment
> files during rendering.
>
> i've uploaded it to http://codereview.appspot.com/ , which is a
> lightweight, web-based code review tool. if anyone's interested in
> reviewing it, please do!
>
> (ignore the comments.js change; it's unrelated. it was supposed to go
> in, but i didn't mean to check it in in this change.)
>
> thanks in advance...
>
> Description:
> hi all! this change add support for multiple comments in a single file.
> it also adds a script for "compacting" all comments for an entry into a
> single file.
>
> this improves performance for entries with large numbers of comments,
> which otherwise have to glob, stat, and read a large number of comment
> files during rendering.
>
> (ignore the comments.js change; it's unrelated. it was supposed to go
> in, but i didn't mean to check it in in this change.)
>
> please review and provide feedback if you have any!
>
> Please review this at http://codereview.appspot.com/25074
>
> Affected files:
>   M    comments.js
>   M    comments.py
>   A    compact_comments.sh
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>

-Ryan

--
http://snarfed.org/

[pyblosxom-users] support multiple comments per file

[<he...@gm...>]

Reviewers: pyblosxom-users,

Message:
hi all! this change added support for multiple comments in a single
file. it also added a script for "compacting" all comments for an entry
into a single file.

this improves performance for entries with large numbers of comments,
which otherwise have to glob, stat, and read a large number of comment
files during rendering.

i've uploaded it to http://codereview.appspot.com/ , which is a
lightweight, web-based code review tool. if anyone's interested in
reviewing it, please do!

(ignore the comments.js change; it's unrelated. it was supposed to go
in, but i didn't mean to check it in in this change.)

thanks in advance...

Description:
hi all! this change add support for multiple comments in a single file.
it also adds a script for "compacting" all comments for an entry into a
single file.

this improves performance for entries with large numbers of comments,
which otherwise have to glob, stat, and read a large number of comment
files during rendering.

(ignore the comments.js change; it's unrelated. it was supposed to go
in, but i didn't mean to check it in in this change.)

please review and provide feedback if you have any!

Please review this at http://codereview.appspot.com/25074

Affected files:
   M    comments.js
   M    comments.py
   A    compact_comments.sh

Re: [pyblosxom-users] pagination

[Will G. <wi...@bl...>]

PyBlosxom doesn't do any pagination.  You'll need a plugin for that.

I'd suggest using wbgpager, but I've been told it's not working with 
PyBlosxom 1.4.x at the moment and I haven't fixed it yet.  I'll try to get 
to that in the next couple of days.

I don't know if there are other paging plugins.

/will


On Sat, 2 Aug 2008, Chris McCormick wrote:

> Hi,
>
> I set num_entries to 5 in my config.py and now 5 entries are showing on
> my blog. There doesn't seem to be a link to older entries though - is
> this something I have missed in my template or something?
>
> Best,
>
> Chris.
>
> -------------------
> http://mccormick.cx
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>

[pyblosxom-users] pagination

[Chris M. <ch...@mc...>]

Hi,

I set num_entries to 5 in my config.py and now 5 entries are showing on
my blog. There doesn't seem to be a link to older entries though - is
this something I have missed in my template or something?

Best,

Chris.

-------------------
http://mccormick.cx

Re: [pyblosxom-users] how to identify entry page in templates

[will <wi...@bl...>]

Hello!

You'll need to write a plugin to do it.  Maybe use the "story" callback, 
check to see if only one entry is being shown and if so, then populate a 
$discuss_js variable with one set of stuff and if not, populate it with 
the other set of stuff.

The comments plugin does this, too, so that may be a good start, but 
it's a big plugin so it might be hard to find what you're looking for in 
there.

I'm about to run out for the morning, otherwise I'd toss together a 
skeleton right now.  Sorry about that.  If you need help, let me know.

As an aside, it'd be good to have a disqus plugin--managing comments is 
not trivial even with all the comment rejection plugins and all the 
other things available.

/will


Wu Zhe wrote:
> I am using http://disqus.com/ for comments in my blog, it require
> different javascript code to embed into the blog entry pages and index
> pages, How can I differentiate entry page and index page in templates
> in order to insert the right javascript?

[pyblosxom-users] how to identify entry page in templates

[Wu Z. <jes...@gm...>]

I am using http://disqus.com/ for comments in my blog, it require
different javascript code to embed into the blog entry pages and index
pages, How can I differentiate entry page and index page in templates
in order to insert the right javascript?

-- 
Wu Zhe
Best Regards

Re: [pyblosxom-users] Solving the 500 Internal error from ImportError

[will <wi...@bl...>]

Brianna Laugher wrote:
> 
> I managed to get Pyblosxom 1.4.3 up and running by following
> <http://pyblosxom.sourceforge.net/1.4/manual/install_cgi.html> but
> putting config.py and pyblosxom.cgi in my base dir. It worked fine
> until I tried to click on the permalink to my first test entry. The
> permalink went to "http://domain.com/first-post.html" and not
> surprisingly it 404ed.
> 
> So I thought OK, maybe I was trying to be too clever, and I should put
> my config.py and pyblosxom.cgi in a cgi-bin dir after all. (I have no
> idea what difference it makes, CGI is one thing I know nothing about.
> I use Dreamhost shared hosting and I was just taking a punt that it
> would work at all. :))

CGI is a protocol that allows the web-server to execute processes on the 
server in a specified environment and return the resulting stdout as the 
response to the browser's request.

More specifically, the web-server sets up a bunch of environment 
variables and then runs pyblosxom.cgi in that environment.  That's it.

There are a couple of problems this creates:

1. it's very possible that the environment the web-server executes 
PyBlosxom in is different in some/many ways from the environment that 
you as a user can execute PyBlosxom in on the command line

2. it's often difficult to figure out what the web-server is doing 
internally to create the environment


> So I created the cgi-bin directory and moved config.py and
> pyblosxom.cgi there, and made my nice relative paths in config.py into
> absolute paths.
> 
> Running ./pyblosxom.cgi in the command line works without
> show-stopping complaint, but the website produces a 500 error thanks
> to not being able to import the right script.

When you say "thanks to not being able to import the right script", what 
error messages are you seeing that draw you to that conclusion?


> http://laugher.id.au/cgi-bin/pyblosxom.cgi

This url gives me a 404.

If you can let us know what the specific error messages are and/or give 
us a url that executes PyBlosxom, I can figure more out from that.

/will

[pyblosxom-users] Solving the 500 Internal error from ImportError

[Brianna L. <bri...@gm...>]

Hi,

I'm new to Pyblosxom but have some Python experience.

I managed to get Pyblosxom 1.4.3 up and running by following
<http://pyblosxom.sourceforge.net/1.4/manual/install_cgi.html> but
putting config.py and pyblosxom.cgi in my base dir. It worked fine
until I tried to click on the permalink to my first test entry. The
permalink went to "http://domain.com/first-post.html" and not
surprisingly it 404ed.

So I thought OK, maybe I was trying to be too clever, and I should put
my config.py and pyblosxom.cgi in a cgi-bin dir after all. (I have no
idea what difference it makes, CGI is one thing I know nothing about.
I use Dreamhost shared hosting and I was just taking a punt that it
would work at all. :))

So I created the cgi-bin directory and moved config.py and
pyblosxom.cgi there, and made my nice relative paths in config.py into
absolute paths.

Running ./pyblosxom.cgi in the command line works without
show-stopping complaint, but the website produces a 500 error thanks
to not being able to import the right script.

http://laugher.id.au/cgi-bin/pyblosxom.cgi

I have the codebase parameter set. I tried running python from the
cgi-bin dir, doing this:

>>> py = {}
>>> py["codebase"] = "/path/to/pyblosxom-1.4.3/"
>>> import os, sys
>>> sys.path.insert(0,py['codebase'])
>>> sys.path
['/path/to/pyblosxom-1.4.3/', '', '/usr/lib/python23.zip',
'/usr/lib/python2.3', '/usr/lib/python2.3/plat-linux2',
'/usr/lib/python2.3/lib-tk', '/usr/lib/python2.3/lib-dynload',
'/usr/local/lib/python2.3/site-packages',
'/usr/lib/python2.3/site-packages',
'/usr/lib/python2.3/site-packages/Numeric',
'/usr/lib/python2.3/site-packages/PIL']
>>> from Pyblosxom.pyblosxom import PyBlosxom
>>>
(/path/to/ changed for posting here, obviously)

OK, so that works!

Command-line pyblosxom.cgi works, why wouldn't the web one?

Is there some kind of CGI reset thing I can try?

Any theories would be welcome :)

thanks,
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/

Re: [pyblosxom-users] Getting 404 for urls that end in .[flavour]

[Fernando E. <com...@gm...>]

I found my mistake by reading through the code in the flavours. I had set
base_url to http://www.foo.com, I just changed it to
http://www.foo.com/index.cgi. Now the urls look like:
http://www.foo.com/index.cgi/index.rss20, and they work.

Now I will try to make the URLs look nicer, I hope  don't have to come back
here soon.

Thanks a lot for your very quick reply.

On Tue, Jun 17, 2008 at 7:41 AM, will <wi...@bl...> wrote:

> The 404 error is coming from your web-server--not from PyBlosxom.  So the
> index.rss20 request isn't getting routed to PyBlosxom....  In fact, no
> request gets through if it has any PATH_INFO bits.
>
> How do you have PyBlosxom deployed?  Are you using CGI?  Are you using
> Apache with an .htaccess file that has RewriteRules in it?  If so, what are
> the RewriteRules you're using?
>
> /will
>
>
>
> Fernando Espinoza wrote:
>
>> Hello.
>>
>> I installed pyblosxom yesterday, and have been trying to get it to work
>> for just too many hours.
>>
>> You can see in http://www.sanpanchoblog.com/ that the links for RSS,
>> comments, permanent link, etc... all result in 404s. Anything that ends with
>> foo.flavourname fails, but if I substitute foo/?flav=flavourname it works.
>>
>> e.g:
>> http://www.sanpanchoblog.com/index.rss20 FAILS
>> http://www.sanpanchoblog.com/?flav=rss20 SUCCEEDS
>>
>> What am I doing wrong? How can I fix this?
>>
>> You can see a copy of the output on debug mode at:
>> http://www.sanpanchoblog.com/dump.html
>>
>> Thank you.
>>
>

Re: [pyblosxom-users] Getting 404 for urls that end in .[flavour]

[will <wi...@bl...>]

The 404 error is coming from your web-server--not from PyBlosxom.  So 
the index.rss20 request isn't getting routed to PyBlosxom....  In fact, 
no request gets through if it has any PATH_INFO bits.

How do you have PyBlosxom deployed?  Are you using CGI?  Are you using 
Apache with an .htaccess file that has RewriteRules in it?  If so, what 
are the RewriteRules you're using?

/will


Fernando Espinoza wrote:
> Hello.
> 
> I installed pyblosxom yesterday, and have been trying to get it to work 
> for just too many hours.
> 
> You can see in http://www.sanpanchoblog.com/ that the links for RSS, 
> comments, permanent link, etc... all result in 404s. Anything that ends 
> with foo.flavourname fails, but if I substitute foo/?flav=flavourname it 
> works.
> 
> e.g:
> http://www.sanpanchoblog.com/index.rss20 FAILS
> http://www.sanpanchoblog.com/?flav=rss20 SUCCEEDS
> 
> What am I doing wrong? How can I fix this?
> 
> You can see a copy of the output on debug mode at: 
> http://www.sanpanchoblog.com/dump.html
> 
> Thank you.

[pyblosxom-users] Getting 404 for urls that end in .[flavour]

[Fernando E. <com...@gm...>]

Hello.

I installed pyblosxom yesterday, and have been trying to get it to work for
just too many hours.

You can see in http://www.sanpanchoblog.com/ that the links for RSS,
comments, permanent link, etc... all result in 404s. Anything that ends with
foo.flavourname fails, but if I substitute foo/?flav=flavourname it works.

e.g:
http://www.sanpanchoblog.com/index.rss20 FAILS
http://www.sanpanchoblog.com/?flav=rss20 SUCCEEDS

What am I doing wrong? How can I fix this?

You can see a copy of the output on debug mode at:
http://www.sanpanchoblog.com/dump.html

Thank you.