Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-41662

"Invalid user" error when non-logged user attempts to access student profile

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.1
    • Fix Version/s: 2.5.3
    • Component/s: Badges
    • Labels:
    • Environment:
      Moodle2.5.1
    • Database:
      MySQL
    • Testing Instructions:
      Hide

      To test, you need badges enabled.

      1. Set forceloginforprofiles and forcelogin to no.
      2. Make sure you can view any user profile page without "Invalid user" error.
      3. Log in as any user.
      4. Make sure you can view your own and other users profile pages without "Invalid user" errors.

      Show
      To test, you need badges enabled. 1. Set forceloginforprofiles and forcelogin to no. 2. Make sure you can view any user profile page without "Invalid user" error. 3. Log in as any user. 4. Make sure you can view your own and other users profile pages without "Invalid user" errors.
    • Affected Branches:
      MOODLE_25_STABLE
    • Fixed Branches:
      MOODLE_25_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-41662_master

      Description

      Similar to MDL-37177. But, show error for every user's profile.(See Picture: not loggedin)
      I am using Moodle2.5.1.
      I only noticed this error after I enabled Badges.
      A student can have Badges displayed right under profile, looks good.(see Picture: loggedin)
      I want the Badges can be displayed for public (without log in account) to view.
      I managed to display via Mozella Open Badges, that is OK enough.
      But the error is annoying.
      Tried to disable Badges, it is too late.
      I can give you an admin account to fix my site.

      Thanks

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  11/Nov/13