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
The block system and API in Backdrop is very different from Drupal's. In Backdrop, as in Drupal, modules can define blocks in code (in fact some of the API at this level is the same, with...
Drupal block module conversion
This was from examining line 2463- of the webform.module, where // Attach necessary JavaScript and CSS. $form['#attached'] = array( 'css' => array(backdrop_get_path('module', 'webform...
How do I diagnose Webform Conditionals failing?
d'oh. Because of course it is reassigning. Don't mind me... the correct syntax is $form['#attached']['js'][] = backdrop_get_path('module', 'mymodule') . '/mymodule.js';
How do I diagnose Webform Conditionals failing?