[Building Sakai] Questions about 2.8.1 site email address edit, multiple email aliases

[Gast, Cynthia (cmw6s)]

Following up on my own question... I see what changed and how to address this for our needs at UVa.

I found the "mailarchive" code in
    mailarchive-tool/tool/src/java/org/sakaiproject/mailarchive/tool/MailboxAction.java, doUpdate()

   changed slightly between 2.7.x and 2.8.x, such that now an edit to the site email address creates another email address instead of modifying the existing email address.

We will revert to the 2.7.x behavior because we want a single site email address, that users can change if desired.  Together with this change, we also hide the Site Info Site URL alias to avoid the creation of multiples.

Cheers,
Cindy @ UVa
cmw6s at virginia.edu


________________________________
From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Gast, Cynthia (cmw6s) [cmw6s at eservices.virginia.edu]
Sent: Monday, May 14, 2012 10:32 AM
To: sakai-dev at collab.sakaiproject.org
Subject: [Building Sakai] Questions about 2.8.1 site email address edit, multiple email aliases

Hello:
I've been reviewing changes made between 2.7.x and 2.8.x related to both multiple site email aliases, and the ability to edit/delete them.  SAK-14910 deals with this.

UVa is preparing to roll out Sakai 2.8.1, and we desire the following behavior for the site email address:
    -- Only one site email address, that the user can edit

It seems changes have been made since Sakai 2.7.1, and wondering if this is something we now have to code around to get back to?  I've spent some time on this, not found a way short of code modification, but possible I missed something?

Question 1:  Is this single site email address behavior still possible in 2.8.1, perhaps with a property or combination of properties - or any patches I can apply?


In Sakai 2.7.1, UVa set the wsetup/siteInfo property to hide the Site URL Alias (wsetup.disable.siteAlias=true) , which was creating multiple site email addresses when the user attempted to edit the existing one (with no way to delete them); with this change in place our users could modify the single email address via the Email Archive tool (if desired).  So, that worked for us in 2.7.1.  Does not work now, as my attempt to modify the single existing email address in Email Archive/Options creates an additional site email address instead.  This UI behavior is unexpected; one would expect edit to change the existing string.

BTW, I did try setting the below property (SAK-14910) in our 2.8.1 instance (after also showing the Site Info Site URL field),  and it still produces another site email alias instead of allowing me to edit the one that exists, and did not let me delete newly created additional site email addresses:
    # Enable email alias edit/delete for existing sites
    site-manage.enable.alias.edit=true
... Wondering if anyone else sees this behavior in 2.8.1?  I can enter a JIRA about this, if needed?

Question 2: What is the current 2.8.x, 2.9.x design intent for site email alias?  Multiples per site, with the ability to edit existing, delete existing, add additional?


Thanks for information on this issue, especially if we can conditionally revert to the "single site email address + edit that one to change it" behavior.
Cindy @ UVa
    (fka Cynthia Walters)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120516/690ff78b/attachment.html