Problem: Can't load articles with long titles

[mutex]

Hello,

I use the s9y blog for more than a year. Yesterday I discovered the following problem:
When I want to read an article of my blog, which has a title length of more than 48 characters, I get the error message 500. Example: http://eric-scheibler.de/blog/index.php ... chten.html

Other entrys with a shorter title length are displayed correctly, example: http://eric-scheibler.de/blog/index.php ... refox.html

I'am sure, that this problem is new, earlyer I could read also the long title articles. I updated the blog to v1.5.5 and did also with the installed plugins, no success. My hoster has changed the php version to 5.3.6 a few weaks ago, could this cause the issue?

I hope you can help me
Thanks in advance
and best Regards

[kleinerChemiker]

I think, it's not a fault of s9y. I qwould guess a problem with the webserver (Apache) or maybe php. Which type of url rewrite do you use?

[Timbalu]

I guess you are running some kind of a home brew server... (lvm, encryption and whatever...) maybe there are restrictions?
What does the servers (php) error log say?
Did you test with a very long url independently from your Serendipity installation?

[mutex]

I don't know, which url rewriting I use, where can I check this?

No, I don't use a home server, It's a small hoster where I've bought a few mb to run my web site. I only have access via ftp and I can't check the php error log. I already contacted the support of the hoster but got no useful answer until now.

[Timbalu]

Yes, sorry asking. I didnt read about your hoster...
Error reporting is to be enabled in your webservers config and serendipity Configuration section.
I think you do not have it enabled.

Try to edit your .htaccess file and insert

Code: Select all

    php_value display_errors On

at the top of the file, reload the blank page with the long artikel title and have a look if you see an error message in your blog? This should lead to further clues.

[mutex]

ok, I changed the .htaccess file in the root folder of my blog. Now it looks like:

Code: Select all

# BEGIN s9y
php_value display_errors On
DirectoryIndex /blog/index.php

<Files *.tpl.php>
    deny from all
</Files>

<Files *.tpl>
    deny from all
</Files>

<Files *.sql>
    deny from all
</Files>

<Files *.inc.php>
    deny from all
</Files>

<Files *.db>
    deny from all
</Files>

# END s9y

I reloaded the page http://eric-scheibler.de/blog/index.php ... chten.html.
I got the same empty page back (error 500). Where can I find the potential php error messages?

btw. I also logged into my blogs admin page and clicked on "check installation". I got this error message: sql/db_update_0.6.8_0.6.9_mysql.sql damaged or changed: check failed
What does this mean? If the database wouldn't be accessible the whole blog should be empty or not? Could there exist a relation between this error and my problem?

And my hoster wrote, that he can't find a problem in his web server settings.

[kleinerChemiker]

With a server error you won't see any php error because the error occurs before php is loaded. Your provider should look in the error logs of the webserver and maybe set the loglevel higher.

The error has nothing todo with the error of the check.

edit: create a php-file with this code and pm me the link.

Code: Select all

<?php
phpinfo();
?>

[kleinerChemiker]

The problem is from suhosin, a security patch for php. Your variable names must not exceed 64 characters. You can try adding this code to your .htaccess but I don't know, if this is allowed by php/Apchae

Code: Select all

php_value suhosin.get.max_name_length 512

If this doesn't work, your provider has to change the value.

[mutex]

I've added your line to the .htaccess, now looks like:

Code: Select all

# BEGIN s9y
php_value display_errors On
php_value suhosin.get.max_name_length 512
DirectoryIndex /blog/index.php
...

Doesn't work... is there anything else I can do? Should my hoster change something in the server settings? Is this possible at all cause you wrote that's a security patch?

[kleinerChemiker]

Your hoster has to change the suhosin configuration. Or else you have to use shorter Titles.

[mutex]

Thank you for your help. I sent an e-mail to my hoster. I hope that he will change the value.
Best regards

[mutex]

Hmm, my hoster changed the value to 512 but I still can't access the long title articles, same error and the php log file contains no relevant entrys. Is there anything else I can do?

[kleinerChemiker]

1) You won't see anything in the php log file, the error should be in the error log of apache.
2) phpinfo() says that nothing is changed. Maybe he should also change the value for "post" and not only for "get".