Upgrade your wallabag installation
You will find here different ways to upgrade your wallabag:
But first, ensure you have
composer installed on your server (or at least the
composer.phar binary in the root directory of wallabag). If not, please install it.
Upgrading from 2.3.x to 2.3.y
If you got an error with
Not a git repository, it means you didn't install wallabag using git but rather using an archive. Follow steps for the shared hosting then.
Upgrading from 2.2.x to 2.3.x
Upgrade on a dedicated web server
If your current installation is < 2.2.x, please upgrade your instance to 2.2 before.
Upgrade on a shared hosting
- Backup your
Download the last release of wallabag:
wget https://wllbg.org/latest-v2-package && tar xvf latest-v2-package
You will find the md5 hash of the latest package on our website.
Extract the archive in your wallabag folder and replace
- Please check that your
app/config/parameters.ymlcontains all the required parameters. You can find here a documentation about parameters.
- If you use SQLite, you must also copy your
data/folder inside the new installation.
- You must run some SQL queries to upgrade your database. We assume that the table prefix is
wallabag_. Don't forget to backup your database before migrating.
- You may encounter issues with indexes names: if so, please change queries with the correct index name.
- You can find all the queries here.
Explanations about database migrations
During the update, we execute database migrations.
All the database migrations are stored in
app/DoctrineMigrations. You can execute each migration individually:
bin/console doctrine:migrations:execute 20161001072726 --env=prod.
You can also cancel each migration individually:
bin/console doctrine:migrations:execute 20161001072726 --down --env=prod.
Here is the migrations list for 2.2.x to 2.3.x release:
20170327194233: added the internal setting to share articles to Scuttle
20170407200919: removed useless
20170420134133: removed useless
site_credentialtable to store username / password for websites with authentication
20170510082609: changed length for username, username_canonical, email and email_canonical fields in
20170511211659: increased length of
20170602075214: added the internal setting to create user via the API
20170606155640: removed useless
20170719231144: changed tags to lowercase
reading_timefield to prevent null value
20171120163128: added the internal setting to enable the storage of article headers
20171125164500: added the internal setting to enable the usage of the origin URL in shaarli sharing
Upgrading from 2.x.y to 2.3.x
If your wallabag instance is < 2.2.0, there is no automatic script. You need to:
- export your data
- install wallabag 2.3.x (read the installation documentation)
- import data in this fresh installation (read the import documentation )
From wallabag 1.x
There is no automatic script to update from wallabag 1.x to wallabag 2.x. You need to: