[support] Multiple roles access a site while in maintenance mode

[Steve Edwards]

Jamie,

I'm not sure I understand your issue. I read it, and you talk about the "administer site configuration" option, but the one I mentioned below was  "use the site in maintenance mode" permission.  Doesn't that one do what you want?

Steve

On Aug 29, 2014, at 1:36 PM, Jamie Holly <hovercrafter at earthlink.net> wrote:

> I wasn't the original OP :p
> 
> But this thread did shake the cobwebs off of an idea I had floating around in my mind for a few years and kept forgetting to open an issue about - creating a permission for "access offline site" and either having Drupal check for just that or (even better) check for that permission, or the administer site configuration one. Very simple fix, to a problem that I feel is nightmare at times from a usability stand point, especially when we're trying to introduce clients to the world of Drupal.
> 
> Here's the issue:
> 
> https://www.drupal.org/node/2330045
> Jamie Holly
> http://hollyit.net
> On 8/29/2014 4:01 PM, Shai Gluskin wrote:
>> Jamie,
>> 
>> I know you liked Steve's answer. But I thought I'd share one more solution I have come to use recently and love.
>> 
>> This is a non-Drupal solution that requires an Apache server: use .htpasswd and .htaccess to restrict access to the Drupal root directory.
>> 
>> If you don't know how to do this, here is a simple tutorial:
>> https://www.addedbytes.com/blog/code/password-protect-a-directory-with-htaccess/
>> 
>> It has the following advantages:
>> The need is temporary; will you remember to remove "Access site in maintenance mode" permission after site goes live? Since the use of maintenance mode is different after the site goes live than before, you may not want to have those folks using the site in maintenance mode. In fact, you probably won't want them to have that permission. With the .htpasswd approach, you can't forget to turn it off because the public can't see the site at all with .htpasswd turned on.
>> The Drupal warning messages about the site being on offline mode can be annoying or even problematic. By problematic I mean that the folks who are reviewing the site as part of a final review can include people who are focusing on layout/page design. The appearance of that site offline message can make it harder for those checkers to evaluate whether the graphic design is in place as necessary.
>> Shai
>> 
>> On 08/29/2014 03:11 PM, Drupal wrote:
>>> That’s why am I talking about! :D
>>> I couldn’t see it nor anybody mentioned it when I was goggling it…
>>> 
>>> Thanks Steve!
>>> 
>>> 
>>> On Aug 29, 2014, at 1:56 PM, Steve Edwards <killshot91 at gmail.com> wrote:
>>> 
>>>> Give the editor role the "Use the site in maintenance mode" permission.
>>>> 
>>>> On Aug 29, 2014, at 11:46 AM, Drupal <drupal at afan.net> wrote:
>>>> 
>>>>> That’s not what am I talking about.
>>>>> I’m admin and I have access to the website while in Maintenance mode. And nobody else. I created an “editor” role for a guy to final content checking and testing and spelling fixes. How to give him the access to the website?
>>>>> 
>>>>> 
>>>>> On Aug 29, 2014, at 1:41 PM, Nancy Wichmann <nan_wich at bellsouth.net> wrote:
>>>>> 
>>>>>> They just need to know to stick "/user" on the end of the URL and they can log in as normal.
>>>>>> 
>>>>>> 
>>>>>> Hi,
>>>>>> The site I’m working on is pretty much done but I still can’t make it public until website editors do some content changes and spelling corrections. I don’t want to give them the admin access so I was wondering how to make their role (editor) bypass the maintenance mode - without any changes in the code or me writing a new module. 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> [ Drupal support list | http://lists.drupal.org/ ]
>>>>> 
>>>>> -- 
>>>>> [ Drupal support list | http://lists.drupal.org/ ]
>>>> 
>>>> -- 
>>>> [ Drupal support list | http://lists.drupal.org/ ]
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> -- 
> [ Drupal support list | http://lists.drupal.org/ ]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20140829/76e8d799/attachment-0001.html