Zum Inhalt der Seite gehen


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

How to Update


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

Updating from old Friendica versions


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

Pre-Update Procedures


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

Using Git


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

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

Using the Archive Files


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

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

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

Post Update Tasks


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

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

Known Issues


None at the time of writing.

How to Contribute


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

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

Thanks everyone who helped making this release possible and have fun!
https://friendi.ca/2021/09/25/friendica-2021-09-released/
Thank you for your awesome work!
Smooth as always. Thank you very much!
Good, I can plan this for next week. Thanks to the dev team
Can i "uodate" from 2021.09 Dev to 2021.09 stabel?
Updating fd37a5767..255b98b5b
error: Your local changes to the following files would be overwritten by merge:
.drone.yml
.github/workflows/releases.yml
CHANGELOG...
src/Module/Api/Mastodon/Unimplemented.php
src/Module/Attach.php
src/Module/BaseAdmin.php
src/Module/BaseApi.php
src/Module/B
Aborting

Is these correct, sorry its my first update. Thats after "git pull
Dieser Beitrag wurde bearbeitet. (2 Jahre her)
Please run git checkout -- . first to reset all your unwarrantedly modified files first.
Dieser Beitrag wurde bearbeitet. (2 Jahre her)
@Hypolite Petovan
git checkout — . is not working
git checkout:
Your branch is behind 'origin/develop' by 624 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
root@Friendica:/var/www/friendica git pull
Updating fd37a5767..255b98b5b
error: Your local changes to the following files would be overwritten by merge:
.drone.yml
.github/workflows/releases.yml
CHANGELOG
@Olaf@Hypolite Petovan The full stop is important:
git checkout -- .
Otherwise a hard reset achieves the same untainted worktree as well:
git reset --hard

Dausacker hat dies geteilt.

For the moment stable and develop are very similar, you can still switch back to stable with no negative consequences.
@Olaf@Hypolite Petovan@Claes Wallin 🇸🇪🇭🇰develop is currently three pull requests ahead of stable none has changed the database structure (which is the main block to reverting to an older version) so, you can just git checkout stable and switch to the stable version.
Fiendica is the evil twin of Friendica. 😈
Known Issues update:

Update Mon Oct 4th: 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.

teilten dies erneut

@hoergen there must have been some interaction with the original posting or a comment, that lead to nodes refetching the conversation. The posting was not re-posted to Twitter, so it was not "re-send".
@Tobias@Michael Vogel@hoergen I'm not sure what the feature would be exactly?
@Hypolite Petovan to automatically ignore new comments to very old (being configured by the users) conversations. This one had been deleted from my node (by expiration time passed) but was re-fetched into the "Latest Post" network tab, by an activity somewhere in the thread.
@Andy H3
liking old posts should not should not bring them up at all
This double negative is confusing 😵

Diese Webseite verwendet Cookies zur Erkennung von wiederkehrenden Besuchern und eingeloggten Nutzern. Durch die weitere Benutzung der Webseite akzeptierst du die Verwendung der Cookies.