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

When a messaging output is set to forced, users should not be able to change that

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.2.3
    • Component/s: Messages
    • Labels:
    • Testing Instructions:
      Hide
      1. Go to Site administration > Plugins > Message outputs > Default message outputs, and set something to forced and something else to disallowed.
      2. As user go to My profile settings > Messaging - note that for the things you set to forced and disallowed now have corresponding text and do not have checkboxes.
      Show
      Go to Site administration > Plugins > Message outputs > Default message outputs, and set something to forced and something else to disallowed. As user go to My profile settings > Messaging - note that for the things you set to forced and disallowed now have corresponding text and do not have checkboxes.
    • Difficulty:
      Easy
    • Affected Branches:
      MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_22_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-32137-master-1

      Description

      Steps to reproduce:

      1. Go to Site administration > Plugins > Message outputs > Default message outputs, and set something to forced.

      2. Go to My profile settings > Messaging - note that for the thing you set to forced, there are two checkboxes, and you appear to be able to un-tick them.

      What was expected. For the forced setting there should be some text like "Is always used" instead of the checkboxes, similar to the "Not permitted" text for things that are Disallowed on Default message outputs.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  14/May/12