Problem/Motivation

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.

Proposed resolution

Remove hard codet block_content usages in order to allow making every entity slot content.

Issue fork slots-3554628

Command icon Show commands

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

hydra created an issue. See original summary.

harlor made their first commit to this issue’s fork.

harlor’s picture

OK 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

harlor’s picture

Status: Needs review » Needs work
harlor’s picture

Status: Needs work » Needs review
hydra’s picture

Status: Needs review » Fixed

Since we have huge overlapping with https://www.drupal.org/project/slots/issues/3477579 we merged this over there so we can test both together.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

hydra’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.