- Issue created by @ccjjmartin
- Status changed to Needs work
22 days ago 2:29pm 8 August 2025 - π¬π§United Kingdom james.williams
The replacement pattern can be wrong simply because of module dependencies, even those for visibility conditions. See #3099693-3: Custom block Token Not render β . e.g. If your block has a user role condition, then the token has to start
[block_token:user:
! Perhaps it would be better to just remove/ignore the module name in the token, since the block ID is already unique? But that might break backwards-compatibility too as content might start showing that wasn't previously showing.