Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.7.0
-
None
-
eZPublish 4.7 with eZDFS cluster
Description
Expiring template-block cache (either from the backoffice or through script) doesn't mark the entries in ezdfsfile table has expired. In consequence, it's not possible to clean up the files from the NFS through issuing an expire on the backoffice. The expected behavior would be to have the entries marked as expired in the database so that a subsequent dfscleanup would handle the files removal.
steps to reproduce:
- In a DFS clustered eZP 4.7 environment
- Expire all cache on the back office
- Run : php bin/php/clusterpurge.php --scopes=template-block
- Inspect the NFS cache folder and verify that all template-block cache are still there.
Attachments
Issue Links
- relates to
-
EZP-20433 Documentation improvement: clusterpurge.php
- Closed