Skip to content
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.

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

Add note regarding Acorn cache when bumping from v3 to 4 #518

Merged
merged 2 commits into from
Aug 2, 2024
Merged
Changes from all commits
Commits
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
5 changes: 4 additions & 1 deletion acorn/upgrading-acorn.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
---
date_modified: 2024-01-16 11:38
date_modified: 2024-08-02 13:45
date_published: 2023-01-13 13:12
description: Acorn v4 introduces some minimal breaking changes that may require updates when coming from Acorn v3.
title: Upgrading Acorn
authors:
- ben
- joshf
---

# Upgrading Acorn
Expand Down Expand Up @@ -206,6 +207,8 @@ namespace App\Providers;
}
```

After doing so, you may need to delete [Acorn's application cache directory](https://roots.io/acorn/docs/directory-structure/). By default, this is located in `[wp-content|app]/cache/acorn/`.

Reference the [Acorn v3 upgrade pull request on the Sage repo](https://github.com/roots/sage/pull/3097) to see a full diff.

#### Target class [assets.manifest] does not exist
Expand Down