# Announcement: new sanitization plugin acts\_as\_sanitiled **URL:** \ **Category:** Rails\ **Created:** [October 15, 2009, 8:15am UTC](https://www.ruby-forum.com/t/announcement-new-sanitization-plugin-acts-as-sanitiled/177338 "2009-10-15T08:15:57Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![dasil003](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/9de0a6/32.png) [@dasil003](https://www.ruby-forum.com/u/dasil003)\ **Post date:** [October 15, 2009, 8:15am UTC](https://www.ruby-forum.com/t/announcement-new-sanitization-plugin-acts-as-sanitiled/177338/1 "2009-10-15T08:15:57Z")
I just finished cooking up a version of acts\_as\_textiled that will sanitize after the RedCloth operation to guarantee well-formedness and XSS safety. I chose this approach over input-filtering like xss\_terminate does because I don’t like to munge the user input, and I didn’t want to have to add an extra column for every textiled field in my app. The acts\_as\_textiled semantics prevent careless template errors, while preserving user input without any DB migrations. I believe the approach will dovetail nicely with koz’s erubis/taint- mode work scheduled for Rails 3 and backported to 2-3-stable and I’ll be looking to integrate them when the time comes. It’s fully gemified, spec’ed in bacon and released to gemcutter: [http://github.com/dasil003/acts\_as\_sanitiled](http://github.com/dasil003/acts_as_sanitiled)