In the issue about adding more settings to the breadcrumbs block I kept thinking that there are some block settings that you really want to apply to all instances of that block, not just one. Making changes to the header block, for example, can be tedious if you need to repeat the exact same change on every instance of the header block.
Custom blocks can store their configuration either in an individual config file, or as part of a layout. I would like propose that we provide that same functionality to all blocks.
Each block type can define whether - by default - it's configuration should be global (like header & breadcrumb blocks) specific (like the page title block) or provide an option to the user (like custom blocks). It not set, the block config should be treated as specific - so existing sites will not be affected.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface