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

badges capabilities include incorrect risks, levels and archetypes

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.5.1
    • Component/s: Badges
    • Labels:
    • Testing Instructions:
      Hide

      note: this depends on major version bump to update core capabilities table, test in fresh new install

      1/ perform install
      2/ review all badges capabilities in following roles: coursecreator (no caps), user (defaults to view and earn), manager and editing teacher (configure everything on course level)
      3/ try badge capabilities overriding at course level

      Show
      note: this depends on major version bump to update core capabilities table, test in fresh new install 1/ perform install 2/ review all badges capabilities in following roles: coursecreator (no caps), user (defaults to view and earn), manager and editing teacher (configure everything on course level) 3/ try badge capabilities overriding at course level
    • Affected Branches:
      MOODLE_25_STABLE
    • Fixed Branches:
      MOODLE_25_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      w26_MDL-40289_m26_badgescaps

      Description

      Configuration risk is intended for site level settings that may pose security risks such as paths to executables.

      I believe the badges should not have this because they are allowed for teachers by defaults.

      The current rule is that only admins may have capabilities with configuration risks.

      The level of each capability is used for overriding, it must be the lowest level where you can override the capability...

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  8/Jul/13