Stache Watcher not working
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by tracing how STATAMIC_STACHE_WATCHER=auto handles filesystem changes after an entry is deleted. Reproduce the report by creating an entry in the CP, deleting its file, and checking the CP; compare with clearing the stache. Done means the deleted entry no longer appears in listings or remains editable.
Written by the indexing model from the issue text.
Description
Bug description
I have STATAMIC_STACHE_WATCHER set to auto locally, and I've deleted some collection entries in the file system. However, the listings in the CP still show the entries, and those are even editable. Clearing the stache fixes it.
How to reproduce
- Ensure the stache watcher is enabled
- Create an entry via CP
- Delete the entry in the file system
- Have a look at the CP
Logs
-
Environment
Environment
Application Name: handschin & handschin
Laravel Version: 12.35.0
PHP Version: 8.4.13
Composer Version: 2.8.11
Environment: local
Debug Mode: ENABLED
URL: statamic-handschin.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Livewire
Livewire: v3.6.4
Statamic
Addons: 3
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 6.0.0-alpha.14 PRO
Statamic Addons
marcorieser/statamic-livewire: dev-statamic-6
marcorieser/statamic-vitals: dev-statamic-6
marcorieser/tailwind-merge-statamic: dev-statamic-6
Installation
Fresh statamic/statamic site via CLI
Additional details
v5 to v6 updated
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 102
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statamic/cms
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
assets
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
antlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
smarty-php/smarty#1215 ·
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days