[6.x] Revisions removed when caches cleared and storage is in content/revisions

[mscruse]

Bug description

In Statamic 6 (beta 3) if you enable revisions and change the storage from the default to content/revisions and clear either the application cache or the stache you will lose your revisions in the CP. The files still exist.

This issue does not occur if you leave the storage location as default. I have also tested this on a new Statmic 5 install and the issue does not occur at all, even when changing the storage location.

How to reproduce

1. New Statamic install - upgrade to 6.x
2. Enable revisions in config and a collection
3. Edit an entry and save/publish to create revisions
4. Clear cache - either all, or application cache or just warm stache
5. Go to your entry - look at revisions and the history list is empty

Logs

Environment

Environment
Application Name: Statamic
Laravel Version: 12.48.1
PHP Version: 8.4.17
Composer Version: 2.9.3
Environment: local
Debug Mode: ENABLED
URL: test.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

Statamic
Addons: 0
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.0.0-beta.3 PRO

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[duncanmcclean]

I'm struggling to reproduce this...

1. Enabled revisions
2. Changed the revisions path to base_path('content/revisions')
3. Created an entry & published it
4. Changed something & saved the working copy
5. Cleared the cache with php artisan cache:clear
6. Refreshed the entry
7. I'm able to view revision history as expected

Go to your entry - look at revisions and the history list is empty

Just to confirm, do the revisions still exist in the filesystem?

[mscruse]

I have this in my env if that helps you:

STATAMIC_REVISIONS_PATH=content/revisions

I have had this issue on 2 sites - my demo site where I first saw it, then I did a fresh install and followed the same steps and have the issue.

[mscruse]

OK - just removed that from my .env and changed the config to base_path('content/revisions') and it seems OK.

I still think there is an issue or something that's unclear in the docs around this.

[duncanmcclean]

Must be related to the env variable - will take a look, thanks!