Serendipity Forums

ver 1.0 has been very stable on my server. I tried upgrading to the 1.1-beta, and while the installation works on my local system, on the server I get the directory source file list instead of an installation page. It behaves almost as if the .php is not recognized.

When I force the index.php file open it contains error messages about the database user/pass. I understand that is because it hasn't been installed properly. But without an installation page - I cannot change the database user/pass - do not know where those variables are stored.

Update: I cleared the directories and reinstalled ver 1.0. It works great. The only difference I can come up with is php version. My local system uses ver 5.1.4 and is able to run serendipity 1.1-beta. The remote server that cannot seem to install 1.1-beta runs php ver 4.4.1.

Oops: so in other words, many people using ISP's who usually are more conservative about upgrading their software *might* be screwed here?

I had the same problem when I installed the 1.1beta version. It would not work on my old server...

Can someone confirm this?

I have a copy of the nightlies (1.1.beta2) running on PHP 4.4.1 (cgi-fcgi) with EAccelerator under lighttpd. (Under OpenBSD on my beta site.)

I had no issues upgrading from 1.0.

I was running late this morning, so my post was kind of terse.

I would be happy to compare phpinfo with anyone, if someone would like to troubleshoot this...

It also might make sense for someone to ask for server error logs to troubleshoot the problem (or use something like php_value error_log to set the log path).

Hi Hindu!

That is really weird. Could you try to setup 1.1-beta in a different directory again, so that we could run a few tests? Like what happens if you call http://yourblog/serendipity_admin.php?

Serendipity should work fine with PHP 4.3.x! Even our new 1.1 version should.

Regards,
Garvin

Garvin - that is a great idea. Later this evening I'll install 1.1 in a subdirectory. Will be back with the results soon...

Hindu

Ok, I finally got around to doing this. I installed 1.1 beta in a subdir. When I go to that site, expecting to see the install screen, I get my directory structure laid bare for anyone to see.

To go further, I click on index.php, and get this (modified a bit to hide my exact directory structure, using brackets [] ):

Warning: mysql_connect(): Access denied for user: 'root@localhost' (Using password: NO) in /[my dir tree]/include/db/mysql.inc.php on line 264

Warning: mysql_select_db(): Access denied for user: 'root@localhost' (Using password: NO) in /[my dir tree]/include/db/mysql.inc.php on line 265

Warning: mysql_select_db(): A link to the server could not be established in /[my dir tree]/include/db/mysql.inc.php on line 265
serendipity error: unable to connect to database - exiting.

Hi!

If you get this message when you expect installation it means serendipity thinks its already installed. You can remove the 'serendipity_config_local.inc.php' file to force new installation; if you cannot remove that file check the FAQ on www.s9y.org about the 'fixperm.php' script.

About the "directory structure laid bare": This means that your webserver has enabled this and it does not use the default 'index.php' file to show serendipity. Sadly this is a webserver config issue, so you should contact your web admin if you don'T want to see directory views.

Best regards,
Garvin

Now I'm to the point that no matter what ver I have installed all you see is the dir tree. It won't default to the index.php file like it should. Something must be wrong in the "paths" table in the database, but looking at it it looks correct. Seems to be something I can't fix no matter how many times I reinstall.

Might have to wipe out the databases (and a year's worth of blog entries) to start from scratch.

Any ideas?

That sounds like either an .htaccess or permission problem. Have you tried the fixperm script Garvin wrote about?

No I have not. How do I do that? I think you are right it's a .htacess problem.

How do I fix that? It should be easy to fix that.

Hi!

Did you try to temporarily remove that .htaccess file?

I am quite sure we can save your blog entries! No worries!

Best regards,
Garvin