This is part of #1723
When you hover over a contextual link of a block, you'll notice that the URL is something like /admin/structure/layouts/manage/default/configure-redirect/[block_hash]&destination=node#configure-block:[block_hash]. That helps us open the "Configure block" dialog for that specific block when we open the Layout admin UI. This is great, but it would be even more useful if in the locked background we scrolled to the specific region where the block is placed. Let me explain...
Say I want to configure the "Powered by Backdrop" block (which happens to be at the bottom of the page and the bottom of the Layout UI too). When I click on the "Configure block" contextual link, this is where I end up:
I think that it would be better UX if we actually scrolled down (using # anchors) to the part of the layout where the block is located. Like so:
Recent comments
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
custom module not showing up in modules list