Wallabag on Cloudron overlooked for 2 updates
Wallabag 12 months out-of-date (#11) · Issues · cloudron / wallabag-app · GitLab
Although upstream releases have greatly slowed, I think we will benefit from the bug fixes in 2.3.7 and 2.3.8
2.4.0 is on its way, but please don't wait for that
For some reason we are actually using a specific commit for the app https://git.cloudron.io/cloudron/wallabag-app/-/blob/master/Dockerfile#L11
I cannot remember what that comment really means about the "right before 2fa".
Wallabag 2.4.0 is out: https://github.com/wallabag/wallabag/releases/tag/2.4.0
The long awaited 2.4.0 is finally here
There's a ton of new features (you can check the full changelog if you want to see them all). We'll only highlight main ones here.
- Allow to rename tags from the web interface #3574,
- Possibility to change locale from login/register pages #3216,
- Ability to import/export tagging rules #4028,
- Enable OTP 2FA via third-party apps (Google Authenticator, Authy or FreeOTP) #3798,
- Add random feature #3526,
- Ability to revoke feed token #3994,
- Move Ignore Origin rules to database #4026,
- Ability to manually define the reading speed #4053,
- MathJax support #4128,
- Allow custom styles system wide #4151,
- Support elCurator import #4175,
- Add mass actions for Material design in list view #4326,
- Add Dark theme to Material #4725
As a side note, the baggy theme is now deprecated and will be removed in 2.5.0.
Support for PHP 7.4
The 2.3.8 lacked support for PHP 7.4 but, hey, that wallabag 2.3.8 was released in May 2019 and PHP 7.4 first alpha goes out in June 2019.
Maybe we should have release 2.3.9 with PHP 7.4 support but there was too much stuff in the master and lack of motivation to only keep commits which enabled support.
I hope we'll be more reactive for PHP 8.0
Dropped support for PHP < 7.2
PRs #3758 #4441
We removed support for PHP < 7.2 because lower version aren't supported by PHP itself.
First we remove support for PHP < 7.1 back in Novembre 2018 #3758 and then support for PHP < 7.2 in June 2020.
Some people will arg that we should keep the lowest version possible because some folks are maintaining outdated version of PHP but we need to move on.
Also, security support for PHP 7.2 will end in November 2020 but we think it's too fast for most people. Also Symfony still required PHP >=7.2.5 for the current master (the upcoming 5.2.0).
Translations in Weblate
PRs #4447 #4359 #4442
The whole application is now connected to the Weblate platform which allow anyone to contribute to the translation without having to use Git at all.
There are multiple sources in Weblate for the wallabag project because the iOS & Android app are also using it.
The application is now fully translated in 10 languages!
️ Feel free to improve translations.
Hashed URLs for faster check
People using the API to save contents often have to check if the URL already exists in the database. Using the plain URL to check wasn't fast enough and it can lead to privacy leak (see #4361 (comment)).
That's why there is now a hash of the URL for each entry. Don't forget to run the command php bin/console --env=prod wallabag:generate-hashed-urls after upgrading to 2.4.0.
URLs are hashed using sha1.
Add basic search endpoint
The API now expose a basic search endpoint. We declare it as basic because it's a simple search in the database (like the one in the web interface). No robust search engine were involved in that change.
How to upgrade
- perform a backup of the database (just in case)
make updatefrom your wallabag directoy
php bin/console --env=prod wallabag:generate-hashed-urlswhich will generates a hash of URL for all saved entries (improve API search+++)
You might be interested in this information too:
- you can safely remove database_driver_class from the app/config/parameters.yml file
- install imagick PHP extension if you want GIF animation to be kept when saving images locally
- you can now use Sentry to log errors from wallabag, just define sentry_dsn in app/config/parameters.yml
Apps, once released, even though revoked later, can always get installed if you know the version. In this case you have to craft a dashboard url like:
Given the migration issues, I am not sure though if we should just release the new version with a new app id or wait for upstream fixes.