Serendipity Forums

Hello folks.

I have just installed serendipity onto my webserver and am trying to embed the blog onto the main page of the site, in order to act as a news feed type thing. After a bit of tinkering I managed to get the embedding to work. I have a wrapper.php file in the serendipity directory and it displays through main page outside that direstory (../news/news.php to be exact). No dramas it is doing what I want.

But, in order to get rid of all the headers and such I went into the configuration panel and turned on the 'embedding' option, nothing else was changed. After checking and saving (successfully) I can no longer connect to the database. I have since found that even by simply opening the configuration panel and clicking save, I get this problem.
Any ideas?

Cheers
Scott

Hi!

Could it be that your browser is filling in invalid information into the database credentials input fields? Firefox3 seems to have an annoying functionality that always uses your LOGIN password in ANY kind of password field, and thus might overwrite the real database password with your invalid login password.

Regards,
Garvin

I am using Firefox 3, but I have no idea how to check if that is happening. I can't access anything of Serendipity, not even the admin stuff, so I can't change any settings back. I just recopy Serendipity and reinstall it. All the 'posts' I have entered are still fine. But I just go back to where I was.

PS, the problem persists in Safari too.

Hi!

If it happens in Safari too, then it's not what I supposed. What happens when you change the configuration exactly, which kind of error do you get?

Does invalid data get stored in the serendipity_config_local.inc.php file, can you check that file and see if the right database info is stored in there after you save the configuration? Also check the .htaccess file and see if it gets changed to something like before.

If you cannot access either of these mentioned files, check the "fixperm.php" script mentioned in the FAQ on www.s9y.org.

HTH,
Garvin

Hello again,

Cheers for the advice, it seems for some reason the wrong password was in the 'database password' field by default (my admin password instead). I don't know how, but it used the right password until I entered the configuration panel. Then when I saved, it used the wrong one from then on... Since changing it back haven't had any problems since.

Thanks again
Scott