Fix: HTMLPurifier cache write error - #1957
Open
toekaa-lnu wants to merge 1 commit into
Open
Conversation
alextselegidis
added a commit
that referenced
this pull request
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By default, HTMLPurifier caches its serialized definitions inside its own
vendor directory (vendor/ezyang/htmlpurifier/library/HTMLPurifier/
DefinitionCache/Serializer), which is commonly deployed read-only or owned
by a different user than the web server - causing write permission errors.
HTMLPurifier is used in Easy!Appointments to validate text-based settings
where HTML is allowed, e.g. texts entered in Settings > Legal Contents >
Privacy Policy or Terms & Conditions. This error could then popup
whenever those texts were shown in the booking UI.
Fix: redirect the cache to storage/cache, the app's own writable data
directory, via storage_path().