Don't use link in message after node save if user doesn't have permissions

Hi all,

I'm reopening the issue because there are valid use cases, for example, in the case of content moderation an anonymous or authenticated user could create some content and then not have permissions to view the content. The above patch works in this situation.

Logically, a link to view unpublished or draft content should not be provided as this will result in an access denied page for the visitor.

Thanks for reading, and hopefully this patch can find it's way into the code base.

Per #30 if this is going to be reopened steps to reproduce fully need to be included in issue summary.

I updated the steps to reproduce the issue according to the updated test and opened a merge request with the fix.

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.

Rebased and slightly simplified the solution. Also expanded the test comment a bit.

Hello,
Tested and verified on drupal 11.
MR applied successfully and its working as expected.

Steps to reproduce

Drupal 11.x installation.
Create content of type test.
Make content type test unpublished by default.
Create a role test_creator and give it access to create content of type test.
Create a user qa with the role test_creator.
Log in as user qa.
Create a node of type test.
After saving, you will see a message about the successful creation of a new node with a link to the new node, but when you go to it you will receive a 403 error.

Check Attachments-

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.

One question on the MR.

Answered, back to RTBC

Thanks for double checking.

Committed/pushed to 11.x and cherry-picked to 11.2.x, thanks!

catch → closed merge request !8877

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