Problem/Motivation

Block Types that are generated by the paragraph_block module should not create config or appear as a dependency in other configs.

Steps to reproduce

1. Create a content type
2. Add a field to that content type which references a paragraph type (f.e Hero) which can be used as a block
3. Save Content Translation Settings
4. Config Files and dependencies will be generated when exporting config
f.e:
- config/sync/core.base_field_override.block_content.hero.changed.yml
- config/sync/language.content_settings.block_content.hero.yml

That config will also have a dependency on "block_content.hero.yml" which does not exist.

Proposed resolution

No base field override config should be generated and no block type config.

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

n1k created an issue. See original summary.

gashunk’s picture

You get the same problem if you edit permissions on the content blocks of the paragraphs.

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

hydra’s picture

Version: 2.0.0-rc1 » 2.x-dev
Status: Active » Needs review

I addressed both issues:

  1. No config dependencies should be getting added when interacting with paragraph blocks to the fake block_content bundles. Instead we should rewrite them to proper dependencies of the underlying paragraph configs.
  2. Since paragraph blocks are no real blocks, there is no sense in creating content_translation configs for them. With the first fix, those configs won't break config import anymore, but since they are useless I removed them from the form entirely to have better UX.

This won't fix existing, broken config. This will only apply for new config.

drupatz’s picture

Status: Needs review » Reviewed & tested by the community

@hydra works great! Thx

  • hydra committed bfabd974 on 2.x
    Issue #3511185 by hydra, n1k, gashunk, drupatz: Incorrect config is...
hydra’s picture

Status: Reviewed & tested by the community » Fixed

Thx for testing! This is huge :)

Status: Fixed » Closed (fixed)

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