Closed (fixed)
Project:
Slots
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Oct 2025 at 18:12 UTC
Updated:
16 Nov 2025 at 15:24 UTC
Jump to comment: Most recent
Currently it's only possible to use block_content as slot content, even though the field theoretically could be added to any kind of entity and the underlaying API from the conditions module is not restricted to block_content.
Remove hard codet block_content usages in order to allow making every entity slot content.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #4
harlor commentedOK basically this seems to work, but:
- We need to make sure the new dependency dynamic_entity_reference is installed correctly (I added an update script that should fix that).
- I don't understand the changes in slots_inline_block - Do we want to support other content types here too?
-- Either we should drop the support for other inline content entities (As the module name suggests)
-- Or this needs some work
Comment #5
harlor commentedComment #6
harlor commentedComment #7
hydra commentedSince we have huge overlapping with https://www.drupal.org/project/slots/issues/3477579 we merged this over there so we can test both together.
Comment #9
hydra commented