[drupal-devel] [feature] A patch to allow users to easily work on unpublished content.

mcd drupal-devel at drupal.org
Thu Jan 27 21:45:07 UTC 2005

 Project:      Drupal
 Version:      cvs
 Component:    user system
 Category:     feature requests
 Priority:     normal
 Assigned to:  gordon
 Reported by:  gordon
 Updated by:   mcd
 Status:       patch

I'd put the tab under Recent Posts, which already has a similar tab for
My Recent Posts.


Previous comments:

September 6, 2004 - 20:12 : gordon

Attachment: http://drupal.org/files/issues/user_9.patch (1.84 KB)

This is a patch that I have wanted for a while, and esp. with the added
menu tabs it has come together very well.

What this patch does is add an additional tab to the "my account" page
called unpublished. This tab displays exactly like the front page, but
only displays unpublished content that belongs to the user. This allows
the user to work on content over multiple editing sessions and then be
able to come back and easily find the content. that they were working
on, and resume editing.

I find this useful if your are content is over multiple pages and you
want to add the links.

One thing that i would like to add is being able to not only seeing
your unpublished content but the content of other users that give you
permission to review/collaborate on before it is published. Maybe it
would be handy to be able to have multiple authors on a single node.


September 6, 2004 - 20:23 : killes at www.drop.org

I think that this could well be implemented as a "personal workflow"
module. There are endless possibilities with the new access controll


September 6, 2004 - 20:49 : gordon

Yes the possiblities are endless. I would like to see something more,
but at this stage I think this would really help alot of people, I know
that it has helped for me.


September 13, 2004 - 05:55 : moshe weitzman

seems useful. consider making it a contrib module so folks can easily
check it out, and we don't wait for core in order to use it.


September 14, 2004 - 08:11 : gordon

I do feel that this should be something that is in core. In its present
form, creating a module for it would be feely easy, but there is not
very much functionality in it, so it would be a very small module.

But turning it into a module maybe a good idea, if the idea is going to
be expanded further, I would maybe like to see colaboration on a
document between multiple users before it gets published. maybe
something like an invitation system, that then users the node
permisions to allow other users to access and edit your document before
it is published.


November 15, 2004 - 11:22 : elias1884

as far as I am concerned, this strongly belongs to core. for me this
improvement goes hand in hand with http://drupal.org/node/7939 as it
gives the unexperienced user a way to verify if their node really got
submitted, since they might get confused by the "access denied" message
they retrieve when published is turnd of in default workflow.


November 15, 2004 - 11:33 : moshe weitzman

It seems like this functionality is part of the workspace.module in
Contrib. The UI may be different, but the idea persists. Perhaps folks
could keep on improving workspace ....


November 17, 2004 - 22:23 : tostinni

A little correction of the patch due to new node_acces function :
Replace : 


And now unpublished tab will really appear ;)


November 17, 2004 - 22:40 : gordon

Attachment: http://drupal.org/files/issues/user_11.patch (1.84 KB)

Here is a fixed version of the patch.


November 17, 2004 - 22:57 : jvandyk

This seems to duplicate the functionality of the workspace module.


November 18, 2004 - 03:32 : Dries

The tabs on the user page represents actions one can perform on a user:
one can 'view', 'edit', 'track' or 'contact' a user.  Adding a tab
called 'unpublished' is a bad idea.


November 18, 2004 - 06:38 : gordon

Attachment: http://drupal.org/files/issues/user_12.patch (1.78 KB)

Yes looking at this, I agree with you. The way that this menu has
developed it is no longer appropiate to add this tab here. My next
option was to put it under the either the view or edit tabs. I am
leaning more towards the view than the edit.
I think that it is a view function because you are not actually editing
anything. Also this is an operation that a user can only use on thier
user, so it is a private function. What do you think?
I also did a bit more investigation of the patch, and had to make some
more changes as the call  to the node_access() has changed, and the
information that I need is no longer accessible that way.

View: http://drupal.org/node/10611
Edit: http://drupal.org/project/comments/add/10611

More information about the drupal-devel mailing list