History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-10802
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Louis Majanja
Reporter: Nuno Fernandes
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Sakai

Logged events don't include context (siteId)

Created: 19-Jul-2007 04:19   Updated: 23-Oct-2008 08:38
Component/s: Gradebook
Affects Version/s: 2.4.0, 2.4.x
Fix Version/s: 2.4.x

Time Tracking:
Not Specified

Issue Links:
Relate
 

2.4.x Status: Resolved
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
In 2.4.0+ (after SAK-6207), logged events don't include context (siteId). Looking at SAK-6207 events should begin with: /gradebook/SITEID/(...)

Logged events are of the following form instead:

| /gradebook/1/New item | gradebook.newItem |
| /gradebook/1/2/instructor | gradebook.updateItemScores |
| /gradebook/1/instructor | gradebook.downloadRoster |
| /gradebook/1/new gb | gradebook.newItem |




 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Nuno Fernandes - 21-Dec-2007 01:50
Louis,

Even if the contextId is not a siteId, it is usefull that this gets logged in the logged event REF field. In this case (and for specific case of SiteStats), I can be aware that this context is not a siteId so i can retrieve the siteId (if it makes sense) and associate the events with it (so SiteStats can manage Gradebook events).

Thanks,
Nuno

Louis Majanja - 21-Dec-2007 10:59
hey Nuno,
disregard my previous comment - actually i used the gradebookId as the contextId but i should have used the gradebookUid as the contextId. the gradebookUid is the same as the as the siteId in which the gradebook is located.

Louis Majanja - 21-Dec-2007 12:13
reolved @ rev 39608