Access our own non published nodes [#70421]

Hi,
So it seems there's a problem with the... node system? I mean, someone creates a node, but he does not want to publish it yet. So he unchecks "published". And he submits the node. Then the node is not in moderation queue, and not published.
With a module such as workspace, he can see his node in a list... he can even edit it by typing the edit url in the browser, such as http://www.example.org/node/33/edit, for the node 33... But if he tries to "view" his node, to check how it looks, he cannot, he has a forbidden access message...

To be able to view not published nodes he needs to have node management rights in the taxonomy system. Not very convenient for a simple user...

This is a big issue for me.

Any workaround?

Thanks

Comments

Comment #1

killes@www.drop.org commented 23 June 2006 at 08:49

Priority:	Critical	» Normal
Status:	Active	» Closed (works as designed)

That works as designed. You need "administer nodes" to access unpublished nodes. If you can set nodes to be unpublished then you already have that permission.

Comment #2

Julien PHAM commented 23 June 2006 at 09:38

Status:

Closed (works as designed)

» Active

I use the workflow module so a node can have some states such as "composing", in moderation queue, then published. This is important for me, as sometimes a user would like to start composing its article now, and continue it later... very important in a CMS environment... So it is important that the user can access his own node.

I think the node system should be changed a bit to allow at least viewing his own unpublished nodes, of course not other's.

And giving him node management allow him to edit "all" nodes even others so I don't want that...

But what is strange... you say it is by design, that you cannot view unpublished nodes, but you can still edit it, if you use the whole link.

http://www.example.org/node/33/edit is accessible even without node management rights, but...

http://www.example.org/node/33 is not...

Are you sure it is by design?

I put this as active again so you can read this message easily, but if it is really by design then just put it back in design state...

Comment #3

Egon Bianchet commented 23 June 2006 at 13:01

It could be a feature request for 4.8 ... In the meantime you can work around this using the views module.

Comment #4

magico commented 18 September 2006 at 20:08

Title:	Impossible to access our own non published nodes	» Access our own non published nodes
Version:	4.7.2	» x.y.z
Category:	bug	» feature

Following #1 it's "by design"; but following #3 it's importante that instead of ?q=admin/content/node deny access to the user, it would apply an automatic filter to show only the login user posts.

Comment #5

Egon Bianchet commented 19 September 2006 at 07:39

Maybe a "my content" page next to "my account"

Comment #6

eafarris commented 19 September 2006 at 14:40

There's an unpublished.module in my sandbox:

http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/eafarris/unpu...

Because a site I was working on required this functionality. It adds a "my unpublished content" item to the navigation menu. It's for Drupal 4.6, so it might need updating.