Database changes from latest stable release to 1.2_alpha2

[jaal]

Hi all,

this is my current situation:

I've forked a testing tree from my stable blog, named test-blog (pretty clever, hm? ).
Then I've upgraded my test-blog to 1.2_alpha2. But well Murphy had to be around here, I didn't realized that I've to change the database in the configfiles. And in the database itself.
Then I've loaded the test-blog and did the upgrade. The upgrade should have upgraded just the original database, no files at all.

Yes, at that point I could have reverted all by just copying back the copy db from the original, but well... um... I tried and deleted the copy... yes, pretty mean, hm?

So are the changes revertable? I'm currently missing some features as checking for updates of the plugins and so on...

Thanks
Jan

[garvinhicking]

Hi Jaal!

Actually the DB upgrade should have done nothing bad to your tables. It just changed the length of a column and added a new column to the category table. With both changes you can run Serendipity 1.1 without any problems!

The only thing you might need to inspect if all plugins are still properly installed?

Best regards,
Garvin

[jaal]

The only thing you might need to inspect if all plugins are still properly installed?

It seems that some of the plugins are failing.

Even if there was only a DB upgrade (or does the upgrade script install some files?) the trackback check is not working properly and the check for updates plugins is not working.
And if the upgrade has just done the changes you mentioned they should work?!

Thanks
Jan

[garvinhicking]

Hi Jaal!

So you backgraded from 1.2 to 1.1 again, did I understnad that right? Or are you still using 1.2?

If you backgraded all files, then all should work as previously...what messages do you get for trackback checking exactly?

Regards,
Garvin

[jaal]

So you backgraded from 1.2 to 1.1 again, did I understnad that right? Or are you still using 1.2?

Erm, no.

I'm still on 1.2-alpha2. But the only thing the upgrade should have done is changing the database and the serendipity_config.inc.php. (That's what I see with diff so far...)

This is what I do get from the trackbacks:

"ende XML-RPC ping zu rpc.pingomatic.com...Success!!
Sende XML-RPC ping zu ping.blo.gs...Failure(Reason: Invalid return payload: enable debugging to examine incoming payload)
Sende XML-RPC ping zu rpc.blogrolling.com...Success!!
Sende XML-RPC ping zu rpc.technorati.com...Success!!
Sende XML-RPC ping zu rpc.weblogs.com...Failure(Reason: Invalid return payload: enable debugging to examine incoming payload)
Sende XML-RPC ping zu ping.ge.bloggt.org...Success!!
Sende XML-RPC ping zu api.my.yahoo.com...Success!!
Sende XML-RPC ping zu blogsearch.google.com...Success!!
Posting to Serendipity...
xml_rpc_client: Connection to RPC server :80 failed. Success
Notice: xml_rpc_client: Connection to RPC server :80 failed. Success in /blog/bundled-libs/PEAR.php on line 848
xml_rpc_client: Connection to RPC server :80 failed. Success"

The last line is interesting: This error was not there befor the upgrade...

Jan

[garvinhicking]

Hi!

Ah, now we're on the same page.

It seems like your upgrade coincidentally collided with a change on your server. According to the output of the plugin, it seems that your webserver is rejecting outgoing connections to the mentioned services.

That "Success!" message usually comes from fsockopen() when socket connections are somehow not completely routable through your network.

Do you know where that "Posting to Serendipity" comes from? I don'T remember that output coming from Serendipity?

So IMHO these changes are caused by a change on your server's network routing, and you just think they might be realted to the s9y upgrade. My bet is that if you backgrade to your previous s9y version, the error will still be there, as it's not related to serendipity itself, but rather your server...

HTH,
Garvin

[jaal]

Okay, I did some testing (this time I did a lot of backups...), and without changing something on the original blog the "check for plugin updates" buttons have reappeared... That seems to match the change you mentioned.

Do you know where that "Posting to Serendipity" comes from? I don'T remember that output coming from Serendipity?

I think they're coming from this plugin:
"LiveJournal/MySpace Aktualisierung"

I don't really remember why I have installed this plugin (I don't use this for myspace/LJ, and because I have set it to "serendipity" it seems that it way because of some internal things...) but it seems to be responsible for the output. But it's quite interesting: It worked until the upgrade I did...

If I deactivate thsi plugin I do get:

Sende XML-RPC ping zu rpc.weblogs.com...Malformed response.
Notice: Malformed response. in /home/salid/public_html/blog2/bundled-libs/PEAR.php on line 848
Malformed response.

Okay. This is a clean installation with a database copy from my original. As you mentioned the changes we non destructive to an old version, this should be a problem of the remote service.

So thanks for your help.

Jan

[garvinhicking]

Hi!

Exactly - the current error message comes frmo the "weblogping" / " Announce entries" plugin. Its unresponsiveness is caused by the network routing change I mentioned, yes...

Best regards,
Garvin

[jaal]

Hell, the error was that the system didn't have had access to the plugins directory. After I've changed the permissions to the webserver, it does work...