[Building Sakai] [Using Sakai] site creation authorizer email logic

Steve Swinsburg steve.swinsburg at gmail.com
Thu Oct 25 17:23:31 PDT 2012


I didn't think you could select a term that wasn't current, therefore you couldn't even get to that step.

At least in my local instance, switching the IS_CURRENT flag to 0 for a few terms means that term no longer appears in the drop down.

cheers,
Steve


On 26/10/2012, at 10:56 AM, John Bush <john.bush at rsmart.com> wrote:

> SiteAction only sends the authorizer email when the term is current.
> Functionally, can someone explain this, why don't we want to notify
> people if the term is in the future?
> 
> 			if (!isFutureTerm) {
> 				for (Iterator iInstructors = authorizerList.iterator();
> iInstructors.hasNext();)
> 				{
> 					String instructorId = (String) iInstructors.next();
> 					if (requireAuthorizer)
> 					{
> 						// 1. email to course site authorizer
> 						boolean result =
> userNotificationProvider.notifyCourseRequestAuthorizer(instructorId,
> requestEmail, term != null? term.getTitle():"", requestSectionInfo,
> title, id, additional, productionSiteName);
> 						if (!result)
> 						{
> 							// append authorizer who doesn't received an notification
> 							authorizerNotNotified += instructorId + ", ";
> 						}
> 						else
> 						{
> 							// append authorizer who does received an notification
> 							authorizerNotified += instructorId + ", ";
> 						}
> 						
> 					}
> 				}
> 			}
> 
> -- 
> John Bush
> 602-490-0470
> _______________________________________________
> sakai-user mailing list
> sakai-user at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> 
> TO UNSUBSCRIBE: send email to sakai-user-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"



More information about the sakai-dev mailing list