Skip to:

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

Remove legacy content cleaner for Sakai 10

Description

It was agreed on the release call 10/10 that we will either remove the code or disable the paths to getting the previous formatted text processor from functioning. AntiSamy low would be the default as this matches closest with the previous filter.

If someone has the property
content.cleaner.use.legacy.html=true

Then a warning should come up in the logs saying that the legacy content cleaner has been removed.

The configuration attributes were removed in SAK-25270 so if someone tries to actually set this (to true) it won't work.

Environment

None

Test Plan

None

Attachments

1

Activity

Show:

Neal Caidin April 28, 2014 at 1:03 PM

Can this be closed or are there still open questions or QA testing that need to be done?

Jean-François Lévêque October 17, 2013 at 9:33 AM

Decision was not mentioned on http://etherpad.ctools.org/rmmt-2013-10-10. If it had been I wouldn't have asked today.

Hudson CI Server October 16, 2013 at 11:39 AM

Integrated in kernel-trunk #723 (See http://builds.sakaiproject.org:8080/job/kernel-trunk/723/)
cleanup of legacy tests (Revision 130529)

Result = SUCCESS

Hudson CI Server October 16, 2013 at 10:29 AM

Integrated in kernel-trunk #722 (See http://builds.sakaiproject.org:8080/job/kernel-trunk/722/)
Remove legacy content cleaner for 2.10 (Revision 130519)

Result = SUCCESS

Aaron Zeckoski October 16, 2013 at 8:38 AM

Ready for QA

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created October 10, 2013 at 12:07 PM
Updated April 25, 2018 at 3:35 PM
Resolved October 16, 2013 at 8:38 AM
Loading...