Borked upgrade from .71 to .82

[peteri]

Following from the RPC-XML exploit warnings I've done the upgrade.

Now I seem to be having problems getting anything at all out of my blog.

I'm still waiting on my ISP to kill and restart PHP incase some caching weirdness is happening, but I thought I'd post my results below.

I did get some rename warnings during the upgrade process
i.e.
Warning: rename (/path/serendipity.inc.php,/path/backup/serendipity.inc.php) Operation not permitted in /path/include/functions_installer.inc.php on line 792.

Now given the paths involved in this I'm guessing I'm safe to ignore these above. The whole thing finished with:
Calling serendipity_installFiles ...
Calling serendipity_removeObsoleteVars ...
Calling serendipity_plugin_api::create_plugin_instance ...
Error: serendipity_event_browsercompatibility:3a81e442583e0726e948f511396340cc ()
Calling serendipity_installFiles ...
Calling serendipity_installFiles ...
Calling serendipity_fixPlugins ...
Calling serendipity_smarty_purge ...

Your Serendipity installation is now upgraded to version 0.8.2

So does anyone have any clues? The PHP version is 4.3 BUT I'm running on a different server from one I originally installed serendipity on and it's actually Mac OSX so all kinds of weirdness could be happening (I had chmod over ftp on the original web server, I don't on the new one).
This is the first time I've done an upgrade on this webserver.

serendipity_config_local.inc.php has "versionInstalled" set to 0.8.2 so I presume the upgrade script thinks it's done it's work.

[garvinhicking]

You should be able to ignore the errors. As you can see in the migration document from 0.7 to 0.8 (see www.s9y.org) there are a lot of obsolete files moved and deleted on your server in the upgrader. If it doesn't work it just means you should manually remove the obsolete files.

Regards,
Garvin

[peteri]

That was my guess too.
If restarting the PHP process doesn't work, if I delete all of the s9y directories then put it back in should I be able to get a working version?

Does upgrading the DB put out anything as part of the process?
I can't see anything in the "final" sucess page that actually says "upgrading the DB".

[garvinhicking]

You only need to remove the files that are marked as obsolete; this is referred in the 0.7 -> 0.8 upgrade documentation.

Do not delete all of the s9y dir and put it back, that will do nothing. And the DB update only reports errors if they occur. You could check your sql/db_update*.sql files and see what they did and if it is reflected in your database. Like check if you now have a table called serendipity_entryproperties; if it exists, it means s9y did perform the DB upgrade.

Regards,
Garvin

[peteri]

Hmm it's very odd.
Finally got around to doing some double checking (setting the production variable to debug in serendipity_config.inc.php ) which means I went off to web-sniffer.net to see what the headers looked like.

I'm getting 302 errors which are pointing off into foo.example.com.
This looks like a default Apache error message.
Is there anything I can get my webhost to check (this setup used to work with 0.7.1)

[Guest]

Hallo all,
i`ve got the update to 0.8.2 and got the following message too.

Error: serendipity_event_browsercompatibility:3a81e442583e0726e948f511396340cc ()

May i have to do anything to make s9y work correctly or not?

Sorry, my english is not the best.

Thanks for answer.

Best regards
Sabine