You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Stache:warm() a file storage/framework/cache/data/stache/indexes/entries/{{ collection_handle }}/collection gets created.
That file seems to be never used.
When making a first request to the site after stache:refresh, file storage/framework/cache/data/stache/indexes/entries/{{ collection_handle }}/collectionHandle is created. This is the correct file.
This can significantly add to response time depending on collection(s) size.
How to reproduce
Run stache:refresh
Go to storage/framework/cache/data/stache/indexes/entries/{{ collection_handle }}/ folder and list the files
Make a request to a page iterating through collection entries ({{ collection }} tag)
Check stache folder from point 2 again - collectionHandle file should be there now
Bug description
When running
Stache:warm()
a filestorage/framework/cache/data/stache/indexes/entries/{{ collection_handle }}/collection
gets created.That file seems to be never used.
When making a first request to the site after
stache:refresh
, filestorage/framework/cache/data/stache/indexes/entries/{{ collection_handle }}/collectionHandle
is created. This is the correct file.This can significantly add to response time depending on collection(s) size.
How to reproduce
stache:refresh
storage/framework/cache/data/stache/indexes/entries/{{ collection_handle }}/
folder and list the files{{ collection }}
tag)collectionHandle
file should be there nowLogs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: