pyblosxom

Seb wrote:
> This allows for serving UTF-8 characters in stories and in any files of
> the flavor.  However, if any of these characters are used in
> /etc/pyblosxom/config.py, then the engine fails and the following error
> is displayed:
> 
> ---<---------------cut here---------------start-------------->---
> Internal Server Error
> The server encountered an internal error or misconfiguration and was unable to complete your request.
> Please contact the server administrator, webmaster@... and inform them of the time the error occurred, and anything you might have done that may have caused the error.
> More information about this error may be available in the server error log.
> ---<---------------cut here---------------end---------------->---
> 
> For instance, trying to set:
> 
> py['blog_description'] = "Canción"

What's in the error log?

will wrote:
> Seb wrote:
>> This allows for serving UTF-8 characters in stories and in any files of
>> the flavor.  However, if any of these characters are used in
>> /etc/pyblosxom/config.py, then the engine fails and the following error
>> is displayed:
>>
>> ---<---------------cut here---------------start-------------->---
>> Internal Server Error
>> The server encountered an internal error or misconfiguration and was 
>> unable to complete your request.
>> Please contact the server administrator, webmaster@... and 
>> inform them of the time the error occurred, and anything you might 
>> have done that may have caused the error.
>> More information about this error may be available in the server error 
>> log.
>> ---<---------------cut here---------------end---------------->---
>>
>> For instance, trying to set:
>>
>> py['blog_description'] = "Canción"
> 
> What's in the error log?

Now that I think about it, I bet I know what the problem is.  Try adding 
the following line to the top of your config.py file:

# -*- coding: utf-8 -*-

That tells Python that the config.py file is also in utf-8.

I know that works locally.  Let me know if that works for you.

/will

On Thu, 22 May 2008 18:14:52 -0400,
will <willg@...> wrote:

[...]

> What's in the error log?

I haven't used one before, but trying:

py['log_file'] = "/tmp/pyblosxom.log"

doesn't create the log file at all.  I don't think it's a permissions
issue, because I can write to /tmp as my user.  What should this be set
to, or where is the default log file?


-- 
Seb

On Thu, 22 May 2008 18:19:55 -0400,
will <willg@...> wrote:

[...]

> Now that I think about it, I bet I know what the problem is.  Try adding 
> the following line to the top of your config.py file:

> # -*- coding: utf-8 -*-

> That tells Python that the config.py file is also in utf-8.

> I know that works locally.  Let me know if that works for you.

Absolutely, that fixes it.  I'd still like to know how to properly set
the log file to check stuff in the future though.  Thanks!


-- 
Seb

Seb wrote:
> On Thu, 22 May 2008 18:14:52 -0400,
> will <willg@...> wrote:
> 
> [...]
> 
>> What's in the error log?
> 
> I haven't used one before, but trying:
> 
> py['log_file'] = "/tmp/pyblosxom.log"
> 
> doesn't create the log file at all.  I don't think it's a permissions
> issue, because I can write to /tmp as my user.  What should this be set
> to, or where is the default log file?

The error your getting is showing up in your web-server's log, not the 
PyBlosxom one.  It's possibly in /var/log/apache2 or somewhere around there.

/will

On Monday 05 May 2008 16:25:06 sigi wrote:
> I activated mod_rewrite with a .htaccess-file as mentioned in your
> documentation with:
> RewriteEngine on
> RewriteRule  ^(.*)$ /cgi-bin/pyblosxom.cgi/$1  [last]

That's what I'm using. It took me a while to get around to using mod_rewrite, 
but it does make for much clearer URLs.

> The rewriting works well, but I can't get the comments-plugin working
> now: It simply rejects all incoming comments.
> My datadir is set to /var/www/ - if I set comment_dir to
> /var/www/comments (where it's located) or not, doesn't make any
> difference.

> The standard form-method in my comments-form looks like
> <form method="post" action="$base_url/$file_path.$flavour#comment_anchor"
> name="comments_form"> I also tried to give the static url,
> /cgi-bin/pyblosxom.cgi included, but that didn't help.

I was having some issues with submitting comments. I think it was related to 
whether people came to my site with a URL without the http://www. I ended up 
changing my comment-form.html to hard-code the base URL as below

<form method="post" action="/cgi-bin/pyblosxom.cgi/$file_path"

That seems to work.

Good luck.

-- 
Steve

On Mon, May 05, 2008 at 10:13:38PM +0100, Steve Clark wrote:
> On Monday 05 May 2008 16:25:06 sigi wrote:
> 
> > The rewriting works well, but I can't get the comments-plugin working
> > now: It simply rejects all incoming comments.
> > My datadir is set to /var/www/ - if I set comment_dir to
> > /var/www/comments (where it's located) or not, doesn't make any
> > difference.
> 
> > The standard form-method in my comments-form looks like
> > <form method="post" action="$base_url/$file_path.$flavour#comment_anchor"
> > name="comments_form"> I also tried to give the static url,
> > /cgi-bin/pyblosxom.cgi included, but that didn't help.
> 
> I was having some issues with submitting comments. I think it was related to 
> whether people came to my site with a URL without the http://www. I ended up 
> changing my comment-form.html to hard-code the base URL as below
> 
> <form method="post" action="/cgi-bin/pyblosxom.cgi/$file_path"
> 
> That seems to work.

I now figured out, that my plugin spamquestion.py caused the error - I 
disabled it, and now without it everything works fine... 

sigi