While it is possible to create a region to place token blocks in (and not even output that region in your template), and further to disable these token only blocks, but these steps should not be necessary. (I created a region labeled "Tokens (place here and disable)" to make this capability and approach explicit.)
In addition or instead, we could allow the use of any plugin-named block directly. This would meet my use case of not caring about special configuration.
Alternatively, we could probably provide a form that allows configuring blocks and forces the disabling and placing in a hidden region like core's default page_bottom region. Then it would work the same as now without the extra steps.
Decide if this is wanted.
Token blocks would (also) be managed on a dedicated page.
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Moving feature request to correct issue queue.
(Note to self: Token Block module → lets us put tokens in blocks. Block Token module turns blocks into tokens → .)
Yeah large +1 on this. I was looking for the checkbox on the block_content forms, but couldn't find it.
Makes much more sense to have this for block_content than for blocks that need to be placed!