No. There are no plans to make Composer mandatory and most people don't touch it for Backdrop sites. While there are a few things you can do in Bee that you can't do in the UI, you can easily manage your site updates almost entirely through the user interface and without Bee.
One exception, but you can do this by editing the files through cPanel File Manager, FTP or some other way is when robots.txt, .htaccess or settings.php have changes that you need to apply. These are not replaced in the UI upgrade process (and won't be when the Bee upgrade command is complete) as it could override any custom settings.
Thank you very much for your fast answers and clear explanations !
I understand that the site is not corrupted and that there is no danger in leaving the code and the database in their...
If you want to try to fix it yourself now, I think you can manually set the schema version for the book module (in the system table) to 7000, and then try running the updates again. Test on a...
This was turned up as an issue with Drupal 6 -> 7 -> Backdrop upgraded sites because the schema version for Book is still from Drupal 6 and Backdrop's upgrade hooks don't fire. There's a...
For the dev meeting we still have last week's proposal (good progress there with our more urgent bugs, only one still open).
But a new problem popped up - phpcs, see https://github.com/...
Comments
No. There are no plans to make Composer mandatory and most people don't touch it for Backdrop sites. While there are a few things you can do in Bee that you can't do in the UI, you can easily manage your site updates almost entirely through the user interface and without Bee.
One exception, but you can do this by editing the files through cPanel File Manager, FTP or some other way is when
robots.txt
,.htaccess
orsettings.php
have changes that you need to apply. These are not replaced in the UI upgrade process (and won't be when the Bee upgrade command is complete) as it could override any custom settings.