Telligent Event Calendar v1.6 is only compatible with Telligent Enterprise 2.6 and Telligent Community 5.6. In the same respect, versions of the Telligent Event Calendar prior to 1.6 are not compatible with Telligent Community 5.6 or Telligent Enterprise 2.6. If you wish to take advantage of the features available in Telligent Event Calendar 1.6 then you must upgrade to to either Telligent Enterprise 2.6 or Telligent Community 5.6.
This installation guide only applies to v1.6 of the Telligent Event Calendar. For older versions please contact us.
***It is recommended, that you backup. your entire web directory before performing any installs.
<PageHeader inherit="true"> <Markup> <![CDATA[ <meta http-equiv="X-UA-Compatible" content="IE=7" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <link rel="shortcut icon" type="image/ico" href="~/themes/fiji/favicon.ico" /> <link type="text/css" rel="stylesheet" href="~/themes/fiji/css/screen.css" media="screen,print" /> <link type="text/css" rel="stylesheet" href="~/themes/fiji/css/calendar.css" media="screen,print" /> ]]> </Markup></PageHeader>
***It is recommended that you do a full database backup before installing SQL.
The installation package contains a folder called /SqlScripts which contains the necessary SQL files. The SQL files are pre-pended with a version number. This version should match the assembly version of Telligent.Services.Calendar.dll in /Web/bin. Always make sure these values match before applying.
In order to support navigation for the Telligent Event Calendar you need to replace the standard Group Application Navigation widget on every page necessary with the Event Calendar- Group Application Navigation widget. This adds the calendar tab to the standard tabs.
In order for search to function, you must install the content handlers. To do so, in the directory you installed the Telligent Job Scheduler, locate the tasks.config file and edit it. Find the CommunityServer.Search.Tasks.SearchIndexingContentHandlerTask and after the default handlers add the calendar and event content handlers as illustrated below, where XX is the next sequential number.
<job schedule="0 */2 * * * ? *" type="CommunityServer.Search.Tasks.SearchIndexingContentHandlerTask, CommunityServer.Search"> <settings> <add key="documentsPerRun" value="100" /> ...(Default Content Handlers)... <add key="handler-XX" value="Telligent.Services.Calendar.Search.CalendarContentHandler, Telligent.Services.Calendar" /> <add key="handler-XX" value="Telligent.Services.Calendar.Search.CalendarEventContentHandler, Telligent.Services.Calendar" /> </settings> </job>
Locate the Tasks folder in the Calendar installation package and copy the remaining jobs into the node of your Job Scheduler's tasks.config file.
You will also need to copy the following files from the installation package to their respective places in the installation directory or the job scheduler service:(note: * means all, e.g. *.dll means all files with the extension of .dll)
Restart your Job Scheduler Service.
This doesn't apply if you are using the Quartz RamJobStore.
You must clear the database state for the Search Indexing job or it will not recognize the new calendar content handlers. Stop the job Scheduler service and run the following SQL on your database to do so:
DELETE FROM QRTZ_TRIGGERS WHERE TRIGGER_NAME='CommunityServer.Search.Tasks.SearchIndexingContentHandlerTask, CommunityServer.Search'DELETE FROM QRTZ_JOB_DETAILS WHERE JOB_NAME = 'CommunityServer.Search.Tasks.SearchIndexingContentHandlerTask, CommunityServer.Search'
In the scenario where you are not using either "fiji" for Telligent Community or "evolution2" for Telligent Enterprise, you will have to make some adjustments in terms of how things get installed.
*** The Event Calendar- Group Application Navigation widget should go on every group page. The Event Calendar-Calendar Breadcrumb widget should go on every calendar based page.
Always verify the version you are running is upgradeable to the latest version.
Please include some screenshots on the widget steps the explanation is not clear.
Also on the database persistence, we should tell how to know if you are using database persistence and how to tell if we are using the Quartz RamJobStore. Is this OOTB for the Job Scheduler or something you would need to configure special?