Skip to content

Commit ea068f3

Browse files
committed
troubleshooting article about missing cp assets
1 parent 668e9dd commit ea068f3

File tree

2 files changed

+59
-0
lines changed

2 files changed

+59
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
id: 6056f7d0-f767-496d-a8b0-e1242f69faa2
3+
blueprint: troubleshooting
4+
title: 'Missing Control Panel Assets (Vite manifest not found)'
5+
template: page
6+
categories:
7+
- troubleshooting
8+
---
9+
You've just installed Statamic and are ready to jump into the Control Panel. You head to `/cp` and are met with a `Vite manifest not found` error.
10+
11+
![](/img/vite-manifest-not-found.png)
12+
13+
The most likely reason for this is that **you have Composer plugins disabled**.
14+
15+
There may be a number of reasons why they are disabled, such as:
16+
- You answered no when it asked if you want to trust the plugin
17+
- You have them disabled in your global composer config
18+
- Your Docker setup doesn't allow them
19+
20+
Regardless, you'll need to at least enable one. When installing or updating Statamic via Composer, we use the `pixelfear/composer-dist-plugin` plugin to copy the assets into the appropriate location.
21+
22+
1. You may explicitly allow it by adding the following to your `composer.json`.
23+
24+
```json
25+
{
26+
"name": "statamic/statamic",
27+
"require": {},
28+
"autoload": {},
29+
"config": { // [tl! **]
30+
"optimize-autoloader": true,
31+
"preferred-install": "dist",
32+
"sort-packages": true,
33+
"allow-plugins": { // [tl! **]
34+
"pestphp/pest-plugin": true,
35+
"php-http/discovery": true,
36+
"pixelfear/composer-dist-plugin": true // [tl! ** ++]
37+
} // [tl! **]
38+
}, // [tl! **]
39+
"minimum-stability": "dev",
40+
"prefer-stable": true
41+
}
42+
```
43+
44+
2. Delete the `vendor/statamic/cms` directory. This will force Composer to re-download Statamic in the next step.
45+
```bash
46+
rm vendor/statamic/cms
47+
```
48+
3. Update Statamic
49+
```bash
50+
composer update statamic/cms
51+
```
52+
53+
:::tip
54+
For Docker specifically, you may be able to avoid this in the future by adding this to your `Dockerfile` before any `composer` commands:
55+
56+
```dockerfile
57+
ENV COMPOSER_ALLOW_SUPERUSER=1
58+
```
59+
:::
45.9 KB
Loading

0 commit comments

Comments
 (0)