Upgrading

Upgrading ResourceSpace requires Subversion (SVN) to be installed on your server. Before upgrading you should ensure that your system meets the General installation requirements.

Open a Terminal/Command Prompt and change to the web root where ResourceSpace is installed (i.e. the location of 'login.php').

On Linux machines this may be:

/var/www/html/resourcespace

On Windows machines this may be:

C:/inetpub/wwwroot/resourcespace

Check to see if there are any modified files:

svn diff

If there are modified files it may be useful to save these to a text file in case of conflicts:

svn diff > before_upgrade.diff

Perform the upgrade by switching the code to the latest version in the releases branch:

svn switch https://svn.resourcespace.com/svn/rs/releases/9.7

or simply:

svn switch ^/releases/9.7

Converting a downloaded installation to a Subversion working copy

Using Subversion means upgrading is easier, particularly if you plan to make local changes that must be carefully merged. To convert your installation to a Subversion working copy, use:

svn co --force https://svn.resourcespace.com/svn/rs/releases/9.7 {path}

You can then update to the latest version of the checked out release simply by typing

svn update {path}

Troubleshooting

  • If you get an error similar to the following: "sqlite[S8]: attempt to write a readonly database" you need elevated permissions to run the SVN command. On Linux put "sudo" before the command and on Windows open the Command Prompt/Powershell as Administrator.
  • When using Command Prompt on Windows you will need to escape the ^ character. So the upgrade command would instead be "svn switch ^^/releases/9.7".
  • File and folder permissions of the code may be changed when upgrading. On Linux setting the ownership of the files to the user group www-data may resolve any permission issues.
  • If any issues occur during the upgrade that leave your checkout in a broken state, use the 'svn cleanup' command to fix this.