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
Comments
Comment #2
Pegasus360 CreditAttribution: Pegasus360 commentedFound a Solution:
For some reason the paragraph types for image and video were corrupt.
The manage form tab for both types was not functional.
I deleted the image field and video field from each paragraph and recreated these entity reference fields - media.
picked the widget for inline entity form simple for each
Now they both work when adding paragraphs to content
I think the best way to solve a headache problem is to post a question and minutes later you will find your own answer !!
Hope this helps.
Comment #3
t460s CreditAttribution: t460s commentedI'm having the same issue.
My drupal distribution is Thunder and I use Thunder Admin theme. I have several paragraph types with each one having an entity reference field of type media image among other fields. Before I could add content to these paragraph types without any problem. But, now when I try to add, the media image field doesn't show up. I am not sure how long this problem has been lying around, but I discovered it yesterday when I tried to add content to my site after at least two weeks. I use entity browser as the widget for this media image field.
The php error is as below:
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "inline_entity_form" plugin does not exist. in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (Zeile 52 in /var/www/html/sgwtest2/docroot/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).
I couldn't delete and recreate the fields as @Pegasus360 did, as I have lots of content on these fields. Instead I changed my admin theme to seven, and now it works again.
Also, if I use any widget other than entity browser, without changing the theme(i.e., use Thunder admin as before), it works.
I couldn't figure out what is causing this problem, Entity Browser or Thunder Admin theme.
Any help would be appreciated.
Thank you!
Comment #4
PepeMty CreditAttribution: PepeMty commentedHey there.
I have the very same situation: Thunder distro, image and video from Paragraphs doesn't open.
Any sugestions...?
Warm regards from sunny México...!
: )
Comment #5
Pegasus360 CreditAttribution: Pegasus360 commentedI posted this problem on the thunder distro.
https://www.drupal.org/node/2902814
This might be insightful or helpful but
The solution from chr.fritsch did not work for me.
Even though the problem above was fixed with deleting and recreating fields I am still getting
buggy hits from IEF like the error (non-fatal) below.
Notice: Undefined index: #submit in Drupal\inline_entity_form\ElementSubmit::addCallback()......
Comment #6
dcam CreditAttribution: dcam as a volunteer commentedThis 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 anentity_form_display
that used theinline_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.