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

Update notifications email should mention the site in the subject

    Details

    • Testing Instructions:
      Hide

      Testing difficulty: Hard (requires fake web service response)

      To test this, the tester would need to invoke sending available updates notification via messaging API and have the admin's messaging set to receive such messages to email.

      It is doable via $CFG->alternativeupdateproviderurl pointing to a local script that returns fake update data. I have this set up at my machine and I already tested it. I'm not sure if putting down all the instructions to prepare such an environment are worth of testing this trivial string change.

      Show
      Testing difficulty: Hard (requires fake web service response) To test this, the tester would need to invoke sending available updates notification via messaging API and have the admin's messaging set to receive such messages to email. It is doable via $CFG->alternativeupdateproviderurl pointing to a local script that returns fake update data. I have this set up at my machine and I already tested it. I'm not sure if putting down all the instructions to prepare such an environment are worth of testing this trivial string change.
    • Affected Branches:
      MOODLE_23_STABLE
    • Fixed Branches:
      MOODLE_23_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-36266-notification-subject

      Description

      If you have more than one site, or even just one site, then the email you get with just "Update notifications" in the subject is less than useful as it doesn't even tell you it's Moodle. This would be better:

      Subject: Moodle updates are available (http://mymoodle.edu)

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    12/Nov/12