This should cover the caching logic, calling process(), loading the library and its configuration, then returning the processed text. I had originally considered we might not need to continue using a custom cache backend for htmlpurifier, but we will still need it for caching some of the internals of htmlpurifier.
Child issues:
#2405243: Build getHTMLRestrictions()
#2405227: Introduce Composer support
#2405235: Configuration Form
#925300: Give better information about what HTML is allowed
#2405247: Make the configuration form easier to use
Comments
Comment #1
heddnComment #2
heddnComment #3
heddnComment #4
dinarcon commentedComment #5
naveenvalechaLucas,
Could you merge the github code on drupal.org and let's actively get the patches what's needs to be done. Thoughts ?
Comment #6
heddnChanges are pushed to d.o. If you are interested in taking on the porting effort, I'll add you as a maintainer.
Comment #7
naveenvalechaThanks Lucas! We're planning to use it, W'll get back to it sometime later.
Comment #8
naveenvalechaUsing this as plan issue and removed related issues to the child issue.
Comment #9
juanolalla commented