Timeline for How do I programmatically remove a block?
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 10, 2019 at 11:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Aug 9, 2019 at 5:56 | history | edited | avpaderno♦ | CC BY-SA 4.0 |
removed tags from the title
|
Aug 8, 2019 at 20:32 | answer | added | Jean-Luc Barat | timeline score: 1 | |
Mar 11, 2019 at 15:00 | history | tweeted | twitter.com/StackDrupal/status/1105121354460876802 | ||
Mar 16, 2016 at 23:35 | comment | added | oaklandj | @marcvangend - Thanks. I did try that a couple of different ways (altering page.html.twig and using hook_page_alter to unset all other regions) and unfortunately all the blocks just moved over to the content block. :( | |
Mar 7, 2016 at 23:53 | comment | added | Berdir | Either that, or a custom page--path.html.twig that doesn't print those regions, hook_block_access() on your module on those pages or just build your own output with your own custom twig template and return it as a plain Response object. | |
Mar 7, 2016 at 20:27 | comment | added | marcvangend |
Did you consider a custom theme that doesn't render any regions? So your page.html.twig only contains something like {{ page.content }} and nothing else?
|
|
Mar 7, 2016 at 19:26 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
removed tags from title
|
Mar 7, 2016 at 19:05 | review | First posts | |||
Mar 7, 2016 at 19:07 | |||||
Mar 7, 2016 at 19:04 | history | asked | oaklandj | CC BY-SA 3.0 |