We've seen this issue when duplicating a site from another site. Then trying to add the calendar, chat, and forum tool to the newly duplicated site. Checking the database's sakai_site_tool table, the duplicated site does contain the registrations for the synoptic tools, but they weren't being displayed in the UI

We found that the original site, for some unknown reason (perhaps during an upgrade from 10.7 to 11.4), it's "overview" page did not contain the property "is_home_page". After adding that property to the original 'template' site's overview page, new duplicates were then able to display the synoptic tools.

Adding the "is_home_page" property to broken duplicates (sites created when the original's "overview" did not have the is_home_page) fixed those sites as well.

So this is a little bit of a mess. SiteAction follows these rules for finding the list of allowed synoptic tools in a site, once it has found some synoptic tools it stops looking anywhere else.

• First lookup configuration from wsetup.home.toolids.{siteType} and if not set then wsetup.home.toolids.

• Second see if we're creating a site from a template and if so use the synoptic tools on the template.

• Third attempt to load the template for this site and look what synoptic tools are on it's home page. Site ID !worksite.{siteType} or fallback to !worksite

• Fourth If we didn't find any configuration anywhere else then check the tools are installed and uses: sakai.iframe.site, sakai.summary.calendar, sakai.synoptic.announcement, sakai.synoptic.chat, sakai.synoptic.messagecenter

In 2.9.x the configuration was defined by default to it never looked in the template sites or used the hard coded values, in 10 there isn't any default so it ends up using the values from !worksite.

The cleanest solution would seem to be to update !gateway to add the extra synoptic tools to it's home page, this way we don't need to add default config and the !gateway/template can continue to work. The problem is that doing the upgrade SQL for this isn't easy as if someone has edited !gateway we might be overwriting their specific configuration.

If we add a default to the config to the server configuration lookups then all the other code never gets run unless we allow someone to explicitly disable the lookups.

This was introduced when commented out the default.sakai.properties values:

wsetup.home.toolids.1=sakai.iframe.site
wsetup.home.toolids.2=sakai.synoptic.announcement
wsetup.home.toolids.3=sakai.summary.calendar
wsetup.home.toolids.4=sakai.synoptic.messagecenter
wsetup.home.toolids.5=sakai.synoptic.chat

On a fresh installation this seems to be because the template site (!worksite) that it ends up looking at doesn't have these synoptic tools added to the it's Home page.

This code is in: org.sakaiproject.site.tool.SiteAction#getHomeToolIds

On 2.9.x when I add the schedule tool the synoptic schedule is added.