IEF plugin does not exist

Created on 17 August 2017, over 7 years ago
Updated 29 February 2024, 9 months ago

this is a fresh thunder install with drupal commerce added.
In the process of testing the example content types included (article) the paragraphs worked fine. I could click on add a paragraph then the selection window would pop up and I could add an image paragraph.
But for some reason when I follow this same procedure the pop up window displays but the new image paragraph does not show up. Then the following php error shows up:

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "inline_entity_form" plugin does not exist. in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition()

The paragraph add window seems to work for link and text but not for image nor video.

I am not sure if this is a Thunder bug, a paragraphs bug, an inline entity form bug or a plugin manager bug. I cannot seem to resolve this issue or find any info or guidance.

Thoughts??
Thanks

πŸ› Bug report
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States Pegasus360

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    This must have been a Thunder bug. The inline_entity_form plugin doesn't exist, but it used to. That was the original machine name for one of the field plugins, going back to the D7 era. I think it was what became the Complex widget, but I'm not certain. If Thunder included configuration for an entity_form_display that used the inline_entity_form widget, then that configuration would caused the error described after IEF changed the widget machine name. Deleting and recreating the field would have solved the problem exactly as described in comment #2, though I have no ready explanation for those of you for whom that didn't work. I suspect that simply re-selecting and saving the widget that's used in the form should have repaired it too.

    In any case, Thunder no longer includes any configuration that uses the old plugin name. So I don't expect that it has the problem any longer.

Production build 0.71.5 2024