Skip to content

docs(filesystem): document use_last_modified_version_strategy option for theme assets #2371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Basti (bneumann97) wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs(filesystem): document use_last_modified_version_strategy option for theme assets #2371

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a8ccf5
docs(filesystem): document use_last_modified_version_strategy option …
bneumann97 Jul 7, 2026
3c038cf
docs(filesystem): rephrasing
bneumann97 Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .wordlist.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -453,6 +453,7 @@ FroshTools
Fullstack
GBP
GCM
GCS
GDPR
GHSA
GIFs
Expand Down
16 changes: 16 additions & 0 deletions guides/hosting/infrastructure/filesystem.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -425,6 +425,22 @@ shopware:
batch_write_size: 250
```

### Disable last-modified version strategy for theme assets

By default, Shopware appends a `?{timestamp}` cache-busting suffix to every theme asset URL by reading the file's last modified time from the filesystem. On remote filesystems such as S3 or GCS (Google Cloud Storage), this can trigger a filesystem metadata call per asset path on cache miss (for example, after a cache flush).

When the default `SeedingThemePathBuilder` is active — which is the case unless you have explicitly changed `storefront.theme.theme_path_builder_id` — this timestamp suffix is redundant. The path builder already rotates the asset path on every theme compilation, which is the actual cache-invalidation event. You can disable the last-modified lookups entirely:

```yaml
# config/packages/shopware.yaml
shopware:
filesystem:
theme:
use_last_modified_version_strategy: false
```

The option defaults to `true`, so existing installations are unaffected. Set it to `false` on shops with a remote theme filesystem to eliminate the extra metadata calls.

### Add your own adapter

To support a storage backend Shopware does not ship with, create a Flysystem adapter (see the [official Flysystem guide](https://flysystem.thephpleague.com/docs/advanced/creating-an-adapter/)) and wrap it in an `AdapterFactory`:
Expand Down
Loading