Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
Failed opening required HTMLPurifier.standalone.php*
Fatal error: require_once(): Failed opening required '/path/to/vanilla/plugins/htmlpurifier/htmlpurifier/HTMLPurifier.standalone.php' (include_path='notimportant') in /path/to/vanilla/plugins/htmlpurifier/default.php on line 40
Any help?
0
Best Answer
-
Options
UnderDog
MVP
Go to the exact path to /vanilla/plugins/htmlpurifier (case sensitive!)
See if the file HTMLPurifier.standalone.php exists (case sensitive!)
There was an error rendering this rich post.
0
Answers
Go to the exact path to /vanilla/plugins/htmlpurifier (case sensitive!)
See if the file HTMLPurifier.standalone.php exists (case sensitive!)
There was an error rendering this rich post.
I would advise against HtmlPurifier, as it overhead does not provide enough benefit. The default HtmlLawed is good enough.
What you need is passable content, the lengths html purifier goes to isn't really necessary except for a select use cases. It less about sanitation (despite the name), and more about being 100% to spec.
If everything on the web was 100% to spec, half of it wouldn't work. Html 5 was a reaction to w3c obsession with (X)HTML, which cost the web (easily) ten years. Yes that is right what is possible to do now could have easily been done ten years ago.
rant over.
grep is your friend.