Moodle

forcelogin not respected when autologinguests enabled

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 1.8.2
  • Fix Version/s: None
  • Component/s: General
  • Labels:
    None
  • Affected Branches:
    MOODLE_18_STABLE

Description

Scenario: I want to force users to log in before doing anything on site. However, I'd also like visitors to directly access some guest-enabled courses without having to sign in as a guest. Under Moodle 1.6 this was possible and indeed this was how it worked on our Moodle.

However, under Moodle 1.8.2+ when torcelogin and autologinguests are both enabled the regular Moodle front page displays to any user who has not yet logged in. It seems that they are automatically logged in as a guest and forcelogin is bypassed.

There is therefore a bit of a conflict between these two settings that maybe needs ironing out. Maybe forcelogin should trump autologinguests, or maybe autologinguests can be granularised so that it can be applied to course contexts (and can therefore be removed from the front-page course)?

A similar report to this: http://moodle.org/mod/forum/discuss.php?d=74901

Activity

Hide
Roger Emery added a comment -

We have the same problem here and can confirm the conflict.

We have previously and would like to continue to have both forcelogin and autologinguests enabled

Show
Roger Emery added a comment - We have the same problem here and can confirm the conflict. We have previously and would like to continue to have both forcelogin and autologinguests enabled
Hide
Michael de Raadt added a comment -

Thanks for reporting this issue.

We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported.

If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

Michael d;

lqjjLKA0p6

Show
Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.1 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d; lqjjLKA0p6
Hide
Michael de Raadt added a comment -

I'm closing this issue as it has become inactive and does not appear to affect a current supported version. If you are encountering this problem or one similar, please launch a new issue.

Show
Michael de Raadt added a comment - I'm closing this issue as it has become inactive and does not appear to affect a current supported version. If you are encountering this problem or one similar, please launch a new issue.

Dates

  • Created:
    Updated:
    Resolved: