Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
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.
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.