Page is a draft due to changes in included resources
You are viewing an old version of this page. Return to the latest version.
Difference between revisions of "Setup:Installation Guide/Patch Update"
| [quality revision] | [quality revision] |
(Tag: Visual edit) |
(Tag: Visual edit) |
For large version jumps (e.g., BlueSpice 2.27.3 to 3.1.10), a new installation is generally recommended.
For a patch update (for example, version 3.1.x to a higher version 3.1.x) you can simply follow these steps:
- Create a backup: Pull a dump of the database and save it together with the complete codebase to a backup location of your choice.
- Renew Codebasethe codebase: Overwrite the Codebase codebase of the current version with the new Codebase codebase of the higher version.
-
Compare: After the overwrite, please compare the following files and folder. Copy from your backup location if necessary
-
If you have a custom skin, please check the
skins/folder. -
LocalSettings.php -
extensions/BlueSpiceFoundation/config -
settings.d/Insettings.d, especially*.local.phpfiles. Copy from your backup if necessary.
-
If you have a custom skin, please check the
-
Run the update:
- Open a console and go to the installation folder (on the LocalSettings.php level)
-
Then enter the following command:
php maintenance/update.php
Note: In a patch update, usually no database schemas have changed. It may not be necessary to run 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.
For large version jumps (e.g., BlueSpice 2.27.3 to 3.1.10), a new installation is generally recommended.
For a patch update (for example, version 3.1.x to a higher version 3.1.x) you can simply follow these steps:
#'''Create a backup:''' Pull a dump of the database and save it together with the complete codebase to a backup location of your choice.
#'''Renew Codebasethe codebase:''' Overwrite the Codebasecodebase of the current version with the new Codebasecodebase of the higher version.
#'''Compare''': After the overwrite, please compare the following files and folder. Copy from your backup location if necessary
##If you have a custom skin, please check the <code>skins/</code> folder.
##<code>LocalSettings.php</code>
##<code>extensions/BlueSpiceFoundation/config</code>
##<code>settings.d/</code>In <code>settings.d</code>, especially <code>*.local.php</code> files. Copy from your backup if necessary.
#'''Run the update:'''
##Open a console and go to the installation folder (on the LocalSettings.php level)
##Then enter the following command: <code>php maintenance/update.php</code>
Note: In a patch update, usually no database schemas have changed. It may not be necessary to run update.php.
<br />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 [[Setupsetup:Installation Guide/Security Settings/File System Permissions|File System Permissions]].
{{Box Note|boxtype=note|Note text=In a patch update, usually no database schemas have changed. It may not be necessary to run update.php.}}<br />
[[en:{{FULLPAGENAME}}]]
[[de:Setup:Installationsanleitung/Patch_Update]]| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
For large version jumps (e.g., BlueSpice 2.27.3 to 3.1.10), a new installation is generally recommended. | For large version jumps (e.g., BlueSpice 2.27.3 to 3.1.10), a new installation is generally recommended. | ||
| − | For a patch update (version 3.1.x to a higher version 3.1.x) you can simply follow these steps: | + | For a patch update (for example, version 3.1.x to a higher version 3.1.x) you can simply follow these steps: |
#'''Create a backup:''' Pull a dump of the database and save it together with the complete codebase to a backup location of your choice. | #'''Create a backup:''' Pull a dump of the database and save it together with the complete codebase to a backup location of your choice. | ||
| − | #'''Renew | + | #'''Renew the codebase:''' Overwrite the codebase of the current version with the new codebase of the higher version. |
| + | #'''Compare''': After the overwrite, please compare the following files and folder. Copy from your backup location if necessary | ||
| + | ##If you have a custom skin, please check the <code>skins/</code> folder. | ||
| + | ##<code>LocalSettings.php</code> | ||
| + | ##<code>extensions/BlueSpiceFoundation/config</code> | ||
| + | ##<code>settings.d/</code>In <code>settings.d</code>, especially <code>*.local.php</code> files. Copy from your backup if necessary. | ||
#'''Run the update:''' | #'''Run the update:''' | ||
##Open a console and go to the installation folder (on the LocalSettings.php level) | ##Open a console and go to the installation folder (on the LocalSettings.php level) | ||
##Then enter the following command: <code>php maintenance/update.php</code> | ##Then enter the following command: <code>php maintenance/update.php</code> | ||
| + | <br />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 [[setup:Installation Guide/Security Settings/File System Permissions|File System Permissions]]. | ||
| − | Note | + | {{Box Note|boxtype=note|Note text=In a patch update, usually no database schemas have changed. It may not be necessary to run update.php.}}<br /> |
| − | |||
| − | |||
| − | |||
| − | |||
[[en:{{FULLPAGENAME}}]] | [[en:{{FULLPAGENAME}}]] | ||
[[de:Setup:Installationsanleitung/Patch_Update]] | [[de:Setup:Installationsanleitung/Patch_Update]] | ||