Updating GLPI
This page covers how to update to a new GLPI release.
Updating GLPI Network Cloud
If you're on a GLPI Network Cloud plan, we'll upgrade your GLPI automatically with each new release; no action needed on your end (unless you're using the GLPI Network Cloud Private offer – so you may ask the upgrade on demand)
How soon we upgrade your instance depends on the type of release:
Security fixes: One week before the public release
Minor releases (e.g., 10.0.18 to 10.0.19): Usually about a week
Major releases (e.g., 10.0.20 to 11.0.0): Longer, usually months (just to make sure everything goes smoothly)
GLPI Network Cloud Private customers can request an update at support.teclib.com. Include the URL of the GLPI Network Cloud instance you want us to upgrade.
Updating a Self-Hosted GLPI
This page covers the updating process of an instance that was installed following this article. If your installation was made with different steps, please make sure to adapt commands and paths according to your environment.
Here are the steps for updating to a new GLPI version (major or minor):
Back up of your application database and files
The application database keeps track of everything of your GLPI instance. It is very unlikely you'll need to roll back to your current version, nevertheless it is always great to have a point of coming back in case something goes wrong.
Never try to import a GLPI database backup to a different version without using the update scripts contained here.
You should not try to restore a database backup on a non empty database (say, a database that has been partially migrated for any reason).
Make sure your database is empty before restoring your backup and try to update, and repeat on fail.
Download latest GLPI version
On http://glpi-project.org/download, find the latest version, and download it to your server, and extract it to an empty folder where your Web Server may find it.
Ensure target directory is empty and extract files there
Restore the
downstream.phpfile previously backed up
This procedure follows the standard Filesystem Hierarchy Standard (FHS) to clearly separate critical elements: configuration files (including the encryption key), application sources, variable data, and logs.
This organization strengthens the security and maintainability of the instance. For more information, see the installation article.
Update GLPI
Open the GLPI Instance URL on your browser, or (recommended) use the php bin/console db:update command line tool
The command line tool will check the integrity of your database to identify changes that could compromise the update, and run migrations to update GLPI
As soon as a new version of GLPI files is detected, you will not be able to use the application until the update process has been finished.
Specific migration of GLPI 10 plugins to GLPI 11
Here you will find the procedure to migrate GLPI 10 to GLPI 11, as well as the following plugins:
Generic Objects (now included in the core)
Fields (required if you use Fields with FormCreator)
FormCreator (now included in the core)
We recommend updating these three plugins before beginning your migration. This will save you from having to install the plugins on your new instance in order to prepare for their migration. Fields, however, must be installed in all cases.
If you have two or more of the plugins listed above, migrate them in the order indicated.
If you are using a Cloud version, plugin migration will be automatic. Migration from GLPI 10 to GLPI 11 will be available upon request only (coming soon).
Plugin migration
Generic Objects
If your plugin was not up to date before the migration (version prior to 2.14.14), please download and activate the plugin from the marketplace. Otherwise, proceed to the section ‘Enter the following command’.
Generic Objects plugin enabled
If you are migrating to a new instance, remember to copy the plugin files from the /files/_plugins/genericobject directory to the new files/_plugins/ directory of your new instance.
By clicking on the wrench icon, you can view the items detected by the plugin that will be migrated.
Run the following command
For Ubuntu and similar systems:
For CentOS and similar systems:
The process may take some time if you have a large amount of data to migrate. You should get a result similar to the following:
The migrated elements will be visible from the park as well as from the Generic Objects plugins.
Fields
If you are migrating to a new instance, remember to copy the plugin files from the /files/_plugins/fields directory to the new files/_plugins/ directory of your new instance.
This is not a migration per se, but you must ensure that the plugin is present and enabled.
FormCreator
If your plugin was not up to date before the migration (version prior to 2.13.10), please install and activate the FormCreator plugin. Otherwise, proceed to the section ‘Enter the following command’.
From
Tools>Formcreator EOL Info, you can view the number of forms to be migrated and those natively present in GLPI (2 by default).
Then run the following command
For Ubuntu and similar systems:
For CentOS and similar systems:
The process may take some time if you have a large amount of data to migrate. You should get a result similar to the following:
You can view the result from the migration status via Tools > Formcreator EOL Info.
You find a video covering this process below:
Last updated