New content remains unpublished for users with Publish permissions

Hi Rik

Would it be possible to provide a configuration option for this? I feel it should be at least a selectable option, as it adds 2 extra steps to the process.

In my own case we have 5 users in total at present. I as user 1 create most of the information, if i make a mistake, it is unlikely anyone would even know, especially as the moment it goes to moderation I will immediately make the next 2 clicks to get it published. So sending to moderation, doesn't add a safety net of a Moderator, the only way that could happen is to take away publication rights, which opens a larger can or worms :)

Basically unless having the cofiguration this way if to enable another module to perform in a certain manner, it really achieves nothing

In Revision Moderation If you had Publish Rights to the content you are creating, it would immediately go to published status

regards
John

Hi Rik,

You just hit on a concept for revisioning that I had not considered, and that is using it for "Drafts", possibly it didnt come to mind as I have been looking at the module Save As Draft, and considered Revisioning a different function. Also I had only considered Save as Draft as a prior to publication function, and not for revisions. But now thinking on it, the function could sit in the process somewhere, though i would say NOT as pending, it needs its own identification. Draft, otherwise if it is sitting in the pending file, it would also be in a Moderators Pending file, and they may moderate/publish it ? I may have missed something though, so please enlighten me

John

Hi Rik

I will check it out later today when its available, but it does sound as though it will work.

The problem we have is that their are many organisations out their with various structures. Many have highly organised structures, developed through experience over umpteeen years, and requirements to meet regulations/standards, which tend to send you in one direction, and then their are the rest, where it has come from necessity, and thrown together one piece at a time, to form a haphazzard mess, which probably need a good overhaul, maybe Revisioning will provide that impetus fo rthem to fix things :)

John

Hi Rik,

Just downloaded the latest version, auto-publish works fine. However the block has now dissapeared :)

John

Hi Rik

The cause of the block dissapearing is due to

 $nodes = get_nodes('update', TRUE, 'vid ASC');

its doesnt like the 'vid ASC'

removing returns the block to visible

Hi Rik

Thought i would investigate further and found this reference on the web

get_nodes  ( $  op,  
  $  pending = FALSE,  
  $  order_by = 'timestamp DESC',  
  $  max = 1000   
 ) 

So thought to try Timestamp, and again the block dissapears,

Hi Rik

good point forgot Module Grants , will try that

John

That fixed it:)

This does bring us back to teh old chesnut of displaying nodes of content types not needing needing moderation. My top 5 are now unpublished nodes from last year which i use as reference :) but thtas another story :)

John