Search
Items tagged with: release
Friendica 2022.12 released
Content warning: We are very happy to announce the avail-ability of the new stable version of Friendica. Wrapping up the sprint from the 2022.10 release of Friendica we closed 73 filed issues and had almost 300 pull requests by 19 contributors. A special thanks goes out t
We are very happy to announce the avail-ability of the new stable version of Friendica. Wrapping up the sprint from the 2022.10 release of Friendica we closed 73 filed issues and had almost 300 pull requests by 19 contributors.
A special thanks goes out to Christian Pöschl from usd AG and Matthias Moritz who have found a CSRF- and XSS-attack, that is fixed with this release.
In addition to fixing this bug, the highlights of the changes since the 2022.10 release are
For details, please the CHANGELOG file in the repository.
Since version 2022.06 the lowest required PHP version Friendica needed on the server was raised to PHP 7.3 and PHP 8.0 is supported.
Friendica is a decentralized 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.
If you are updating from an older version than the 2022.06 release, please first update your Friendica instance to that version as it contained some breaking changes.
Ensure that the last backup of your Friendica installation was done recently.
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
cd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch than the
Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.
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.12.tar.gz (sha256) and friendica-addons 2022.12.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
The files of the dependencies are included in the archive (make sure you are using the friendica-full-2022.12 archive), so you don’t have to worry about them.
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.
Regarding the update process none as of writing.
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!
A special thanks goes out to Christian Pöschl from usd AG and Matthias Moritz who have found a CSRF- and XSS-attack, that is fixed with this release.
In addition to fixing this bug, the highlights of the changes since the 2022.10 release are
- The default theme of Friendica (frio) got many improvements and some old themes got deprecated.
- The calendar saw some improvements and can now be made visible to anonymous visitors.
- The homepage mentioned on the user profile is now automatically verified via the rel-me backlink.
- Images attached to a posting are now shown in a grid at the bottom of the posting.
- A moderation corner was established from the admin panel where a future release will add more moderation tool and bundle them with the current once.
.htaccess.For details, please the CHANGELOG file in the repository.
Since version 2022.06 the lowest required PHP version Friendica needed on the server was raised to PHP 7.3 and PHP 8.0 is supported.
What is Friendica
Friendica is a decentralized 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 2022.06 release, please first update your Friendica instance to that version as it contained some breaking changes.
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.12 release would becd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch than 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.12.tar.gz (sha256) and friendica-addons 2022.12.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.12 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.06 released
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!Gunnera manicata, photographed near the church at St Just in Roseland in Cornwall. Photo by Tom Oates, License CC-BY 3.0
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” areFor details, please the CHANGELOG file in the repository.
- 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.
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 hookssettings_formandsettings_post. Your addon should use theaddon_settingshook 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 thestablebranch, the commands to update your installation to the 2022.06 release would be
cd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch then thestableone, 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 (sayfriendica_new) and copy over your existing configuration (config/local.config.phpandconfig/addon.config.php) and.htaccessfiles. Afterwards rename your current Friendica directory (e.g. friendica) tofriendica_oldandfriendica_newtofriendica.
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.06 released
Content warning: 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
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!
Gunnera manicata, photographed near the church at St Just in Roseland in Cornwall. Photo by Tom Oates, License CC-BY 3.0
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 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
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.
If you are updating from an older version than the 2021.09 release, please first update your Friendica instance to that version.
Ensure that the last backup of your Friendica installation was done recently.
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
cd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch then the
Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.
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
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.
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.
Regarding the update process none as of writing.
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!
Kudos to everyone who made this release possible by their contributions!
Gunnera manicata, photographed near the church at St Just in Roseland in Cornwall. Photo by Tom Oates, License CC-BY 3.0In 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.
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 becd friendicagit pullbin/composer.phar install --no-devcd addongit 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 2021.09 released
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
- scheduled postings (scheduling is done in the permissions of a posting),
- the notification system got an overhaul, and
- admins can now browse the logs more comfortable in the admin panel.
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 thestablebranch, the commands to update your installation to the 2021.09 release would be
cd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch then thestableone, 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 (sayfriendica_new) and copy over your existing configuration (config/local.config.phpandconfig/addon.config.php) and.htaccessfiles. Afterwards rename your current Friendica directory (e.g. friendica) tofriendica_oldandfriendica_newtofriendica.
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
Update Mon Sept 27th: If you are using MySQL (not MariaDB) the automatic DB structure updates may fail see issue 10768.
Update Mon Oct 4th / 7th: Solved for the full archive downloadable from files.friendi.ca. A node-specificconfig/local.config.phpfile has been inadvertently included in the full archive. Please make sure you either remove it or overwrite it with your own when you perform the update as described above.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
Content warning: 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 trans
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
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.
If you are updating from an older version than the 2020.03 release, please first update your Friendica instance to that version.
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.
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
cd friendicagit pullbin/composer.phar install --no-devcd addongit pull
If you want to use a different branch then the
Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.
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
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.
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.
Update Mon Sept 27th: If you are using MySQL (not MariaDB) the automatic DB structure updates may fail see issue 10768.
Update Mon Oct 4th / 7th: Solved for the full archive downloadable from files.friendi.ca. A node-specific
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!
For a detailed overview of the changes, please have a look at the CHANGELOG. The highlights of the release are
- scheduled postings (scheduling is done in the permissions of a posting),
- the notification system got an overhaul, and
- admins can now browse the logs more comfortable in the admin panel.
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 becd friendicagit pullbin/composer.phar install --no-devcd addongit 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
Update Mon Sept 27th: If you are using MySQL (not MariaDB) the automatic DB structure updates may fail see issue 10768.
Update Mon Oct 4th / 7th: Solved for the full archive downloadable from files.friendi.ca. A node-specific
config/local.config.php file has been inadvertently included in the full archive. Please make sure you either remove it or overwrite it with your own when you perform the update as described above.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 “Red Hot Poker” 2020.03 released
We are happy to announce the avail-ability of Friendica “Red Hot Poker” 2020.03!
Thanks to all the helpers during the RC phase to polish some corners of the release. Almost 400 tickets went into this release according to the milestone, closing something around 90 numbered issues and some unnumbered as well. But along all these fixes we also introduced some new features and revamped some aspects of your daily life with Friendica. For a complete list of changes, please have a look into the CHANGELOG, here are some of the highlights:Thanks to all the people who have made this release possible!
- We adopted the “audio” type for ActivityPub postings and are now federating with Funkwhale.
- The multiple profile feature was removed and replaced by free form profile fields that you can present different audiences (unverified visitors of your profile and selected Friendica contact/-groups). The old (additional) profiles are converted automatically for the new format.
- The hide-wall profile option was replaced by a hopefully more clear option to have your public postings unlisted on the community page of your node.
- The creation of delegated accounts was made more easy.
- The accessibility of the web-interface was improved.
- Admins can now manage the users of their node from the command line.
- An addon to use Markdown instead of BBCode while composing new postings and comments was added.
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.htaccessfile to.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.Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we had some reports about problems with the profile field migration. All of these should be fixed, but better safe than sorry.
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.
If you are using PHP version 7.0 please be aware of an issue with one of the dependencies of Friendica. You should read this forum thread before updating as you need to manually adjust the code or update your PHP version.Using Git
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 friendicagit pullbin/composer.phar installcd addongit pull
If you want to switch the branch (e.g. if you helped to test the release candidate) please do so after the pull usinggit checkout master(ordevelop).
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-2020.03.tar.gz and friendica-addons-2020.03.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.phpandconfig/addon.config.php) and.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 thefriendica-full-2020.03archive), 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.
Please note, that some of the changes to the database structure will take some time (hours)) to be applied, depending on the size of your Friendica database.Known Issues
After the release it was reported, that one of the dependencies of Friendica currently has problems with PHP 7.0. If you are using PHP version 7.0 please be aware of this issue. You should read this forum thread before updating as you need to manually adjust the code or update your PHP version.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!2020.03 Milestone · friendica/friendica
Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.GitHub
Friendica “Red Hot Poker” 2020.03 released
Content warning: We are happy to announce the avail-ability of Friendica "Red Hot Poker" 2020.03! Thanks to all the helpers during the RC phase to polish some corners of the release. Almost 400 tickets went into this release according to the milestone, closing something a
We are happy to announce the avail-ability of Friendica “Red Hot Poker” 2020.03!
Thanks to all the helpers during the RC phase to polish some corners of the release. Almost 400 tickets went into this release according to the milestone, closing something around 90 numbered issues and some unnumbered as well. But along all these fixes we also introduced some new features and revamped some aspects of your daily life with Friendica. For a complete list of changes, please have a look into the CHANGELOG, here are some of the highlights:
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
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 had some reports about problems with the profile field migration. All of these should be fixed, but better safe than sorry.
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.
If you are using PHP version 7.0 please be aware of an issue with one of the dependencies of Friendica. You should read this forum thread before updating as you need to manually adjust the code or update your PHP version.
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 friendicagit pullbin/composer.phar installcd addongit pull
If you want to switch the branch (e.g. if you helped to test the release candidate) please do so after the pull using
Be aware that the
If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2020.03.tar.gz and friendica-addons-2020.03.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 (
The files of the dependencies are included in the archive (make sure you are using the
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.
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.
Please note, that some of the changes to the database structure will take some time (hours)) to be applied, depending on the size of your Friendica database.
After the release it was reported, that one of the dependencies of Friendica currently has problems with PHP 7.0. If you are using PHP version 7.0 please be aware of this issue. You should read this forum thread before updating as you need to manually adjust the code or update your PHP version.
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!
Thanks to all the helpers during the RC phase to polish some corners of the release. Almost 400 tickets went into this release according to the milestone, closing something around 90 numbered issues and some unnumbered as well. But along all these fixes we also introduced some new features and revamped some aspects of your daily life with Friendica. For a complete list of changes, please have a look into the CHANGELOG, here are some of the highlights:
- We adopted the “audio” type for ActivityPub postings and are now federating with Funkwhale.
- The multiple profile feature was removed and replaced by free form profile fields that you can present different audiences (unverified visitors of your profile and selected Friendica contact/-groups). The old (additional) profiles are converted automatically for the new format.
- The hide-wall profile option was replaced by a hopefully more clear option to have your public postings unlisted on the community page of your node.
- The creation of delegated accounts was made more easy.
- The accessibility of the web-interface was improved.
- Admins can now manage the users of their node from the command line.
- An addon to use Markdown instead of BBCode while composing new postings and comments was added.
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 file to .htaccess-dist in 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.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we had some reports about problems with the profile field migration. All of these should be fixed, but better safe than sorry.
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.
If you are using PHP version 7.0 please be aware of an issue with one of the dependencies of Friendica. You should read this forum thread before updating as you need to manually adjust the code or update your PHP version.
Using Git
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 friendicagit pullbin/composer.phar installcd addongit pull
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 develop).Be aware that the
.htaccess file 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-dist if 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-2020.03.tar.gz and friendica-addons-2020.03.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.03 archive), 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.
Please note, that some of the changes to the database structure will take some time (hours)) to be applied, depending on the size of your Friendica database.
Known Issues
After the release it was reported, that one of the dependencies of Friendica currently has problems with PHP 7.0. If you are using PHP version 7.0 please be aware of this issue. You should read this forum thread before updating as you need to manually adjust the code or update your PHP version.
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 2018.09 released
Dear everybody in the Federation, the Fediverse and anywhere else, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.09.
This release brings the long awaited restructuring of the item table in the database, alongside some 100 closed issues from the tracker. Please see the CHANGELOG file for the complete overview of the changes. Here just a short list of the noteworthy changes since the 2018.05 release of Friendica.Thanks everyone who has made this release possible. Your work is much appreciated!
- The long awaited restructuring of the item table of the database will finally be included in this release. The needed changes and alterations of the database structure and content will take some time. Depending on the resources available on your system this can take hours or even days. The maintenance mode will inform you about the progress.
- The configuration structure is changed. Your old `.htconfig.php` file will still work, but you will get a notification in the admin panel with some hopefully explaining text on how to convert your settings to the config file. In some cases the encoding of the displayed text got mangled up, if you are suffering from such garbage you need to switch to the new config style and set the correct encoding for the database.
- The `.htaccess` file is no part of the git repository anymore. Instead we now ship the `.htaccess-dist` file that you have to copy to the `.htaccess` location. This has the advantage that you can now customise the `.htaccess` file to meet your requirements. Please make a copy of your old `.htaccess` file should you have made any changes and restore the file after the update from the backup or the distributed file. Without a working `.htaccess` file your node will probably not work!
- We removed the old syntax highlighting mechanism from `[code]` blocks due to problems federating the highlighted syntax to other platforms. There will be an addon for this in the next release.
- The libravatar service will be continued, so contrary to the note with the last release, you can keep using the libravatar addon to automatically generate avatar pictures for your users.
How to Update
Updating from old Friendica versions
If you are updating from a version older then Friendica 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.
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.Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems (except those listed below), but better save than sorry.
This is especially true during this update for your `.htaccess` file which we removed from the repository so you can make local adjustments to the files without further conflicts. Please make a copy of the file before you start the update and restore it afterwards. If you have not made any changes to the file, you can use the new `.htaccess-dist` file and copy that to the `.htaccess` file.Using the Archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-2018.09.tar.gz and friendica-addons-2018.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 `.htconfig.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-2018.09 archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.Using git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica git pull bin/composer.phar install cd addon git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull using `git checkout`.
Be aware that the `.htaccess` file was removed from the git repository. You have to restore yours from a backup (if you have done local changes) or from the `.htaccess-dist` file (copy the file to `.htaccess` if you had not done any changes to the old `.htaccess` file).Post-Update Procedures
Restore your .htaccess file from the backup or the .htaccess-dist file.
The conversion process of the items stored in the database can take a long time. Reports indicate some hours to days or even weeks depending on the number of stored items and the available resources on the server.
If you can start the process directly from the command line interface, this will speed up the process significantly. To do so run the following command (use screen or a similar tool so you can detach from the session while the process is running):
bin/console postupdate
from the base of your Friendica installation.
The conversation of the stored items to the new structure of the database will cause some load on the server. It will not interfere with the daily usage of your Friendica node. Once it is finished the needed storage for the database should be lowered significantly, especially on large nodes.Known Problems
Should the DB update process get 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.Problem with InnoDB on MySQL 5.7
One user reported problems during the update of the database using MySQL 5.7 getting the error message `Creating index ‘PRIMARY’ required more than ‘innodb_online_alter_log_max_size’ bytes of modification log. Please try again.` from MySQL. If you encounter this problem, please try the following:
- increase the config value mentioned in the error message above,
- execute this command in your mysql console: `update config set v=1278 where k=”post_update_version”;`
- after this execute the command `bin/console postupdate`.
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 everyone who helped making this release possible and have fun!f.belug.de/profile/cat-alina
!Friendica Support Since yesterday I have several unicode encoding issues on develop branch. Can anybody confirm this?forum.friendi.ca
2020.03 Milestone · friendica/friendica
Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.GitHub
Friendica 2018.09 released
Content warning: Dear everybody in the Federation, the Fediverse and anywhere else, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.09. This release brings the long awaited restructuring of the item table in the database, alon
Dear everybody in the Federation, the Fediverse and anywhere else, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.09.
This release brings the long awaited restructuring of the item table in the database, alongside some 100 closed issues from the tracker. Please see the CHANGELOG file for the complete overview of the changes. Here just a short list of the noteworthy changes since the 2018.05 release of Friendica.
If you are updating from a version older then Friendica 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.
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.
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems (except those listed below), but better save than sorry.
This is especially true during this update for your `.htaccess` file which we removed from the repository so you can make local adjustments to the files without further conflicts. Please make a copy of the file before you start the update and restore it afterwards. If you have not made any changes to the file, you can use the new `.htaccess-dist` file and copy that to the `.htaccess` file.
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-2018.09.tar.gz and friendica-addons-2018.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 `.htconfig.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-2018.09 archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica git pull bin/composer.phar install cd addon git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull using `git checkout`.
Be aware that the `.htaccess` file was removed from the git repository. You have to restore yours from a backup (if you have done local changes) or from the `.htaccess-dist` file (copy the file to `.htaccess` if you had not done any changes to the old `.htaccess` file).
Restore your .htaccess file from the backup or the .htaccess-dist file.
The conversion process of the items stored in the database can take a long time. Reports indicate some hours to days or even weeks depending on the number of stored items and the available resources on the server.
If you can start the process directly from the command line interface, this will speed up the process significantly. To do so run the following command (use screen or a similar tool so you can detach from the session while the process is running):
bin/console postupdate
from the base of your Friendica installation.
The conversation of the stored items to the new structure of the database will cause some load on the server. It will not interfere with the daily usage of your Friendica node. Once it is finished the needed storage for the database should be lowered significantly, especially on large nodes.
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.
One user reported problems during the update of the database using MySQL 5.7 getting the error message `Creating index ‘PRIMARY’ required more than ‘innodb_online_alter_log_max_size’ bytes of modification log. Please try again.` from MySQL. If you encounter this problem, please try the following:
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 everyone who helped making this release possible and have fun!
This release brings the long awaited restructuring of the item table in the database, alongside some 100 closed issues from the tracker. Please see the CHANGELOG file for the complete overview of the changes. Here just a short list of the noteworthy changes since the 2018.05 release of Friendica.
- The long awaited restructuring of the item table of the database will finally be included in this release. The needed changes and alterations of the database structure and content will take some time. Depending on the resources available on your system this can take hours or even days. The maintenance mode will inform you about the progress.
- The configuration structure is changed. Your old `.htconfig.php` file will still work, but you will get a notification in the admin panel with some hopefully explaining text on how to convert your settings to the config file. In some cases the encoding of the displayed text got mangled up, if you are suffering from such garbage you need to switch to the new config style and set the correct encoding for the database.
- The `.htaccess` file is no part of the git repository anymore. Instead we now ship the `.htaccess-dist` file that you have to copy to the `.htaccess` location. This has the advantage that you can now customise the `.htaccess` file to meet your requirements. Please make a copy of your old `.htaccess` file should you have made any changes and restore the file after the update from the backup or the distributed file. Without a working `.htaccess` file your node will probably not work!
- We removed the old syntax highlighting mechanism from `[code]` blocks due to problems federating the highlighted syntax to other platforms. There will be an addon for this in the next release.
- The libravatar service will be continued, so contrary to the note with the last release, you can keep using the libravatar addon to automatically generate avatar pictures for your users.
How to Update
Updating from old Friendica versions
If you are updating from a version older then Friendica 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.
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.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems (except those listed below), but better save than sorry.
This is especially true during this update for your `.htaccess` file which we removed from the repository so you can make local adjustments to the files without further conflicts. Please make a copy of the file before you start the update and restore it afterwards. If you have not made any changes to the file, you can use the new `.htaccess-dist` file and copy that to the `.htaccess` file.
Using the Archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-2018.09.tar.gz and friendica-addons-2018.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 `.htconfig.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-2018.09 archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Using git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica git pull bin/composer.phar install cd addon git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull using `git checkout`.
Be aware that the `.htaccess` file was removed from the git repository. You have to restore yours from a backup (if you have done local changes) or from the `.htaccess-dist` file (copy the file to `.htaccess` if you had not done any changes to the old `.htaccess` file).
Post-Update Procedures
Restore your .htaccess file from the backup or the .htaccess-dist file.
The conversion process of the items stored in the database can take a long time. Reports indicate some hours to days or even weeks depending on the number of stored items and the available resources on the server.
If you can start the process directly from the command line interface, this will speed up the process significantly. To do so run the following command (use screen or a similar tool so you can detach from the session while the process is running):
bin/console postupdate
from the base of your Friendica installation.
The conversation of the stored items to the new structure of the database will cause some load on the server. It will not interfere with the daily usage of your Friendica node. Once it is finished the needed storage for the database should be lowered significantly, especially on large nodes.
Known Problems
Should the DB update process get 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.
Problem with InnoDB on MySQL 5.7
One user reported problems during the update of the database using MySQL 5.7 getting the error message `Creating index ‘PRIMARY’ required more than ‘innodb_online_alter_log_max_size’ bytes of modification log. Please try again.` from MySQL. If you encounter this problem, please try the following:
- increase the config value mentioned in the error message above,
- execute this command in your mysql console: `update config set v=1278 where k=”post_update_version”;`
- after this execute the command `bin/console postupdate`.
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 everyone who helped making this release possible and have fun!
Friendica 2018.05 released
Dear Federation, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.05.
Back on track with scheduled releases, after 3.6 took such a long time. In this release we have packed some bug fixes and enhancements. After an incompatibility glitch with the last release, Friendica 2018.05 is now again compatible with PHP 5.6. However we recommend using a more recent PHP version to further enhance the performance gain from the ongoing overhaul of the Friendica code and processes. Obviously GDPR was one thing we concentrated on for this release. Identifying problems in existing features (e.g. account and node mobility), adding new features (see below) and making things more transparent. To make a long story short, here a list of the noteworthy changes since the last release:For a list of further changes, please have a look at the CHANGELOG file.
- Finnish translation was added to the repository from Transifex. With it, Friendica now has 20 localizations from which 11 have more then 80% of the core plattform translated (DE, EN, EN-GB, EN-US, ES, FI, FR, IT, PL, RU, ZH-CN).
- New module for Terms of Services for your node that can be activated from the admin panel. If the module is activated links from the general information page and the user registration will be added. Additionally a basic privacy statement can be shown in both, the TOS page and the registration page.
- Many utility scripts are now bundled in a console that can be found in the bin directory. Please see bin/console –help for all available commands.
- When entering a new password, the choosen one will be checked locally against a database of exposed passwords.
- As libravatar is closing their service we have added a new alternative to the gravatar service based on David Revoy’s cat-avatar-generator: the catavatar.
- The long deprecated themes frost( and frost-mobile have been removed from the Friendica repository. If you need them, you can find them in the deprecated-themes repository.
wordcloud from the commit messages
Thanks to everyone who made this release possible, by writing code, translating the user interface and reporting issues!How to update?
Pre-Update procedures
Ensure that the last backup of your Friendica database was done recently. While testing, we did not encounter problems, but better save than sorry.From the archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-2018.05.tar.gz and friendica-addons-2018.05.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 .htconfig.php file. 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-2018.05 archive), so you don’t have to worry about them.From git
Regardless of the branch you are on (master, develop or 2018.05-rc) all you have to do to get the new code is to run
git pull
on your server in the base and the addon directory. Remember to update the dependencies via composer as well.
If you helped testing the release candidate, you should also switch to either the master or the develop branch. Thanks for testing!
If you are updating from an older version then the 3.6 release, please be aware that Friendica is now using composer to manage the dependencies. After you pulled the latest code, you have to check the dependencies for updates as well. To do so run
bin/composer.phar install
from the base directory of your Friendica installation. To be able to extract the downloaded archives, you need to have the php-zip module installed on your server. If you don’t want to remember this every time you pull, you can also use a so called git-hook to do it automatically. Please have a look at the docs for further information about this.
If you are updating from a version older then 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.Post-Update procedures
If you are updating from the 3.6 release (or older versions) of Friendica please remember to change the path to the worker in the cron job to adopt the changed location.
It should now be something along these lines:
/usr/bin/php bin/worker.php
Among other things the worker will detect changes to the database structure. The changes will be applied automatically and may, depending on the size of your table (especially the item table) and the available resources on the server, take some time. On larger systems this can be hours.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!Check for exposed password during password change · Issue #4604 · friendica/friendica
Today I stumbled on https://github.com/DivineOmega/password_exposed, a library that exposes a handy function to check if a given password has been part of the leaks recorded by https://haveibeenpwn...GitHub
f.belug.de/profile/cat-alina
!Friendica Support Since yesterday I have several unicode encoding issues on develop branch. Can anybody confirm this?forum.friendi.ca
Friendica 3.6 released
Content warning: The year started with sad news that Tony Baldwin passed away January 6th. Tony was an early member of the Friendica/RedMatrix/Hubzilla community who contributed ideas, addons, themes and utility tools. He was a great spirit among the FLOSS people, an arti
The year started with sad news that Tony Baldwin passed away January 6th. Tony was an early member of the Friendica/RedMatrix/Hubzilla community who contributed ideas, addons, themes and utility tools. He was a great spirit among the FLOSS people, an artist, a translator, an interpreter and a great friend who is deeply missed.
This release is dedicated to the memory of Tony “tazman” Baldwin.
Screenshot of the Diabook theme by Tony “tazman” Baldwin CC BY-SA 3.0 Source en.wikipedia.org
With no further ado, we’d like to present to you Friendica 3.6 The Tazmans Flax-lily.
It took a long while this time for the developers find the opportunity to say now is the right time. Initially we wanted to have the release after last years hackathon, but then the big adventure of reorganising the code was started and that took some time. But the long wait was worth it, the code got cleaner and faster.
Some things we want to highlight are:
https://peertube.tifox.fr/videos/embed/f5058788-6614-433d-a513-00a1bc3cf877
You can find the video on peertube and Vimeo.
We started to use composer for dependency management. This means, that if you are using git to manage the Friendica sources on your server, there is now an additional step in the update process. If you used the archives provided, you don’t need to care about it, as the archives contain the dependencies as well.
Should you encounter any problems while testing the RC code, please let us know about in the Friendica support forum, at github or over any other of the support channels.
Independent of the update path you are choosing, please be aware that there are some changes to the database structure to enhance the performance of Friendica that will be applied automatically to your database. Depending on the size of your database, especially the item table, these changes can take several hours.
If you are updating from a very old version of Friendica, you have to first update to version 3.5.4 before you can update to the 3.6 release.
Please note that due a slight oversight we did not encounter during testing in the RC phase you currently need php7 with the version 3.6. We are working on a 3.6.1 release that will then work again with php5.6. 3.6.1 should be available soon.
As mentioned above, Friendica is now using composer for dependency management. This means that you have to do one further step when updating your git repository. This can be either an additional command every time you update, or adding a shell script to a git hook.
Composer needs to be able to unpack the downloaded archives, hence you need to have the PHP zip module available on your server.
If you want to do it all manually, then use the following sequence of commands: starting in the base directory of your Friendica installation.
git pullphp util/composer.phar installcd addongit pull
This will download the updated sources from github, call composer to get the dependencies and then change into the addon repository to fetch the new code there as well.
If you don’t want to remember this every time you pull, you can also use a so called git-hook to do it automatically. Please have a look at the docs for further information about this.
As the changes regarding the dependency management are likely already in place on your system, a git pull in your Friendica core repository and the addon repository should bring you on the latest code as usual.
If you helped testing the release candidate–thanks a lot for helping!–you need to decide either to checkout the master or develop branch after the pull.
If you are using the develop branch, please be reminded about the recent path changes for many scripts.
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-3.6.zip or tar.gz and friendica-addons-3.6.zip or 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
The files of the dependencies are included in the archive (make sure that you use the friendica-full-3.6 archives), so you don’t have to worry about them.
After you performed the update, you need to touch your cron job for the background process. The script handling the worker has been moved to scripts directory. So your cron job must now contain: something like
/usr/bin/php scripts/worker.php
instead of the old location in the include directory.
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!
landing page for visitors using the frio theme
This release is dedicated to the memory of Tony “tazman” Baldwin.
Screenshot of the Diabook theme by Tony “tazman” Baldwin CC BY-SA 3.0 Source en.wikipedia.org
With no further ado, we’d like to present to you Friendica 3.6 The Tazmans Flax-lily.
Noteworthy Changes
It took a long while this time for the developers find the opportunity to say now is the right time. Initially we wanted to have the release after last years hackathon, but then the big adventure of reorganising the code was started and that took some time. But the long wait was worth it, the code got cleaner and faster.
Some things we want to highlight are:
- You can now interact with postings on the community page, even if you are not connected with the author.
- Forums can now be addressed with an !, e.g. !helpers. The ACL dialog does this automatically when you select a forum as recipient and has the forums listed separately from user groups and regular contacts. Addressing a forum with an ! will make the posting exclusively for the subscribers to the forum (public or private depends on the forum settings).
- You can now follow hashtags
- Dependency management is now done using composer (see below).
- The API was improved, letting the native clients provide a nicer mobile user experience.
https://peertube.tifox.fr/videos/embed/f5058788-6614-433d-a513-00a1bc3cf877
You can find the video on peertube and Vimeo.
How to Update?
We started to use composer for dependency management. This means, that if you are using git to manage the Friendica sources on your server, there is now an additional step in the update process. If you used the archives provided, you don’t need to care about it, as the archives contain the dependencies as well.
Should you encounter any problems while testing the RC code, please let us know about in the Friendica support forum, at github or over any other of the support channels.
Independent of the update path you are choosing, please be aware that there are some changes to the database structure to enhance the performance of Friendica that will be applied automatically to your database. Depending on the size of your database, especially the item table, these changes can take several hours.
If you are updating from a very old version of Friendica, you have to first update to version 3.5.4 before you can update to the 3.6 release.
Please note that due a slight oversight we did not encounter during testing in the RC phase you currently need php7 with the version 3.6. We are working on a 3.6.1 release that will then work again with php5.6. 3.6.1 should be available soon.
Updating with git from the stable (master) branch
As mentioned above, Friendica is now using composer for dependency management. This means that you have to do one further step when updating your git repository. This can be either an additional command every time you update, or adding a shell script to a git hook.
Composer needs to be able to unpack the downloaded archives, hence you need to have the PHP zip module available on your server.
If you want to do it all manually, then use the following sequence of commands: starting in the base directory of your Friendica installation.
git pullphp util/composer.phar installcd addongit pull
This will download the updated sources from github, call composer to get the dependencies and then change into the addon repository to fetch the new code there as well.
If you don’t want to remember this every time you pull, you can also use a so called git-hook to do it automatically. Please have a look at the docs for further information about this.
Updating with git from the RC or the development branches
As the changes regarding the dependency management are likely already in place on your system, a git pull in your Friendica core repository and the addon repository should bring you on the latest code as usual.
If you helped testing the release candidate–thanks a lot for helping!–you need to decide either to checkout the master or develop branch after the pull.
If you are using the develop branch, please be reminded about the recent path changes for many scripts.
Updating using the source archives
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-3.6.zip or tar.gz and friendica-addons-3.6.zip or 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 .htconfig.php file to friendica_new. 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 that you use the friendica-full-3.6 archives), so you don’t have to worry about them.
After you performed the update, you need to touch your cron job for the background process. The script handling the worker has been moved to scripts directory. So your cron job must now contain: something like
/usr/bin/php scripts/worker.php
instead of the old location in the include directory.
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!
landing page for visitors using the frio theme
Friendica 3.5.4 released
Dear Federation, the Friendica team is pleased to announce the release of Friendica *Asparagus* 3.5.4.
This release is a hotfix release for a bug that was overlooked in the 3.5.3rc phase during saving searches to the users side menu. It also includes fixes to smaller issues we had with relocating accounts from one node of the network to another. As well as the support for the new Diaspora* relocation signal, that was planned for the upcoming 3.6 release of Friendica. Which means if you move to another node, now your Diaspora contacts will receive the signal as well and vice versa.
Additionally we fixed numerous bugs that the community had found and we polished some quirks. For the complete list of changes, please see the CHANGELOG file.How to Update?
If you used `git` to install your copy of Friendica and use the master or develop branch, a git pull is enough to upgrade.
If you have helped to iron out quirks for this release and used the 3.5.4rc branch of the repository you just need to pull from the repository and switch to either the master or develop branch.
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-3.5.3.zip and friendica-addons-3.5.3.zip) and unpack it on your local computer.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 🙂GitHub - friendica/friendica: Friendica Communications Platform
Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.GitHub
Friendica 3.5.4 released
Content warning: Dear Federation, the Friendica team is pleased to announce the release of Friendica *Asparagus* 3.5.4. This release is a hotfix release for a bug that was overlooked in the 3.5.3rc phase during saving searches to the users side menu. It also includes fixe
Dear Federation, the Friendica team is pleased to announce the release of Friendica *Asparagus* 3.5.4.
This release is a hotfix release for a bug that was overlooked in the 3.5.3rc phase during saving searches to the users side menu. It also includes fixes to smaller issues we had with relocating accounts from one node of the network to another. As well as the support for the new Diaspora* relocation signal, that was planned for the upcoming 3.6 release of Friendica. Which means if you move to another node, now your Diaspora contacts will receive the signal as well and vice versa.
Additionally we fixed numerous bugs that the community had found and we polished some quirks. For the complete list of changes, please see the CHANGELOG file.
If you used `git` to install your copy of Friendica and use the master or develop branch, a git pull is enough to upgrade.
If you have helped to iron out quirks for this release and used the 3.5.4rc branch of the repository you just need to pull from the repository and switch to either the master or develop branch.
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-3.5.3.zip and friendica-addons-3.5.3.zip) and unpack it on your local computer.
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 🙂
This release is a hotfix release for a bug that was overlooked in the 3.5.3rc phase during saving searches to the users side menu. It also includes fixes to smaller issues we had with relocating accounts from one node of the network to another. As well as the support for the new Diaspora* relocation signal, that was planned for the upcoming 3.6 release of Friendica. Which means if you move to another node, now your Diaspora contacts will receive the signal as well and vice versa.
Additionally we fixed numerous bugs that the community had found and we polished some quirks. For the complete list of changes, please see the CHANGELOG file.
How to Update?
If you used `git` to install your copy of Friendica and use the master or develop branch, a git pull is enough to upgrade.
If you have helped to iron out quirks for this release and used the 3.5.4rc branch of the repository you just need to pull from the repository and switch to either the master or develop branch.
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-3.5.3.zip and friendica-addons-3.5.3.zip) and unpack it on your local computer.
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 🙂
GitHub - friendica/friendica: Friendica Communications Platform
Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.GitHub
Friendica 2018.05 released
Content warning: Dear Federation, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.05. Back on track with scheduled releases, after 3.6 took such a long time. In this release we have packed some bug fixes and enhancements. Afte
Dear Federation, the Friendica team is pleased to announce the release of Friendica The Tazmans Flax-lily 2018.05.
Back on track with scheduled releases, after 3.6 took such a long time. In this release we have packed some bug fixes and enhancements. After an incompatibility glitch with the last release, Friendica 2018.05 is now again compatible with PHP 5.6. However we recommend using a more recent PHP version to further enhance the performance gain from the ongoing overhaul of the Friendica code and processes. Obviously GDPR was one thing we concentrated on for this release. Identifying problems in existing features (e.g. account and node mobility), adding new features (see below) and making things more transparent. To make a long story short, here a list of the noteworthy changes since the last release:
wordcloud from the commit messages
Thanks to everyone who made this release possible, by writing code, translating the user interface and reporting issues!
Ensure that the last backup of your Friendica database was done recently. While testing, we did not encounter problems, but better save than sorry.
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-2018.05.tar.gz and friendica-addons-2018.05.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 .htconfig.php file. 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-2018.05 archive), so you don’t have to worry about them.
Regardless of the branch you are on (master, develop or 2018.05-rc) all you have to do to get the new code is to run
git pull
on your server in the base and the addon directory. Remember to update the dependencies via composer as well.
If you helped testing the release candidate, you should also switch to either the master or the develop branch. Thanks for testing!
If you are updating from an older version then the 3.6 release, please be aware that Friendica is now using composer to manage the dependencies. After you pulled the latest code, you have to check the dependencies for updates as well. To do so run
bin/composer.phar install
from the base directory of your Friendica installation. To be able to extract the downloaded archives, you need to have the php-zip module installed on your server. If you don’t want to remember this every time you pull, you can also use a so called git-hook to do it automatically. Please have a look at the docs for further information about this.
If you are updating from a version older then 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.
If you are updating from the 3.6 release (or older versions) of Friendica please remember to change the path to the worker in the cron job to adopt the changed location.
It should now be something along these lines:
/usr/bin/php bin/worker.php
Among other things the worker will detect changes to the database structure. The changes will be applied automatically and may, depending on the size of your table (especially the item table) and the available resources on the server, take some time. On larger systems this can be hours.
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!
Back on track with scheduled releases, after 3.6 took such a long time. In this release we have packed some bug fixes and enhancements. After an incompatibility glitch with the last release, Friendica 2018.05 is now again compatible with PHP 5.6. However we recommend using a more recent PHP version to further enhance the performance gain from the ongoing overhaul of the Friendica code and processes. Obviously GDPR was one thing we concentrated on for this release. Identifying problems in existing features (e.g. account and node mobility), adding new features (see below) and making things more transparent. To make a long story short, here a list of the noteworthy changes since the last release:
- Finnish translation was added to the repository from Transifex. With it, Friendica now has 20 localizations from which 11 have more then 80% of the core plattform translated (DE, EN, EN-GB, EN-US, ES, FI, FR, IT, PL, RU, ZH-CN).
- New module for Terms of Services for your node that can be activated from the admin panel. If the module is activated links from the general information page and the user registration will be added. Additionally a basic privacy statement can be shown in both, the TOS page and the registration page.
- Many utility scripts are now bundled in a console that can be found in the bin directory. Please see bin/console –help for all available commands.
- When entering a new password, the choosen one will be checked locally against a database of exposed passwords.
- As libravatar is closing their service we have added a new alternative to the gravatar service based on David Revoy’s cat-avatar-generator: the catavatar.
- The long deprecated themes frost( and frost-mobile have been removed from the Friendica repository. If you need them, you can find them in the deprecated-themes repository.
wordcloud from the commit messages
Thanks to everyone who made this release possible, by writing code, translating the user interface and reporting issues!
How to update?
Pre-Update procedures
Ensure that the last backup of your Friendica database was done recently. While testing, we did not encounter problems, but better save than sorry.
From the archive files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive from GitHub (friendica-full-2018.05.tar.gz and friendica-addons-2018.05.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 .htconfig.php file. 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-2018.05 archive), so you don’t have to worry about them.
From git
Regardless of the branch you are on (master, develop or 2018.05-rc) all you have to do to get the new code is to run
git pull
on your server in the base and the addon directory. Remember to update the dependencies via composer as well.
If you helped testing the release candidate, you should also switch to either the master or the develop branch. Thanks for testing!
If you are updating from an older version then the 3.6 release, please be aware that Friendica is now using composer to manage the dependencies. After you pulled the latest code, you have to check the dependencies for updates as well. To do so run
bin/composer.phar install
from the base directory of your Friendica installation. To be able to extract the downloaded archives, you need to have the php-zip module installed on your server. If you don’t want to remember this every time you pull, you can also use a so called git-hook to do it automatically. Please have a look at the docs for further information about this.
If you are updating from a version older then 3.5.4 you have to make the update process in two steps due to a change in the updating procedure. First update to the 3.5.4 release and then update to the current release.
Post-Update procedures
If you are updating from the 3.6 release (or older versions) of Friendica please remember to change the path to the worker in the cron job to adopt the changed location.
It should now be something along these lines:
/usr/bin/php bin/worker.php
Among other things the worker will detect changes to the database structure. The changes will be applied automatically and may, depending on the size of your table (especially the item table) and the available resources on the server, take some time. On larger systems this can be hours.
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!
Check for exposed password during password change · Issue #4604 · friendica/friendica
Today I stumbled on https://github.com/DivineOmega/password_exposed, a library that exposes a handy function to check if a given password has been part of the leaks recorded by https://haveibeenpwn...GitHub