I am getting this error for every Paragraphs feature I am trying to enable, even for very simple ones.

I looked at one of the field files noted in the error, and this is the list of dependencies:

dependencies:
  config:
    - field.storage.paragraph.field_table_row
    - paragraphs.paragraphs_type.table
    - paragraphs.paragraphs_type.table_row
  module:
    - entity_reference_revisions

I am not entirely sure, but how can a feature module contain a dependency on itself (field.storage.paragraph.field_table_row)? Won't that always prevent it from being enabled?

Comments

kevinquillen created an issue. See original summary.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

It sounds like your feature has a field config item in it, and that field depends on a field storage as well as the two other items listed. You need to ensure you either (a) add these dependencies to the feature you're enabling or (b) probably better, add them to a different feature module that your feature has as a dependency.

In the feature you're enabling, what are the files in config/install?

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

Hmm. It looks like most of the files that should be there are there, except the storage ones. Is field storage definitions not detected or not included for best practices? This feature is meant to introduce/install that field in a paragraph.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

On the feature overview admin page (admin/config/development/features), you'll see how Features assigns a site's configuration to different packages or features. See this (somewhat outdated) screenshot. By default, field storages that are used in more than one feature will be assigned to the 'core' feature, which becomes a dependency of other features that have fields that require one of those field storages.

Is this what you're seeing? Have you generated the 'core' feature?

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

Ok, is that what I should do? I have not made a "Core" feature. I am just trying to cherry pick certain things from one install to a new install (different site with same functionality). There is a lot of overlap in terms of fields, media bundles and text formats across Paragraphs, and perhaps this is where I am running into trouble.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

Yes, it sounds like you may need to generate a core feature along with your other ones.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

So is that the way to start with any features you want to bring into a new site? A Core export is required? Will that lock me into any config or variables that are set in that feature in the future? Or is that a way to get a dump of all the field config / field storage in use so that I don't run into this issue?

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

This is what I got after exporting Core and trying to enable on another site:

Unable to install Core, core.entity_form_display.block_content.sidebar_promo.default, core.entity_form_display.node.face_of_certification.default, core.entity_form_display.node.homepage.default, core.entity_form_display.node.product.default, core.entity_form_display.node.resource.default, core.entity_form_display.paragraph.accordion.default, core.entity_form_display.paragraph.accordion_callout.default, core.entity_form_display.paragraph.accordion_item.default, core.entity_form_display.paragraph.accordion_links.default, core.entity_form_display.paragraph.featured_nurse.default, core.entity_form_display.paragraph.full_width_row.default, core.entity_form_display.paragraph.icon_callout.default, core.entity_form_display.paragraph.icon_callout.editing, core.entity_form_display.paragraph.motivation_card.default, core.entity_form_display.paragraph.sample_question.default, core.entity_form_display.paragraph.sample_questions.default, core.entity_form_display.paragraph.split_60_40.default, core.entity_form_display.paragraph.table.default, core.entity_form_display.paragraph.table_row.default, core.entity_form_display.paragraph.text_editor.default, core.entity_form_display.paragraph.three_up_component.default, core.entity_form_display.paragraph.user_motivation.default, core.entity_form_display.paragraph.video.default, core.entity_view_display.block_content.sidebar_promo.default, core.entity_view_display.media.image.article_listing, core.entity_view_display.media.image.callout, core.entity_view_display.media.image.content_embed, core.entity_view_display.media.image.face_of_certification, core.entity_view_display.media.image.featured, core.entity_view_display.media.image.hero, core.entity_view_display.media.image.homepage_hero, core.entity_view_display.media.image.product_listing, core.entity_view_display.media.image.sidebar_promo, core.entity_view_display.media.image.video, core.entity_view_display.node.article.alert, core.entity_view_display.node.article.hero, core.entity_view_display.node.article.listing, core.entity_view_display.node.face_of_certification.default, core.entity_view_display.node.face_of_certification.teaser, core.entity_view_display.node.homepage.default, core.entity_view_display.node.homepage.hero, core.entity_view_display.node.page.alert, core.entity_view_display.node.page.hero, core.entity_view_display.node.page.search_index, core.entity_view_display.node.product.default, core.entity_view_display.node.product.featured, core.entity_view_display.node.product.listing, core.entity_view_display.node.product.teaser, core.entity_view_display.node.resource.default, core.entity_view_display.node.resource.resource, core.entity_view_display.node.resource.teaser, core.entity_view_display.paragraph.accordion.default, core.entity_view_display.paragraph.accordion_callout.default, core.entity_view_display.paragraph.accordion_item.default, core.entity_view_display.paragraph.accordion_links.default, core.entity_view_display.paragraph.featured_nurse.default, core.entity_view_display.paragraph.full_width_row.default, core.entity_view_display.paragraph.icon_callout.default, core.entity_view_display.paragraph.icon_callout.preview, core.entity_view_display.paragraph.motivation_card.default, core.entity_view_display.paragraph.sample_question.default, core.entity_view_display.paragraph.sample_questions.default, core.entity_view_display.paragraph.split_60_40.default, core.entity_view_display.paragraph.table.default, core.entity_view_display.paragraph.table_row.default, core.entity_view_display.paragraph.text_editor.default, core.entity_view_display.paragraph.three_up_component.default, core.entity_view_display.paragraph.user_motivation.default, core.entity_view_display.paragraph.video.default, field.field.block_content.sidebar_promo.field_sidebar_image, field.field.block_content.sidebar_promo.field_title_image, field.field.media.image.field_image, field.field.node.article.field_article_image, field.field.node.article.field_hero_image, field.field.node.face_of_certification.field_face_image, field.field.node.homepage.field_hero_image, field.field.node.page.field_hero_image, field.field.node.product.field_product_image, field.field.node.resource.field_resource_image, field.field.paragraph.accordion.field_accordion_item, field.field.paragraph.accordion_callout.field_callout, field.field.paragraph.accordion_item.field_accordion_body, field.field.paragraph.accordion_item.field_accordion_callout_title, field.field.paragraph.accordion_item.field_accordion_step_title, field.field.paragraph.accordion_item.field_accordion_title, field.field.paragraph.accordion_item.field_callouts_and_links, field.field.paragraph.accordion_links.field_links, field.field.paragraph.faces_of_certification.field_left_share_link, field.field.paragraph.faces_of_certification.field_right_share_link, field.field.paragraph.featured_courses.field_link, field.field.paragraph.featured_nurse.field_link, field.field.paragraph.featured_nurse.field_nurse_image, field.field.paragraph.featured_nurse.field_rich_text, field.field.paragraph.full_width_row.field_content, field.field.paragraph.icon_callout.field_button_1, field.field.paragraph.icon_callout.field_button_2, field.field.paragraph.icon_callout.field_description_1, field.field.paragraph.icon_callout.field_description_2, field.field.paragraph.icon_callout.field_icon_1, field.field.paragraph.icon_callout.field_icon_2, field.field.paragraph.icon_callout.field_title_1, field.field.paragraph.icon_callout.field_title_2, field.field.paragraph.motivation_card.field_link, field.field.paragraph.motivation_card.field_rich_text, field.field.paragraph.news_resources.field_news_link, field.field.paragraph.news_resources.field_rich_text, field.field.paragraph.news_resources.field_search_link, field.field.paragraph.sample_question.field_question, field.field.paragraph.sample_question.field_question_options, field.field.paragraph.sample_questions.field_questions, field.field.paragraph.split_60_40.field_content_limit_2, field.field.paragraph.table.field_header_left, field.field.paragraph.table.field_header_right, field.field.paragraph.table.field_table_row, field.field.paragraph.table_row.field_cell_left, field.field.paragraph.table_row.field_cell_right, field.field.paragraph.text_editor.field_rich_text, field.field.paragraph.three_up_component.field_3u_link, field.field.paragraph.three_up_component.field_end_description, field.field.paragraph.three_up_component.field_rich_text, field.field.paragraph.user_motivation.field_motivation_card, field.field.paragraph.video.field_video_id, field.field.paragraph.video.field_video_image have unmet dependencies.

I am just going to uninstall and reinstall Features and export Core without touching anything.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

For your use case, you might want to look also at the Configuration Split module.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

So... I guess I am confused. Is the 8.x branch of Features unable to selectively pull functionality like a couple of content types and views or paragraphs and pull that into brand new sites? I need to do this for about four new websites right now. They'll all share the same base functionality (filter formats, content types, paragraph types) and it sounds like Features would be best fit to export and bring in that functionality.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

This time I tried "Import Missing" from the Feature page, I get a slightly different error:

Error importing field.field.paragraph.three_up_component.field_rich_text : Missing bundle entity, entity type paragraphs_type, entity id three_up_component.
Error importing field.field.paragraph.three_up_component.field_end_description : Missing bundle entity, entity type paragraphs_type, entity id three_up_component.
Error importing field.field.paragraph.three_up_component.field_3u_link : Missing bundle entity, entity type paragraphs_type, entity id three_up_component.
Error importing field.field.paragraph.news_resources.field_search_link : Missing bundle entity, entity type paragraphs_type, entity id news_resources.
Error importing field.field.paragraph.news_resources.field_rich_text : Missing bundle entity, entity type paragraphs_type, entity id news_resources.
Error importing field.field.paragraph.news_resources.field_news_link : Missing bundle entity, entity type paragraphs_type, entity id news_resources.
Error importing field.field.paragraph.motivation_card.field_rich_text : Missing bundle entity, entity type paragraphs_type, entity id motivation_card.
Error importing field.field.paragraph.motivation_card.field_link : Missing bundle entity, entity type paragraphs_type, entity id motivation_card.
Error importing field.field.paragraph.featured_nurse.field_rich_text : Missing bundle entity, entity type paragraphs_type, entity id featured_nurse.
Error importing field.field.paragraph.featured_nurse.field_nurse_image : Missing bundle entity, entity type paragraphs_type, entity id featured_nurse.
Error importing field.field.paragraph.featured_nurse.field_link : Missing bundle entity, entity type paragraphs_type, entity id featured_nurse.
Error importing field.field.media.image.field_link : Missing bundle entity, entity type media_bundle, entity id image.
Error importing field.field.media.image.field_image : Missing bundle entity, entity type media_bundle, entity id image.
Error importing field.field.media.image.field_description : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.paragraph.three_up_component.default : Missing bundle entity, entity type paragraphs_type, entity id three_up_component.
Error importing core.entity_view_display.paragraph.motivation_card.default : Missing bundle entity, entity type paragraphs_type, entity id motivation_card.
Error importing core.entity_view_display.paragraph.featured_nurse.default : Missing bundle entity, entity type paragraphs_type, entity id featured_nurse.
Error importing core.entity_view_display.media.image.video : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.media.image.sidebar_promo : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.media.image.hero : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.media.image.featured : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.media.image.default : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.media.image.content_embed : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_view_display.media.image.callout : Missing bundle entity, entity type media_bundle, entity id image.
Error importing core.entity_form_display.paragraph.three_up_component.default : Missing bundle entity, entity type paragraphs_type, entity id three_up_component.
Error importing core.entity_form_display.paragraph.motivation_card.default : Missing bundle entity, entity type paragraphs_type, entity id motivation_card.
Error importing core.entity_form_display.paragraph.featured_nurse.default : Missing bundle entity, entity type paragraphs_type, entity id featured_nurse.
Error importing core.entity_form_display.media.image.default : Missing bundle entity, entity type media_bundle, entity id image.

It looks like a lot of things imported correctly, and this was leftover. Am I just missing Paragraphs Type and Media Type exports?

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

It looks like you have a complex site with a lot going on and are running into issues that are beyond the scope of what I can provide here in the way of tips. You could try (re)reading the handbook documentation, including the Features building workflow page.

Lennard Westerveld’s picture

Lennard Westerveld
🤖
Primary language Dutch
Location Dordrecht, Netherlands
CreditAttribution: Lennard Westerveld as a volunteer commented

I have the same issue (i think), by creating a fresh website and enable all features giving this unmet dependentie errors because some dependentie is in a not enabled module or this config is in a other feature but not yet imported.
What i got for example is a ft_fields feature where all the field storages are in but when i create a new ECK entity type then the field cannot be imported because the feature for the ECK entity type has not been imported or when i trying to enable ECK entity type feature its not possible because the field.field settings are there in and they have a dependentie on the storage.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

Yes.

So, I gave this one last shot. I went in and "created" a new feature, and selected all Paragraph types. Then I selected all related fields and field storage. I also threw in my only media bundle, because some Paragraphs have a media reference field.

I then de-selected all fields, blocks, block types etc that got auto selected but are unrelated. I also had to add in view modes that were not detected on the Paragraphs.

I then had to remove any node-type dependency from the yaml and basically eliminate any Paragraph that was referencing nodes, I don't need them and it creates a dependency on node types.

After that, I was getting null pointer exceptions on EntityDisplayBase for form displays. I then experimented by basically deleting any yaml regarding form display and content display, and deleted an entity embed yaml that was exported because it caused a WSOD.

When I removed all of those things, I could finally import ~25 Paragraph types as a base starting point.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

Now that I have a base, I have deleted some paragraph types and things I won't need in this new site.

Is the procedure now to tag the feature version 8.x-1.1 and write over the existing one? I have a lot of things reported as missing, but, that's due to me deleting them from active config. I am working at refining what I have, so I expect the base feature to start shrinking.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen at Velir commented

So now I have been able to prune down my paragraphs to what I want or don't need and generated two new updates to the Feature module itself.

I nuked my install and started over, this time I fared much better, EXCEPT it would not enable again. This time, it said "editor.editor.full_html...." and a couple other filter formats were "already installed" and therefore could not install the feature. I tried three times.

I went in and enabled Features and Features UI so I could look at the Feature from the admin UI. Nothing suspect or flagged - went back to the Extend screen and this time the Feature module enabled with no fuss. Would be great if I could narrow it down so the install process is repeatable.

What was it about enabling Features/Features UI module that made the error about filter formats go away? This kind of stuff seems pretty standard to me as far as full html and basic html config go.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented

What was it about enabling Features/Features UI module that made the error about filter formats go away?

Drupal core will not allow you to install a module that provides configuration that already exists on the site.

To facilitate feature development workflow, the Features module overrides this for features modules, so that it's possible on a given site to (a) generate feature modules and (b) install the newly generated modules on the originating site.

r.spring’s picture

r.spring CreditAttribution: r.spring commented

I've noticed that when creating a feature that selecting both your paragraph types and their associated fields doesn't actually export the paragraph types even if they're explicitly selected (i.e. the necessary paragraphs.paragraphs_type.my_example.yml config files).

If you create a new feature and just select the necessary paragraph types it should automatically export dependent fields AND the paragraph bundles.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented
Status: Active » Fixed

Please feel free to reopen if the answers here don't cover it.

Status: Fixed » Closed (fixed)

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

devil2005’s picture

devil2005 CreditAttribution: devil2005 commented

Hi,

Any news of this request ?
I try to export a content type with paragraphs and it's broken for import :(

Thanks

yuseferi’s picture

yuseferi CreditAttribution: yuseferi as a volunteer and commented

any update on this how can we export paragraphs and content type from another website by features module and import it in another sie. it returns ` have unmet dependencies: ` for me but I'm sure I've selected all dependencies.