#DX (Developer Experience)

Rebase seems good.

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Rebased and applied outstanding suggestion.

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Fixed typo.

The first 3 commits and the first 3 pipelines at https://git.drupalcode.org/project/experience_builder/-/merge_requests/1495 illustrate this well:

1. commit 1 = create expected subset, but don't update logic ⇒ tests pass, but should've failed
2. commit 2 = update logic ⇒ tests fail, because commit 1 was incomplete: it should've removed more — IOW: a superset is expected, a subset is present, hence test failure
3. commit 3 = create correct expected subset ⇒ tests pass

Since there's been no follow up, going to close out. If still a valid task please re-open.

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

This came up as the daily BSI triage target of the day

This appears to still be valid, but still needs an issue summary update and MR updated to 11.x

I'm all for naming things well. This rename can happen either before or after a stable release.

quietone → closed merge request !9423

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Based on #26

uploaded patch from https://git.drupalcode.org/project/drupal/-/merge_requests/8374/diffs to use in composer

YES, still relevant!

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Since there's been no follow up and as a feature request going to close out. Can always be re-opened

Thanks all!

Adding workaround in Issue Summary:

Until this gets committed in Drupal core, Node view permissions → module enables permissions "View own content" and "View any content" for each content type on permissions page as it was on Drupal 6.

Based on comments in ✨ Access Control with View Own Content / View Own Entity in Core Closed: duplicate , thanks @pameeela and @anybody!