Cloned content type missing UUID

Not fixed in latest release 2.0

@_kom__ : Fixed the issues in the new release (2.2). Request you to check and reopen issue if still persists

Not fixed in 2.2.0 in /config/sync/core.entity_form_display.taxonomy_term...

By the way, I do not see announced feature "role clone" neither in 2.0, nor in 2.2 release. Can you point out commits in commit log that fix these?

Please Update the issue description with the required steps to reproduce the issue.
Because we can not reproduce it and it does not exist at all.
Feel free to open a new issue.
I close the issue as Fixed.

Did you try to reproduce it on single Dupal installation?
You must have TWO Drupal sites (e.g. development and production) - one for export configuration of cloned entity and another for import this configuratoin. When configuration file (namely, "...form_display...") is imported in other installation it gets uuid in Drupal database automatically because this field is missed in imported configuration file. As a result, configurations remain unsynchronized with DB because imported file has no row with uuid and hence they are different.

Of course, when you try to do export/import on single Drupal installation you can't see differences, because both configurations (in database and exported file) has no uuid.

I don't know how to explain this simple fact more clear.

See example above:

langcode: ru
status: true
dependencies:
  config:
    - field.field.taxonomy_term.volosti_kaz.field_guberniya
....

And correct exported config should be:

uuid: 00091558-3256-4dae-ac66-49f9cb058eed
langcode: ru
status: true
dependencies:
  config:
    - field.field.taxonomy_term.volosti_kaz.field_guberniya

Not fixed in 3.0.1.

The simplest way to reproduce (I can't put it into issue description, because I'm not author of this issue).

1. Upgrade module to 3.0.1
2. Open /admin/config/entity-type-clone and select any node type, e.g. Page
3. Assign Target bundle name 'Page Clone' and Target bundle machine name 'page_clone'
4. Click 'Clone' button
5. Go to /admin/config/development/configuration
6. There will be a lot of created configurations (depends on fields that you have added earlier to node type Page). Every configuration has the row 'uuid: ...' except -
7. Open 'core.entity_form_display.node.page_clone.default' - it has NO 'uuid: ...' row.

This problem still appears in version 3 and it is impossible to create cloned content.

The fields are cloned but when you go to create a new content /node/add/content_type the fields do not appear, the problem seems to be in the form display that is not being created correctly.

Hi, I have just pushed an MR for review, with these new adjusment the error that I was presenting in the form display and uuid works well for me.

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