[Building Sakai] Disallow course join/unjoin in 2.7

Bryan Bakotich bakotibj at plu.edu
Thu Jan 13 14:09:21 PST 2011


Sorry about that last reply. Hit the wrong button.

Thanks for the quick response. You are correct that the property works for
making sites not joinable. I was looking at an old site that was public
before we added that saka property.

I will take a look at the revision you mentioned and see if I can get the
unjoinable part working. Thanks again.

-Bryan

On Thu, Jan 13, 2011 at 2:07 PM, Bryan Bakotich <bakotibj at plu.edu> wrote:

> Matthew,
>
> Thanks for the
>
> On Thu, Jan 13, 2011 at 12:42 PM, Matthew Jones <jonespm at umich.edu> wrote:
>
>> We're on 2.7 and I'm *pretty* sure that the joinable block works because
>> we are using that same setting and it does make it so course sites are not
>> joinable.
>>
>> [image: Picture 79.png]
>> As far as the unjoinable, we don't have that set there. My 5 minute guess
>> is that this revision:
>> *
>> http://source.sakaiproject.org/viewsvn/site-manage/trunk/site-manage-tool/tool/src/webapp/vm/membership/chef_membership.vm?r1=58447&r2=58448&
>> *as part of SAK-15142 <https://jira.sakaiproject.org/browse/SAK-15142> broke
>> that functionality. (Looks like that piece wasn't merged till 2.6.3/2.7.0)
>>
>> It looks like the call to
>>   189
>>  #set($siteType=$site.Type)
>> was moved from above to below the call that actually needs to use it so
>> it's probably not set and doesn't work?
>>   176
>>  #if($disableUnjoinSelection || ($!siteType &&
>> $!disableUnjoinSiteTypes.contains($!siteType)))
>> -Matthew
>>
>> On Thu, Jan 13, 2011 at 3:11 PM, Bryan Bakotich <bakotibj at plu.edu> wrote:
>>
>>>  Hi all,
>>>
>>> In Sakai 2.6 we have the following properties in place so that users
>>> can't Join or Unjoin a course site:
>>> wsetup.disable.joinable.count=1
>>> wsetup.disable.joinable.1=course
>>> wsetup.disable.unjoin.count=1
>>> wsetup.disable.unjoin.1=course
>>>
>>> With those same sakai properties in Sakai 2.7 users are able to Join and
>>> Unjoin course sites. Is there a new way to handle this use case in 2.7?
>>>
>>> -Bryan
>>>
>>> --
>>> Bryan Bakotich
>>> Open Source Implementation Specialist
>>> Digital Media Center, Information & Technology Services
>>> Pacific Lutheran University
>>> Tacoma, WA 98447-0013
>>> Phone: 253-536-5021
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>
>>
>
>
> --
> Bryan Bakotich
> Open Source Implementation Specialist
> Digital Media Center, Information & Technology Services
> Pacific Lutheran University
> Tacoma, WA 98447-0013
> Phone: 253-536-5021
>



-- 
Bryan Bakotich
Open Source Implementation Specialist
Digital Media Center, Information & Technology Services
Pacific Lutheran University
Tacoma, WA 98447-0013
Phone: 253-536-5021
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110113/e68f772b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 20409 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110113/e68f772b/attachment.png 


More information about the sakai-dev mailing list