Serendipity Forums

Hello,

My webhost recently upgraded from PHP version 4.4.9 to 5.2.17 and my S9y 1.5.2 install is now dysfunctional. I see mention in the installation notes about needing to be on S9y 1.5.5 or later. I attempted to do an upgrade to V 1.6 after backing up my database and then expanding the contents of a Serendipity install archive over top my existing installation but I can't seem to trigger the upgrade. My blog location: http://klyment.com/serendipity/. Help, please. =) I hope it's something really simple I've overlooked.

Thank you. =D

This might be a change of your physical path, Try to find out ... and if so, you might be able to reset it with your Database Admin Tool, like PhpMyAdmin, with (Note: change the table prefix to yours)
Your errors were:

Warning: Smarty error: unable to read resource: "404.tpl" in ....

Warning: readfile(../menu.htm): failed to open stream: No such file or directory in /hsphere/local/home/klyment0/klyment.com/serendipity/content.php on line 23

Ian,

Thank you for your response. =) It appears as though my physical path was changed from /hsphere/local/home/klyment/klyment.com/serendipity/ to /hsphere/local/home/klyment0/klyment.com/serendipity/. I updated the serendipityPath variable in the serendipity_config table with the new path but am still getting the same error and am still not able to invoke the upgrade. Anything else I could check?

You still have that error.
Warning: readfile(../menu.htm): failed to open stream: No such file or directory in /hsphere/local/home/klyment0/klyment.com/serendipity/content.php on line 23

Is it there?
Is it readable?
Is it an embedded installation? Check all path settings.
Where do you have other full path settings?
...

Sorry . . . I changed it back to the original setting but have changed it back again to the current physical path.

I removed what was on line 23 of content.php (it was calling menu.htm . . . used to be a menu bar tacked on below the blog) but the error still seems to be showing up for some reason.

I changed all other instances I could find of the full path: two more in serendipity_config related to anti-spam log files, one in serendipity_pluginlist related to serendipity_event_bbcode though the search brought up an additional 55 entries all in serendipity_pluginlist but I wasn't able to see the full path visible anywhere in each of the records.

Again, do I need to trouble shoot this before I can invoke the upgrade? The upgrade/installation documentation specifically notes that I need to be on S9y 1.5.5 or later if I am running PHP5 on my server. I'm hoping that an upgrade will "magically" make everything work again.

Klyment wrote:Sorry . . . I changed it back to the original setting but have changed it back again to the current physical path.

???

Klyment wrote:I removed what was on line 23 of content.php (it was calling menu.htm . . . used to be a menu bar tacked on below the blog) but the error still seems to be showing up for some reason.

Try to clean up the files in templates_c. There all compiled templates reside.

Klyment wrote:Again, do I need to trouble shoot this before I can invoke the upgrade? The upgrade/installation documentation specifically notes that I need to be on S9y 1.5.5 or later if I am running PHP5 on my server. I'm hoping that an upgrade will "magically" make everything work again.

Serendipity is magic!! Yes. But you will need to solve that first, I assume.

check into http://www.klyment.com/serendipity/sere ... _admin.php
and check all the absolute path settings in configurable options.

If this does not clear things up:
* try a different templates style.
* check again sitewide absolute path settings
* did you ask your ISP about changes?
* check /tmp path settings to be writable
* ....
* make sure your .htaccess and serendipity_config_local.inc.php files, the plugins/ , uploads/ and templates/ dirs are really writable
* upgrade your Serendipity (it can't get more worse, than now)
*
* always clear browsers and smarty compile caches to be sure a reload hits the truth.

So . . . it turns out my webhost did a full migration of a bunch of servers which included new database servers and new host names for FTP servers. Apparently I was uploading to the old servers which were no longer serving my domain. Thanks for helping me with this trouble shooting and sorry for being a nuisance. =)

We love having nuisances like that, specifically if they get solved into 'sweetness'!