Skip to main content


Friendica 2022.02 released


We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2022.02. This is the first release containing the work of the Arabic translation team – thanks a lot for your work! Other highlights of the release are
  • The video tab was removed from the profile, in exchange Friendica profiles now have a media tab, showing postings that contain more then just text.
  • An addon to allow usage of WebDAV for the storage back-end has been added.

For a detailed overview of the changes, please have a look at the CHANGELOG.

How to Update


Please note: With this release the minimal PHP version that Friendica requires is PHP 7.3 and later. Known issues with PHP 8 are collected in the issue tracker at github, though Friendica seems to work fine with PHP 8 now.

Deprecation Warning: Some old and unmaintained addons have been removed from the core addon repository. These addons are: blogger, buffer, jappixmini, notimeline, xmpp.

Updating from old Friendica versions


If you are updating from an older version than the 2021.09 release, please first update your Friendica instance to that version.

Pre-Update Procedures


Ensure that the last backup of your Friendica installation was done recently. We had no problems reported during the upgrade process from 2021.09 to the 2021.12 release candidate, so hopefully you will have a smooth transition.

Using Git


Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository, regardless of the branch (stable or develop) you are using. Remember to update the dependencies with composer as well. So, assuming that you are on the stable branch, the commands to update your installation to the 2022.02 release would be
cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull
If you want to use a different branch then the stable one, you need to checkout the branch before your perform the git pull.

Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

Using the Archive Files


We will provide the “full archive” shortly.

Post Update Tasks


The database update should be applied automatically, but sometimes it gets stuck. If you encounter this, please initiate the DB update manually from the command line by running the script
bin/console dbstructure update
from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned below.

Please note, that some of the changes to the database structure will take some time to be applied, depending on the size of your Friendica database.

Known Issues


None at the time of writing.

How to Contribute


If you want to contribute to the project, you don’t need to have coding experience. There are a number of tasks listed in the issue tracker with the label “Junior Jobs” we think are good for new contributors. But you are by no means limited to these – if you find a solution to a problem (even a new one) please make a pull request at github or let us know in the development forum.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation, the translation or advertisement materials is welcome or reporting a problem. You don’t need to deal with Git(Hub) or Transifex if you don’t like to. Just get in touch with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!
https://friendi.ca/2022/02/06/friendica-2022-02-released/
@Friendica News
Updating 1adbdfb8d..72c4ed95f
error: Your local changes to the following files would be overwritten by merge:#

whats going worng?
@Olaf auf Friendica you seem to have made some changes to tracked files. gid status will show you which files were changed, git diff will show you all the changes.
The archive files are now avail-able as well :)
@Paulo da Silva thanks for highlighting this! I've added a note to the release notes. Though granting all accounts on the system write access is a bad solution if you can avoid it.
@Paulo da Silva @Friendica News Thank you for letting us know. I just added another line to my chmod.sh script
I think I should include a chmod.sh script as well when creating the archive. Can you provide your script so I can double-check if I'm missing something?