Hello,
I have installed the module but it doesn't seem to work. It doesn't redirect to user/login and it just says the defaul tbrowser message. Do I have to make some setting, or a rewrite rule? My host uses lighttpd

Comments

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Title: I can't make the module to work » How to use this module
Version: 7.x-1.3 » 7.x-1.x-dev
Component: Code » Documentation
Priority: Normal » Major

this should be part of readme imho:
(i had to "read the source, luke"...)

* go to admin/config/system/site-information
* at "error pages / 403 page" enter this: r4032login
* fill the other settings below as needed

the above thing should probably be done by a hook_form_alter...
setting to doc issue for now

robloach’s picture

robloach
he/him
commented
Category: bug » task

This is in the .install though, which should automatically set that variable....

/**
 * Implements hook_enable().
 */
function r4032login_enable() {
  variable_set('site_403', 'r4032login');
}

/**
 * Implements hook_disable().
 */
function r4032login_disable() {
  variable_del('site_403');
}

It does deserve to be in the documentation somewhere though.

lotyrin’s picture

lotyrin commented

Is there any reason to have r4032login installed without the 403 page set to it?

Just brainstorming if it would be appropriate to display a warning to the user in that case. (perhaps on the configuration page)

facal’s picture

facal commented

Totally agree with axel.rutz, those three bullets must be in the readme!

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Fixed

The automated steps in the installer and simple text in http://drupalcode.org/project/r4032login.git/blob/refs/heads/7.x-1.x:/RE... make this seem fixed to me.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.