Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-41402

Site Info > Duplicate Site > Provide meaningful email alias (Email Archive)

    Details

    • 19 status:
      Resolved
    • Test Plan:
      Hide

      NOTE: must be tested in an environment where site duplication is enabled

      1. In any site, add the Email Archive tool
      2. Go to Site Info > Duplicate Site
      3. Give the duplicate site a site title and finish the duplication process
      4. Navigate to the duplicated site's Email Archive tool
      5. Verify the site's email alias is not set to the site's UUID (it should generally match the site title you provided for the duplicate site)
      Show
      NOTE: must be tested in an environment where site duplication is enabled In any site, add the Email Archive tool Go to Site Info > Duplicate Site Give the duplicate site a site title and finish the duplication process Navigate to the duplicated site's Email Archive tool Verify the site's email alias is not set to the site's UUID (it should generally match the site title you provided for the duplicate site)

      Description

      Currently when you duplicate a site which contains the Email Archive tool, the resulting duplicated site's Email Archive tool will have the site's email alias set to the UUID of the site. This isn't very intuitive for the user; they may not immediately notice the alias, and when they do they may not understand what the UUID is or why it was set this way.

      The linked PR proposes changing this behaviour to provide more control for the user to determine what the email alias should be. If the originating site contains the Email Archive tool, the user will be presented with a new, dedicated text box to enter their desired email alias.

      If the user does not provide any input into the email alias field, they are presented with an appropriate error message which blocks the duplication process. If the user provides an email alias which is already in use by another site, the user is presented with an appropriate error message which blocks the duplication process. Once the user has provided a valid, unique email alias, the duplication process can be completed normally.

      During testing of this PR, I also noticed that the error messaging was not properly implemented. If any error besides the first one in the code (which checks if a site title was provided) is triggered, the site duplication process proceeds as if no errors were encountered. The linked PR also fixes this bug so that proper error messaging is displayed to the user before the duplication process continues.

      I also fixed a bug where the user supplied site title would not be pre-populated in the form in the event of an error message being displayed (loss of user data).

        Gliffy Diagrams

          Attachments

          1. configureemail.png
            configureemail.png
            17 kB
          2. dupEmailAliasError.png
            dupEmailAliasError.png
            83 kB
          3. dupEmailError.png
            dupEmailError.png
            82 kB
          4. noEmailArchive.png
            noEmailArchive.png
            64 kB
          5. noEmailError.png
            noEmailError.png
            76 kB

            Issue Links

              Activity

                People

                • Assignee:
                  bjones86 Brian Jones
                  Reporter:
                  bjones86 Brian Jones
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code