Setup:Installation Guide/Patch Update: Difference between revisions

(Created page with "For large version jumps (e.g., BlueSpice 3.2.x to 4.2.x), a new installation is generally recommended. For a patch update (for example, version 4.1.x to a higher version 4.1....")
Tag: 2017 source edit
 
m ((username removed) (log details removed))
(No difference)

Revision as of 13:39, 21 March 2022

For large version jumps (e.g., BlueSpice 3.2.x to 4.2.x), a new installation is generally recommended.

For a patch update (for example, version 4.1.x to a higher version 4.1.x+) you can simply follow these steps:

  1. Create a backup: Pull a dump of the database and save it together with the complete codebase to a backup location of your choice.
  2. Renew the codebase: Overwrite the codebase of the current version with the new codebase of the higher version.
  3. Compare: After the overwrite, please compare the following files and folder. Copy from your backup location if necessary
    1. If you have a custom skin, please check the skins/ folder.
    2. LocalSettings.php
    3. extensions/BlueSpiceFoundation/config
    4. settings.d/In settings.d, especially *.local.php files. Copy from your backup if necessary.
  4. Run the update:
    1. Open a console and go to the installation folder (on the LocalSettings.php level)
    2. Then enter the following command: php maintenance/update.php


If you use Linux as the basis of your BlueSpice installation, please note that file system permissions may be lost when overwriting the codebase. More information can be found under File System Permissions.

Note:In a patch update, usually no database schemas have changed. It may not be necessary to run update.php.




To submit feedback about this documentation, visit our community forum.