ResourceSpace Upgrade

[Matt Cooper]

Hi all,

what's the best way to upgrade Resourcespace to the latest revision?

We are going from revision 2055 to the latest (4220). I have tried
once but got the following:

"Please go back and try something else.

You can check your installation configuration.

/path/resourcespace/include/db.php line 997: unserialize()
[function.unserialize]: Error at offset 0 of 72 bytes"

Would I be better to manually drop the directories for the new release
in and tes that way? Obviosuly take a copy of my config.php.

Any help appreciated.

Thanks, Matt

[Matt Cooper]

It seems the directories are OK but the database doesn't seem to get upgraded. Anyone any tips? Is there an SQL schema that needs uploaded?

Here is my process:

1. Take a copy of config.php
2. create a directory on the same level as resourcespace "temp"
3. Grab the latest svn of ResourceSpace
4. cp -R newdir/* /olddir   --- copy everything from new directory into old directory
5. Browse to site for installer
6. Run the installer and then try to login

Get the following error:

Please go back and try something else.

You can check your installation configuration.

---

/var/www/resourcespace/include/db.php line 997: unserialize() [function.unserialize]: Error at offset 0 of 72 bytes

Am I missing something here? svnupdate seems to be giving similar results.

Thanks, Matt

[Tom Gleason]

It looks like one of your plugins has config column data that is invalid. 

You might be able to fix this by deleting the config column of the plugins table, but you'll have to reconfigure your plugins. You may be able to track it down to a specific plugin to clear that config field. 

--
 
 

--
Tom Gleason
Buildadam - ResourceSpace Hosting & Development

Colorhythm LLC
http://www.colorhythm.com

Main Office:  +1 415-399-9921
Fax: +1 253-399-9928
Mobile:  +1 347-537-8465

tgle...@colorhythm.com

[Tom Gleason]

config column data should be a base64 encoded serialized php array, so if you see a config value that is not a base64 string, that's probably the culprit.

[Matt Cooper]

OK should I perhaps disable and remove the plugins on our original install and then run the upgrade? Or should I look at the database for non base64 and change it? Thanks for the help. Matt

[Tom Gleason]

It's up to you how you fix it. You could simply delete the plugins table, but depending on how much info you want to preserve about active plugins and their configs, you might want to just find the broken one and delete that config field.

--
 
 

[Matt Cooper]

Hi,

I have finally got back round to sorting this one.

I removed the config column from the plugings table and was able to get to the login screen.

Logged in and got the following error:

/var/www/resourcespace/include/header.php line 418: Use of undefined constant __DIR__ - assumed '__DIR__'

Can anyone help?

Thanks, Matt