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.
I've started to port Entity Reference Autofill at https://github.com/backdrop-contrib/entityreference_autofill. It's not working so far, but I hope to make some progress in the next days....
Posted7 hours 51 min ago by Olaf Grabienski (Olafski) on:
From the chat:
did they already test to call the full (ugly) URL like index.php?q=node/12 or so? Either something with mod_rewrite (htaccess) or the clean urls setting, or......
Posted9 hours 11 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Could you provide the output from bee projects? This might help us spot if anything is amiss (e.g. a core module that is disabled).
I suggest putting it in a code block will make it easier...
Posted9 hours 20 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
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.