Current workflow: 1. Go to the layout edit page. 2. Click the "Add block" action of any region. 3. Select any block type. 4. Change your mind about the selected block type. 5. Close the "Add block" dialog (using the x button at the top right corner) 6. Click the "Add block" action of the region. 7. Make sure you select the correct block type this time because you'll have to go through this over again and it's tedious.
How it should work: 1. Go to the layout edit page. 2. Click the "Add block" action of any region. 3. Select any block type. 4. Change your mind about the selected block type. 5. Click the "Back" button (the one we'll add in this issue - for now just imagine it's there ) 6. Select correct block type this time. Don't worry if you get it wrong again - you can always hit the imaginary "Back" button :stuck_out_tongue_winking_eye:
1 step less = better UX :wink: :wine_glass:
Recent comments
In page.tpl.php you can get the current path and add it to the class array $classes[] = 'path-' . str_replace('/', '', $_SERVER['REQUEST_URI']); You will get an original class for each page....
Insert custom class into body tag
https://www.drupal.org/project/views/issues/1266388 shows that this is an architectural issue, and requires another 2 hooks being adjusted. It would be really nice to add comments/notes to...
node access
Hmmm, from D7 ancient tomes: from https://drupal.stackexchange.com/questions/7056/limit-which-roles-can-view-a-node-basing-on-its-content-type yet https://docs.backdropcms.org/api/...
node access