- Issue created by @Anybody
- Assigned to lrwebks
- First commit to issue fork.
- 🇩🇪Germany Anybody Porta Westfalica
Mind that there are two possible cases:
1. No matching ad generally exists for an ad block
2. The result of an existing ad is emptyI think we should not care for the second case.
There are two possible ways to solve this:
1. Checking if there is an ad for the block right before rendering the block at all (server-side)
2. Removing the block in JS if no ad is found for the block (client-side)I'd tend to 1. because that also allows Drupal to hide the whole region that contains the block server-side
Might happen that we also need (2) later.
- 🇩🇪Germany Anybody Porta Westfalica
See our example boilerplate implementation.
- 🇩🇪Germany Anybody Porta Westfalica
@lrwebks please quickly add an update hook to set the new config value TRUE for existing installs. Afterwards let's merge this!
- Issue was unassigned.
- Status changed to Fixed
about 1 month ago 1:04pm 18 June 2025 Automatically closed - issue fixed for 2 weeks with no activity.