Until some other more pressing cause crops up, these donations will stay in my pocket. They'll go toward things like food and bills. Reminder that my dayjob pays me in free housing, so I'm reliant on donations from y'all to do things like pay for my email server.
You can rename the file_embed table to file_oembed if you wish to get back on v1.20.9. GNU social v2 (which is the version in master and nightly) is not in a release state, not even in alpha, that's why there are no upgrade instructions yet. Public/Productions instances should use the 1.20.x branch. I believe that GNU social 2 is only used by @aab who is sharing his logs and reporting bugs and by the devs in their local and online test instances. Unless you want to contribute with code, it is probably better to use 1.20.x which is a stable branch. I will let you know when GS v2 gets an alpha release :)
@louis You can drop the file_oembed table and run the Embed plugin's fixup script.
That probably has happened because you checkedout either in master or nightly, then in 1.20.x and then back in master or nightly. GS can't automagically downgrade, it only expects upgrades (without downgrades by the middle).
git remote rm origin # Delete the existing remote git remote add origin https://notabug.org/diogo/gnu-social.git # Add the notabug remote git remote update # Fetch the current state of the art git checkout 1.20.x # Checkout on the stable branch git pull # Update your GNU social files ./scripts/upgrade.php -f # Upgrade GNU social
Hi @louis before the "big merge" @MMN-o (official maintainer) will review the changes in the notabug fork.
GNU.io had some issues when we were re-activating development and thus we just temporarily moved to notabug. Despite that, this is an official GNU social continuation, otherwise it wouldn't be on https://www.gnu.org/software/soc-projects/ideas-2019.html#social
This repository is under active development and our latest stable release was v1.20.9. @MMN-o is aware of all this effort and we have consistently been mentioning him in every release information on !gnusocial and chatting about the changes in the #social IRC.
@kim Just fork, do your changes and open an MR in notabug :)
We can have the progress bar there as long as it isn't required in order to make the installation happen (if JS enable it shows up otherwise it doesn't).
You can MR your changes to master. In nightly I'm working in adding a newer Modules system. We intend to ask the user which plugins he wants enabled in his instances during install time.
I'm now having lunch but after we can talk about this in IRC :D