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.
Thanks
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.
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@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/ ]
Give the editor role the "Use the site in maintenance mode" permission.
On Aug 29, 2014, at 11:46 AM, Drupal drupal@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@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/ ]
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@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@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@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/ ]
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-htacc...
It has the following advantages:
1. 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. 2. 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@gmail.com mailto:killshot91@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@afan.net mailto:drupal@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@bellsouth.net mailto:nan_wich@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/ ]
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-htacc...
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@gmail.com mailto:killshot91@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@afan.net mailto:drupal@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@bellsouth.net mailto:nan_wich@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/ ]
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@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-htacc...
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@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@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@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/ ]
You're right. I totally forgot it was added in D7, which is why I probably never opened the issue. The minds going in my old age!
Jamie Holly http://hollyit.net
On 8/29/2014 4:47 PM, Steve Edwards wrote:
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@earthlink.net mailto:hovercrafter@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-htacc...
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@gmail.com mailto:killshot91@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@afan.net mailto:drupal@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@bellsouth.net mailto:nan_wich@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/ ]
Two tricks I have done in the past. First is a very simple one. Give them the administer site configuration permission. That's the quick and easy, but in my experience, it has lead to confusion, especially among users new to Drupal setting up content (they now got a bunch more menus and can get overwhelmed)
The second is a little more involved, requiring some coding that can be done in your settings.php, but is still only about a 5-10 minute hack/fix
- First, create a special "login" link using a URL variable or even a custom path that you can check with $_GET['q']. Check if that condition is met in your settings.php, then set a custom cookie and redirect back to the front page.
- Add another check in your settings.php, checking for that cookie. If it's set, then set $conf['site_offline'] = 0;
There is one final option, that is easier, but only applies to if this is a new site that has never had regular users check in. Simple check for the session cookie in settings.php, then set the $conf['site_offline'] to 0 if it exists. This works since users can still hit the login screen when the site is in offline mode (in case the admin needs to get in) and remain logged in when the site comes up.
Jamie Holly http://hollyit.net
On 8/29/2014 2:32 PM, Drupal wrote:
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.
Thanks
-
Drupal -
Jamie Holly -
Nancy Wichmann -
Shai Gluskin -
Steve Edwards