Sanitize HTML already in database
-
I have csv files of over 9000 user submitted poems (which will now be posts) in my database and some still in CSV files. I am currently at around 2500 posts imported and now I have noticed that one of my biggest contributors had found a hack using contentEditable and various other html. As a result, when a visitor goes to one of these posts, none of the links work and everything is temporarily editable from the front end.
I tried using HTML Lawed and HTML Purifier, but both are outdatted and their functionality shows it. Also, there is still the problem with the data in the database that still has unexceptable HTML.
I realize I could hack into the WordPress core to correct the output, but right now I know that their is still unacceptable HTML in the database. So how can I correct this?
- The topic ‘Sanitize HTML already in database’ is closed to new replies.