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

heddn’s picture

heddn’s picture

Issue tags: +SprintWeekend2015
dinarcon’s picture

Assigned: Unassigned » dinarcon
naveenvalecha’s picture

Lucas,
Could you merge the github code on drupal.org and let's actively get the patches what's needs to be done. Thoughts ?

heddn’s picture

Changes are pushed to d.o. If you are interested in taking on the porting effort, I'll add you as a maintainer.

naveenvalecha’s picture

Category: Feature request » Plan

Thanks Lucas! We're planning to use it, W'll get back to it sometime later.

naveenvalecha’s picture

juanolalla’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.