I think there should be a configuration parameter allowing to specify cache path for HTMLPurifier. Without it HTMLPurifier wants to use vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer directory, which is kind of a weird location to be writable by web server user, under which the worker is running.
I think there should be a configuration parameter allowing to specify cache path for HTMLPurifier. Without it HTMLPurifier wants to use
vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer
directory, which is kind of a weird location to be writable by web server user, under which the worker is running.It could be injected here: