Bug - or not?
Roles without "Bypass content access control "-permission is not able to see any list of own unpublished nodes in a views-page-list OR in the list from /admin/content.

My site is a book with 4 levels and different content type on each level.

The only way to find a unpublished node for roles who not have "Bypass content access control "-permission is to write the node id in the URL.
IF the role has all other permissions "on", except the required "Bypass content access control "-permission, it is not able to see any kind of list over there own unpublished nodes..?

( I thought it was a Views-related bug before I did try the list "admin/content" - then I realized that this must be something wrong in the Core.
I have also close down a lot of modules, especially all who handle permissions (node or field-permission) - without finding any kind of conflict or be able to view the list at admin/content?)

Also read this: "Bug or not? Roles without "Bypass content access control "-permission is not able to see unpublished nodes in a views-page-list"

There is a old or similar problem from DB 8: "book.module should correctly handle unpublished content"

It is a lot of bug-reports when unpublished content does'n view in a menu - could it be a permission to see the node-title who is involved?

PLEASE PLEASE advice - how to get unpublished nodes visible (in a list) for the author who created the node-content???

Comments

Göran created an issue. See original summary.

cilefen’s picture

Component: user system » node system
Priority: Major » Normal
Issue tags: -node_access unpublished

Support requests are never major priority.

Version: 7.39 » 7.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.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.