♲ Friendica News (email@example.com) 2019-12-23 19:30:28:
Friendica 2019.12 released
Wrapping up for the end-of-the-year? We too; and therefore we are happy to announce the release of Friendica “Dalmatian Bellflower” 2019.12.
This release bundles up some bug fixes, but mostly enhancements to existing features and adds some new ones as well. For a full list of changes, please have a look at the CHANGELOG file in the repository. For a short summery, the highlights are:
The titles of all the pull requests of the 2019.12 release summarized as word cloud.
- The ACL dialogue introduced in the 2019.09 release on the new compose page for the frio theme was now adopted to all themes.
- The handling of reshares was made more native for the federated platforms and federation with Diaspora*, Mastodon, Pixelfed and Peertube was improved.
- The API was improved and got some new endpoints to improve the experience of using Friendica with mobile apps like Fedilab.
- Postings can now be pinned to your profile wall and
- if you like, you can connect to Discourse forums via email.
Thanks to all the people who have made this release possible!
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2018.09 release, please first update your Friendica instance to that version as there were several important changes in that version.
Please note, that we moved the shipped
.htaccess-distin the 2019.01 version. Make sure that you have saved a copy of the file if you made any changes to it, so that you can copy the file from the backup after the upgrade.
Please further note, that since Friendica 3.6 we use Composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Furthermore, we raised the minimal requirements with the 2019.06 version to PHP 7. Before updating please ensure that you are using a supported PHP version on your server. We suggest PHP 7.2 or later.
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better safe than sorry.
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.
If you want to switch the branch (e.g. if you helped to test the release candidate) please do so after the pull using
git checkout master(or
Be aware that the
.htaccessfile was removed from the git repository in the 2019.01 version. You might have to restore yours from a backup (if you have done local changes) or from the
.htaccess-distif you had not done it before.
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-2019.12.tar.gz and friendica-addons-2019.12.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 (
.htaccessfiles. 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-2019.12archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format in the 2019.03 version. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Post Update Tasks
The database update should be applied automatically, but maybe 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.
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!