2015-04-15 18:26:18 +03:00
|
|
|
---
|
|
|
|
title: Update
|
|
|
|
show_in_menu: contents
|
|
|
|
nav_sort: 10
|
|
|
|
---
|
|
|
|
|
|
|
|
# Plugin update
|
|
|
|
|
|
|
|
Update procedure can vary from plugin to plugin but the common steps are the
|
2017-11-01 04:08:13 +03:00
|
|
|
same and listed below. Also it's recommended to check the README file shipped
|
|
|
|
with a plugin before update.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
## The process
|
|
|
|
|
|
|
|
### Get the plugin
|
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
First of all you need to download the plugin. In most cases plugin's author
|
|
|
|
provides prepared `.zip` (or `.tar.gz`) archive with the code.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
The list of all stable and officially approved plugins can be found at the
|
|
|
|
[dedicated page](https://mibew.org/plugins) on the official web site of the
|
|
|
|
project.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
### Update sources
|
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
When you've got the archive with an actual version of a plugin you should
|
|
|
|
extract files from it and upload them to the **Mibew Messenger**'s web server
|
|
|
|
replacing the old version of a plugin.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
It is highly recommended to backup old files before replacement.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
### Update database
|
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
After update of the plugin's files, the database should be updated too. To do
|
|
|
|
so you should navigate to `<mibew base URL>/operator/plugin` page and click on
|
|
|
|
'_update_' link in the plugin's row.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
It is highly recommended to backup the database before update.
|
2015-04-15 18:26:18 +03:00
|
|
|
|
2017-11-01 04:08:13 +03:00
|
|
|
If the plugin was updated successfully the value in '_state_' column will
|
|
|
|
change to '_working_'. If it did not, one should check the error log of the
|
|
|
|
web server for details of the problem.
|