SiteStats and SAK-10801
- Former user (Deleted)
Table of Contents |
|---|
1. Information
SiteStats versions >= 1.1 are aware of SAK-10801 - Getting issue details... STATUS resolution so it will use Event.getContext() if this method is available. Having this JIRA applied to Sakai automatically solves all issues related with event siteId/contextId parsing and simplifies the process of adding support for new tools in SiteStats (see STAT-73 - Getting issue details... STATUS to track new tools support).
Although SiteStats will work without SAK-10801 - Getting issue details... STATUS applied, we do recommend patching as it will add support for the tools listed in STAT-73 - Getting issue details... STATUS .
2. Applying SAK-10801
2.1. Applying to Sakai 2.5.0/2.5.x
2.1.1 Apply patches to source code
- Patch event module with Event_SAK-10801_2-5-x.patch
- Patch memory module with Memory_SAK-10801_2-5-x.patch
- Patch search module with Search_SAK-10801_2-5-x.patch
- Patch entitybroker module with:
- Entitybroker_SAK-10801_2-5-0.patch for Sakai 2.5.0
- Entitybroker_SAK-10801_2-5-x.patch for Sakai 2.5.1, 2.5.2, 2.5.x
2.1.2 Convert SAKAI_EVENT database table
- Mysql:
alter table SAKAI_EVENT add column CONTEXT varchar(255);
- Oracle:
alter table SAKAI_EVENT add CONTEXT varchar2(255) NULL;
2.2. Applying to trunk/Sakai 2.6+
SAK-10801 - Getting issue details... STATUS is already included in trunk and versions >= 2.6 so there is no need to patch Sakai.