Limiting display to public

From http://bugs.sakaiproject.org/jira/browse/SAK-4240:

For legal reasons, we need to be able to turn off the 'make public' checkbox for certain content, for a given type of site.
For example, we want to turn off the ability to make resources or announcements public for class sites, but leave on that ability for syllabus. It shoudl be setup to be controlled by sakai.properties, the default being to give the current behavior where the public checkbox shows up for announcements, syllabus, resources in all types of sites, similar to what was done to disable the ability to make a site of a certain type joinable.

For example,

  1. does the 'display to public' option show up for announcements, syllabus, resources?
    resources.disable.public=false
    announcements.disable.public=false
    syllabus.disable.public=false

and we would set
resources.disable.public=true
announcements.disable.public=true
syllabus.disable.public=false

to disable the public option for resources and announcements.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Apr 10, 2006

    John Leasia says:

    In order to be able to control this on a per site type basis, it's more like pre...

    In order to be able to control this on a per site type basis, it's more like

    prevent.public.announcements.count=1
    prevent.public.annc.1=course

    prevent.public.resources.count=1
    prevent.public.resources.1=course

    prevent.public.syllabus.count=1
    prevent.public.syllabus=course

    and if you wanted to prevent the public checkbox in resources for both project and course, you'd have
    prevent.public.resources.count=2
    prevent.public.resources.1=course
    prevent.public.resources.2=project

  2. Apr 11, 2006

    Stephen Marquard says:

    As discussed on Sakai dev, I think a more appropriate means to implement this wo...

    As discussed on Sakai dev, I think a more appropriate means to implement this would be through permissions, which could then be set in the site template realms, and/or user type realms.

    This introduces a parallel configuration mechanism for sites, which is also less flexible.