[Deploying Sakai] IsCourseSite

Zhen Qian zqian at umich.edu
Sat Aug 29 21:55:39 PDT 2009



I have also seen those warnings in my log file, but I haven't touched the
mercury tool. 

After debugging, I found the error was generated from permission check in
order to show the "New Site" link in Admin Sites tool. For example, it is
the following code within AdminSitesAction.buildListContext(): 

 if (SiteService.allowAddSite(""))
 {
 bar.add(new MenuEntry(rb.getString("sitact.newsit"), "doNew"));
 } 

The related implementation inside BaseSiteService.java file is as follows:


 public boolean allowAddSite(String id)
 {
 // check security (throws if not permitted)
 if (id != null &
 }
 else if (id != null &
 }
 else
 {
 return unlockCheck(SECURE_ADD_SITE, siteReference(id));
 }
 } 

Seems like here empty String id should first be turned to null and hence
neither isUserSite() nor isCourseSite() would be called at all. 

Or the AdminSitesAction.java should use SiteService.allowAddSite(null)
instead. 

I have created SAK-16890 for this and fixed in r66160 from within Admin
Sites
tool. Please test. 

Thanks, 

- Zhen 

On Sun, 30 Aug 2009 00:08:19 -0400, Paul Gibbs  wrote:  It sounds like I'm
in good shape then. I guess I'll just ignore it unless I find that other
issues are related to it. I didn't delete the mercury portal--just the
site. Glad to hear you do the same thing on new installs. Much appreciated!

Paul

-------------------------
 CC: demonner at umich.edu; production at collab.sakaiproject.org
From: steve.swinsburg at gmail.com
To: pgibbsjr at hotmail.com
Subject: Re: [Deploying Sakai] IsCourseSite
Date: Sun, 30 Aug 2009 09:22:01 +1000

You can delete the mercury site with no side effects. It's the first thing
I do in a new install.  If, however, you deleted the mercury portal (which
is a different thing altogether and would require you to delete code) then
you might be in trouble. I'm not sure of the link between the mercury
portal and the SkinnableCharonPortal which is what's in use now though. 
I'd be looking elsewhere for the cause of the error. That
said, its not an
error, just a warning.  cheers, Steve

  On 30/08/2009, at 7:26 AM, Paul Gibbs wrote: 
    Uh-oh. :)    I have the mercury site disabled in
sakai.properties--would that mean that the error is coming from some other
non-existent site? Or would there be calls to mercury anyhow at some
points, even though I've disabled it? If I should be recreating mercury as
a step toward troubleshooting this issue, Is there any way to recreate the
site without manually keying in records into the database?   Paul     FROM:
Sean DeMonner [mailto:demonner at umich.edu [1]] 
SENT: Saturday, August 29, 2009 5:10 PM
TO: Paul Gibbs
CC: production at collab.sakaiproject.org [2]
SUBJECT: Re: [Deploying Sakai] IsCourseSite     There is a portal
interface called mercury (like /portal or /xlogin) that is used mostly by
developers for testing and configuration purposes. I don't know if deleting
it would could problems (I didn't know there was a mercury site), but all
things being equal I'd probably just
leave it alone :^)      SMD.          
    On Aug 29, 2009, at 4:24 PM, Paul Gibbs wrote:  

  (Sorry for what could be a double-post if you've already received this
before. In Nabble, it looked like my previous message on this topic got
appended to the Evaluations System discussion just recently concluded.)  
Whenever I open the Sites tool or the Worksite Setup tool, I get this error
in catalina.out:   2009-08-24 20:56:50,503 WARN
http-localhost%2F127.0.0.1-8080-Processor12
org.sakaiproject.site.impl.BaseSiteService - isCourseSite(): no site with
id:   No error message appear in the browser, and things appear to function
normally. Has anyone seen that before? I think the only site I deleted was
the "mercury" siteshould I not have done that?   Paul Gibbs CBTS /
Lansdale, Pennsylvania   _______________________________________________  
production mailing list   production at collab.sakaiproject.org [3]  
http://collab.sakaiproject.org/mailman/listinfo/production [4]       TO
UNSUBSCRIBE:
send email to production-unsubscribe at collab.sakaiproject.org
[5] with a subject of "unsubscribe"       
SMD.           ========================================================== 
 Sean DeMonner, IT Senior Project Manager, CTools Implementation Group  
Digital Media Commons @ The Duderstadt Center, U-M  (734) 615-9765   Pub
Key 24DD6B09      

      _______________________________________________
production mailing list
production at collab.sakaiproject.org [6]
http://collab.sakaiproject.org/mailman/listinfo/production [7]

TO UNSUBSCRIBE: send email to
production-unsubscribe at collab.sakaiproject.org [8] with a subject of
"unsubscribe"     

-------------------------
 Hotmail(R) is up to 70% faster. Now good news travels really fast. Try it
now. [9] 

 

Links:
------
[1] mailto:demonner at umich.edu
[2] mailto:production at collab.sakaiproject.org
[3] mailto:production at collab.sakaiproject.org
[4] http://collab.sakaiproject.org/mailman/listinfo/production
[5]
mailto:production-unsubscribe at collab.sakaiproject.org
[6] mailto:production at collab.sakaiproject.org
[7] http://collab.sakaiproject.org/mailman/listinfo/production
[8] mailto:production-unsubscribe at collab.sakaiproject.org
[9]
http://windowslive.com/online/hotmail?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_faster:082009
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20090830/154aef5c/attachment.html 


More information about the production mailing list