The WebIssues Server Manual
Issue tracking and team collaboration system

Upgrading the WebIssues Server

This chapter describes the procedure of upgrading the WebIssues Server to a newer version.

  1. Make sure nobody is using the system during the upgrade. Disable the cron job if it is enabled. Create a backup of the database and the directory where the WebIssues Server is installed.

  2. Delete all files and subdirectories in the installation directory except the storage and log subdirectories.

  3. Download and unpack the webissues-server package. Move all files from the unpacked directory to the installation directory.

  4. Create the storage and log subdirectories if they don't exist yet in the server's location. Make sure they are writable for the web server and not accessible to anyone else.

  5. Copy config/config-template.inc.php to config/config.inc.php and edit the created file to configure database connection and other settings. See Configuration for more information.

  6. Point your browser to the update.php script in the server's location, for example http://www.example.com/update.php and follow the installation steps. The script will check the configuration and update the database tables.

After the upgrade is finished, connect to your server using the WebIssues Desktop Client application to check if everything works correctly. Use the location of the index.php script as the server's URL, for example http://www.example.com/index.php.

If you wish to use email notifications, configure a cron job or Scheduled Task to periodically execute the cron.php script and make sure the mailing engine is configured correctly. Refer to the Notifications section for more details.

Warning

Make sure the configuration file, file attachments and server logs are not accessible for unauthorized users. See the Security chapter for more information about security settings.

You can check if the WebIssues Server is working by opening its URL in the browser. It will connect to the database, test if it is configured correctly and display a status message. You can also use the error log to check if there are any problems.