Publish Permissions

[mrjasongorman]

Is there a way to lock down (via role) the ability to update / publish a page live?

My client needs some people to be able to edit a page, but the page changes must be reviewed by another member of staff who have access to push the update live.

Is this possible?

Thanks

[LostKobrakai]

There's currently no drafting feature in ProcessWire. A page is therefore either live or not and there's always only a single version of a page to save to. 

[Martijn Geerts]

It is possible I guess...

If you hook to page::loaded, you can get the status and cache it to a variable.

Then before pages::save you could check the status and role, when the status has changed, you could re-assign the cached status.

[mrjasongorman]

Thanks for responding so quick guys, I've found this discussion https://processwire.com/talk/topic/954-hide-publish-button/ but not sure it's exactly the same.

So it is possible to store the "page" (updated fields) in a state that's not live?

I'm not too clued up with exactly how processwire works, if i say anything stupid i apologise 

[LostKobrakai]

This only works as long as a page isn't live. As soon as it's published all changes to it will be published, too. A page does currently always have a single state in the database to which you save your changes. There's no second set of "draft" values.

[mrjasongorman]

Ah i see :/

Taking the version control module @teppo created, which adds multiple versions of fields, it may not be too hard to tweak this to create a "Draft" stage.

Would you guys agree?? it may not be that simple, but in theory it would work?