"Create referenced entities if they don't already exist" does not respect published/unpublished default [#2845138]

Problem/Motivation

When a referenced entity is auto-created from an Autocomplete ER widget, it is created as Published regardless of what is set as default for its content type which disrupts the publishing workflow.

Steps to reproduce:
1. Create content type A, make sure Published is unchecked in the Publishing options.
2. Create a test node of type A, verify that it's Unpublished.
3. Create content type B, add an ER field referencing A, check "Create referenced entities if they don't already exist", choose Autocomplete widget in Form display.
4. Create a test node of type B, type nonexistent A label in field A, save B.
5. Verify that the auto-created A node is Published.

Proposed resolution

Respect the default set in the content type settings when auto-creating a referenced entity.

Comments

Comment #1

20 January 2017 at 05:40

ndlarge created an issue. See original summary.

Comment #2

marassa CreditAttribution: marassa commented 29 March 2017 at 07:01

Component:

entity_reference.module

» entity system

Comment #3

29 March 2017 at 07:01

Version:

8.2.4

» 8.2.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Comment #4

29 March 2017 at 07:01

Version:

8.2.x-dev

» 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Comment #5

marassa CreditAttribution: marassa commented 29 September 2021 at 15:32

Status:

Active

» Needs review

The fix is available in the linked issue https://www.drupal.org/project/drupal/issues/2845144

Comment #6

29 September 2021 at 15:32

Version:

8.9.x-dev

» 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Comment #7

29 September 2021 at 15:32

Version:

9.2.x-dev

» 9.3.x-dev

Comment #8

29 September 2021 at 15:32

Version:

9.3.x-dev

» 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Comment #9

29 September 2021 at 15:32

Version:

9.4.x-dev

» 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.