Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Update antisamy library

Description

We've found some errors in our logs like this:

It seems that this is a bug in antisamy library fixed in the last version.

Activity

Show:

Matthew Jones August 23, 2017 at 9:27 AM

I'm not 100% sure if this issue (the log message) is fixed, but this is updating the antisamy version which looks to be okay.

Matthew Jones February 2, 2017 at 9:47 AM

Well if it can get verified we can merge it, but I don't know what would get it to the verified state. Maybe something to wait on until at least 11.3 is released then get it in.

Neal Caidin February 2, 2017 at 9:41 AM

Should we take the 11 status merge flag off this one if we don't plan on merging into the 11 branch?

Matthew Jones January 30, 2017 at 8:32 AM

We really don't have a test plan for this, and I don't know if I'd merge this to 11 since the upgrade required updating some dependencies in master. It looks like announcement is still deploying an old version of xercesImpl which should also be updated. And rwiki pulled this update for xalan and should still work but needs to be tested.

I'd probably just test this by creating content, testing import/export (process that creates and processes XML), testing out wiki, and creating a new jira to get announcement updated.

Juanjo Meroño January 13, 2017 at 5:26 AM
Edited

After googling a little bit I've found this issue [1], but unfortunately I don't know how to reproduce the problem in Sakai, maybe following the steps indicated in that issue, but we do not use that rule in Sakai, anyway updating antisamy library isn't a bad thing.

[1] https://github.com/bobpaulin/owaspantisamy/issues/168

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Labels

Created January 13, 2017 at 5:16 AM
Updated April 25, 2018 at 3:19 PM
Resolved January 29, 2017 at 7:24 PM