Directory /var/www/html/mysite.com/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer not writable, please chmod to 777

[core45]

I have an issue after deployment:
Directory /var/www/html/mysite.com/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer not writable, please chmod to 777

The fix is released already. You can see the ticket here:
passbolt/passbolt_api#274

Can you please update your package

[stevebauman]

Hi @core45,

Did you publish the config file? The serializer path is already set to your applications storage path:

purify/src/Config/config.php

Line 44 in 266b3bb

'Cache.SerializerPath' => storage_path('purify'),

I looked into the issue you mentioned, and that package does the same thing:

https://github.com/passbolt/passbolt_api/blob/36a4b4177b72a0cdef1406f8f6b99c10b4aafd1e/src/Utility/Purifier.php#L26-L32

[core45]

You are right. I didn't publish the config file.
After publishing it all is good.
Thank you!

[alpharameeztech]

Even without publish the config file, it should suppose to work uninterrupted.

[nielslucas]

I cant seem to find anything about "publish the config file"? any reference where I can look into, i have the same error.

[pmochine]

Same error... the config file is published

[stevebauman]

I cant seem to find anything about "publish the config file"? any reference where I can look into, i have the same error.

@nielslucas It's literally the second installation step in the readme:

To install Purify, run the following in the root of your project:

composer require stevebauman/purify

Then, publish the configuration file using:

php artisan vendor:publish --provider="Stevebauman\Purify\PurifyServiceProvider"

HTMLPurifier requires a cache path, and will default to its own folder inside the vendor directory if you do not publish the configuration file.

Same error... the config file is published

Clear your configuration cache.

[stevebauman]

@alpharameeztech

Even without publish the config file, it should suppose to work uninterrupted.

Since this is a sanitation library, I do not want to merge the configuration with the default built-in configuration, as this may include settings that the developer does not want in their purified text. This could cause major issues for people and they may wonder why some attributes are being removed / included.

All developers must publish the configuration file to define explicitly what they want to be filtered and kept in the purified HTML.

[pmochine]

@stevebauman hey thanks for the responses to the others. I don't understand why it didn't work for me. I have a staging site on a vps, but when I started to deploy my page I found out that I had the same bug as in the comments.

I didn't want to give chmod rights to the vendor folder so I was forced to look for other packages. This one had the same issue mewebstudio/Purifier#27, and fixed it somehow. So with this package from the mewerbstudio, I don't have any issues at all and don't have to do anything. It worked out of the box, even though I prefer your package for the simpler settings much more...

And for the staging site, I'm using a zero deployment tool where all caches are cleared etc.

[stevebauman]

I didn't want to give chmod rights to the vendor folder so I was forced to look for other packages.

This was just fixed in v3.0.1.