We have several people that post to our website. When I pull everything down to our dev server so that we can do changes of any kind, I send out a message to all posters to NOT post items to the site, or they will get overwritten.

Almost every time, somebody (or nobody) has paid attention to this request.

I know I could go into User roles and flip switches, but that could get time consuming. I'd prefer if there was a way to toggle one switch that prevents any posts to the website. They could log in, but maybe they get a message telling them the ability to post is temporarily halted. Then when we're done, and I push the dev site to the production site, I can turn it back on, and avoid dealing with deleted posts (or having to post items in both locations.)

Thank you!

Comments

mmjvb’s picture

That is what maintenance mode is all about.

turpentyne’s picture

Maintenance mode turns the public site off, displaying a message that the site is down for maintenance, correct? That's not what I want. I want the site to stay active, but staff to not be able to post.

sprite’s picture

There are modules just for group content workflow, with better approaches ...

Evaluate the following modules:

https://www.drupal.org/project/workflow

https://www.drupal.org/project/content_approval

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

pixelsweatshop’s picture

sprite’s picture

Maybe the Drupal foundation should trademark ....

"There's a module for that"

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

mmjvb’s picture

looks like a much more professional approach than maintenance mode. Too bad it didn't make it into D8.

Found no distributions containing it, surprisingly enough.

pixelsweatshop’s picture

With configuration management in D8, I don't really see a need for it.

turpentyne’s picture

Tell me a little more about configuration management? Would that solve this problem? Might help with suggesting to our team that we upgrade to D8

pixelsweatshop’s picture

Yes, this would solve your problem. In Drupal 8 configuration is now stored in yaml files instead of the database. Therefore you can develop new featured in a development site, then export the new config to the staging for testing. then move it to live. All with little to no down time. Users can also keep adding content, updating their user accounts and using the site while this is all going on.

See
https://chromatichq.com/blog/drupal-8-configuration-management-solving-c...
https://www.lullabot.com/articles/configuration-management-in-drupal-8-t...