Skip to content

Releases: friendica/friendica

Friendica 2022.06 released

7fe7d0c
Compare
Choose a tag to compare

We are very happy to announce the avail-ability of the new stable version of Friendica. With this release the "Siberian Iris" cycle is closed and we start a new one, the "Giant Rhubarb". 20 people have contributed directly to the code of Friendica "Giant Rhubarb" over the last year, committing over 2500 pull requests fixing nearly 200 numbered issues and adding new features.

Kudos to everyone who made this release possible by their contributions!

In addition to fixing bugs and improving the performance of Friendica, the highlights of the changes of the last year since the first release of the "Siberian Iris" are

  • The UI translations for Arabic and Dansk was added and Friendica supports now left-to-right languages generally better then before.
  • We have two new addons (S3 and WebDAV) to use additional storage back-ends for storing the media files.
  • The Mastodon compatible API was improved, you now should be able to use most Mastodon clients with your Friendica account.
  • The federation with Diaspora*, Mastodon, PeerTube, Pleroma and Lemmy was enhanced.
  • The themes (Frio and vier) got some touch ups, and the screen-reader support of Frio was improved.

For details, please the CHANGELOG file in the repository.

The lowest required PHP version Friendica needs on the server was raised to PHP 7.3 and PHP 8.0 is supported.

Breaking Change If you are running a custom addon, please note that the 2022.06 release does a breaking change removing the hooks settings_form and settings_post. Your addon should use the addon_settings hook instead.

What is Friendica

Friendica is a decentralised communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Twitter.

How to Update

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.

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.06 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 fetch and 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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2022.06.tar.gz (sha256) and friendica-addons 2022.06.tar.gz (sha256) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2022.06 archive), so you don’t have to worry about them.

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

Regarding the update process none as 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!

Friendica 2022.03 released

Compare
Choose a tag to compare

We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2022.03. This release is mainly a bug fixing release with breaking changes. Notably these are:

  • The closing of a bug in the recipient selector for private messages. The bug could result in direct messages being send to the wrong person from the contact list of the user.
  • The rework of how messages in private forums are delivered. Those are now as well distributed using the ActivityPub protocol. After a node is updated, communication in private forums is not longer possible with older versions of Friendica.
  • The StatusNet compatible API now uses the same ID as the Mastodon compatible API. Users of clients using the StatusNet compatible API (such as Friendiqa) need to remove the account from the client and re-register it.

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

How to Update

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.

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.03 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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2022.03.tar.gz (sha256) and friendica-addons 2022.03.tar.gz (sha256) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2022.03 archive), so you don’t have to worry about them.

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

Regarding the update process none as 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!

Friendica 2022.02 released

Compare
Choose a tag to compare

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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2022.02.tar.gz (sha256) and friendica-addons 2022.02.tar.gz (sha256) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2022.02 archive), so you don’t have to worry about them.

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

  • After the update please make sure that the directory vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer is write-able by your web server.

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!

Friendica 2021.09 released

2021.09
Compare
Choose a tag to compare

The summer sprint is over and we are happy to announce the availability of the new stable release of Friendica "Siberian Iris" 2021.09. It contains more then 160 pull requests from seven contributors and updates to several language packages from the translation teams.

For a detailed overview of the changes, please have a look at the CHANGELOG. The highlights of the release are

How to Update

Please note: With the release of 2021.09 Friendica does require at least PHP version 7.2 or above. Known issues with PHP 8 are collected in the issue tracker at github.

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 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.07 to the 2021.09 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 2021.09 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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive from friendica-full-2021.09.tar.gz (sha256) and friendica-addons 2021.09.tar.gz (sha256) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.09 archive), so you don’t have to worry about them.

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!

2021.07

Compare
Choose a tag to compare

We are very happy to announce the availability of the new stable release of Friendica "Siberian Iris" 2021.07. This release contains 219 pull requests from ten contributors and the work of the translation teams. While fixing some problems identified, we have added some nice features

  • support for right-to-left languages was added,
  • the API was expanded to have Mastodon compatible endpoints and
  • an addon was added to support SAML services like keycloak for login.

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

How to Update

Updating from old Friendica versions

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

In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be nessessary.

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.04 to the 2021.06 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

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.

cd friendica
git fetch
git checkout BRANCH
git fetch
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout BRANCH
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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2021.07.tar.gz and friendica-addons 2021.07.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.07 archive), so you don’t have to worry about them.

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

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

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!

Friendica 2021.04 Released

Compare
Choose a tag to compare

with a slight delay, we are happy to announce the availability of the new stable version of the Friendica communications server: Friendica Siberian Iris 2021.04.

This is mostly a bug fixing release, stabilizing the new features we introduced over the Red Hot Poker cycle, but also finishing some long time restructuring work on the database structure, which results in a greatly improved performance of Friendica. This release bundles 196 pull requests fixing 53 filed issues. For a detailed overview of the changes, please have a look at the CHANGELOG, some of the highlights

  • The reworking of how items are stored in the database was finished, which results in a great improvement of Friendicas performance. Please note that the needed upgrade might take hours depending of your database size.
  • Admins can now block tags from the trending tag widget.
  • We removed the Flash based addons from the addon repository.

And a heads up for developers, we moved some endpoints in the API to normalize the endpoints.

How to Update

Updating from old Friendica versions

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

In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be necessary.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently. Despite the long duration of the database upgrade we had no reports of unaddressed problems during the RC phase.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Important: We removed the master branch and are using the stable branch instead.

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.

cd friendica
git fetch
git checkout stable
git pull
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout stable
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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2021.04.tar.gz and friendica-addons 2021.04.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.01 archive), so you don’t have to worry about them.

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

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

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!

Friendica 2021.01 Released

Compare
Choose a tag to compare

and a happy new year dear reader. Not quiet in time for the holidays, but we are very happy to announce the availability of the latest stable version of the Friendica communications server which bundles up some 270 pull requests closing 86 numbered issues. For a detailed overview of the changes, please have a look at the CHANGELOG, some of the highlights

  • Thanks to Balázs Úr Friendica is now available in Hungarian. The German, Italian and Russian translation was updated as well.
  • hansw-nlo made us aware of some places where user input was not properly escaped. For security reasons we urge you to upgrade to the new release. See Issue 9538 for details.
  • The performance of the background process was further improved. For nodes running on very limited hardware, this might cause some problems. If you are running Friendica on such hardware please be aware that you might need to adjust settings like the worker_cooldown in your configuration file.
  • Friendica is now able to directly re-share a posting in addition to the manual cite and re-share we are used to. Additionally the native re-sharing mechanisms of the different protocols supported by Friendica got improved and re-shared postings are now displayed on the users profile page.

How to Update

Updating from old Friendica versions

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

In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be nessessary.

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 2020.09 to the 2020.12 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Important: We removed the master branch and are using the stable branch instead.

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.

cd friendica
git fetch
git checkout BRANCH
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout BRANCH

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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2021.01.tar.gz and friendica-addons 2021.01.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.01 archive), so you don’t have to worry about them.

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

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

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!

Friendica 2020.09-1 Hotfix release

Compare
Choose a tag to compare

During the RC phase of the 2020.09 release of Friendica a problem during sending out notification mails was not observed by the testers, but only reported after the release. Therefore we release now the 2020.09-1 hotfix release which will re-enable those mails.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 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 2020.07 to the 2020.09 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Important: We are removing the master branch and are using the stable branch instead.

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.

cd friendica
git fetch
git checkout BRANCH
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout BRANCH

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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2020.09-1.tar.gz and friendica-addons 2020.09-1.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2020.09 archive), so you don’t have to worry about them.

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

If you are using lighttpd to serve your Friendica node the boolean AND operator for the full text search seems not to be working at the moment.

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!

Friendica 2020.09 Released

Compare
Choose a tag to compare

We are happy to announce the availability of Friendica 2020.09, wrapping up the work over the summer. It bundles some exciting new features and enhancements with numerous fixes along the way.

This release is composed of 230 pull requests to the development branch, that closed 65 numbered tickets and enhanced several aspects of Friendica and the communication with other projects within the Fediverse. For a full reference, please have a look at the CHANGELOG file, some important things are worth highlighting here:

  • The speed of the full text search was enhanced significantly. If you had disabled it before, please check it out now and let us know if it works for you as we are considering to remove the option to disable it in a future release.
  • The themes got some updates. Among other things the way how a re-share is displayed. If you like the old display style better you'll find an option in the user settings to switch back.
  • Some time ago we did a user voting about which additional features should be handled in a unified way on all Friendica instances. The last of these items are now reworked. One of these is that all public calendar entries are now available as iCAL file from your profile.
  • Friendica is now supporting Activity Pub relay server. For more information please have a look at this forum thread

Additionally this release contains a fix for a problem that Roger Meyer discovered in the processing of Activity Pub messages. We encourage all Friendica admins to update their nodes to the 2020.09 release to prevent problems arising from this. Thanks to Roger to report the issue!

If you are using PHP version 7.0 there is currently a problem with one of the dependencies of Friendica. Please see this forum thread for more information.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 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 2020.07 to the 2020.09 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Important: We are removing the master branch and are using the stable branch instead.

Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to update the dependencies with composer as well.

cd friendica
git fetch
git checkout BRANCH
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout BRANCH

Where BRANCH is either the new stable branch or the develop branch, depending which version of Friendica you want to use. The old master branch will not receive any updates and will be removed soon.

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

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2020.09.tar.gz and friendica-addons 2020.09.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2020.09 archive), so you don’t have to worry about them.

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

If you are using lighttpd to serve your Friendica node the boolean AND operator for the full text search seems not to be working at the moment.

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!

Hotfix Release of Friendica 2020.07-1

Compare
Choose a tag to compare

Thanks to Roger Meyer who reported a flaw in the administration module of Friendica, we could fix a security vulnerability that could leak sensitive information from the server environment. The hotfix release 2020.07-1 includes the patch for the stable release branch of Friendica. The development and RC branches have been updated as well.

Affected versions of Friendica

All versions of Friendica since April 2019 (develop branch) and June 2019 (stable) are affected.

Through the admin module environment variables of the server system can be read by anyone on the internet. Among other things this may include database passwords for Docker installs and the memcached SASL password. Therefore we recommend all node admins to change their potentially affected passwords after the upgrade to 2020.07-1. Furthermore this fix also prevents anonymous users to update node-wide addon settings.

How to Upgrade.

This information only applies to the stable release 2020.07 of Friendica. The patch has separately been added to the develop and 2020.09-rc branch of the repository.

Using Git

Important: We are removing the master branch and are using the stable branch instead.

Updating from the git repositories of Friendica will be a bit more complicated as you might be used to as we decided to rename the branch for the stable releases to stable. Hence you need to switch the branch you want to use, after pulling the current version of the code from the repositories. As usual, please remember to update the dependencies with composer as well.

cd friendica
git fetch
git checkout stable
git pull

Pulling in the dependencies with composer is not necessary for this hotfix release.

Using the Archive Files

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2020.07-1) file and unpack it on your local computer. Compared to the 2020.07 release only a few files were updated and none of the config files are affected. So you can just upload the changed files onto your server.

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 again Roger Meyer to make us aware of this problem!