<p>That error occurs when there is a discrepancy between the schema versions listed in your incoming project config YAML, and what’s actually installed.</p>
<p>If you have the site installed locally, try rebuilding the project config (<strong>Utilities</strong> → <strong>Project Config</strong> → <strong>Rebuild</strong>), and then upload the new <code>config/project/</code> folder to production.</p>

CC BY-SA 4.0
2022-04-06T06:40:21.420Z
That did it, thanks Brandon. 
Tyssen
CC BY-SA 4.0
2022-04-06T04:20:57.470Z
2022-04-06T04:20:57.470Z
Brandon Kelly
<p>I'm working on a site on shared hosting and I can't run <code>composer install</code> from CLI to install the vendor folder because I get</p>
<blockquote>
<p>The Process class relies on proc_open, which is not available on your PHP installation</p>
</blockquote>
<p>and <code>proc_open</code> can't be enabled because it's a security risk.</p>
<p>I can upload the vendor folder from my local and everything works fine but when I go to apply YAML changes, I get:</p>
<blockquote>
<p>Your project config YAML files are expecting different versions to be installed
Try running <code>composer install</code> from your terminal to resolve.</p>
</blockquote>
<p>With the vendor folder already in place, if I run <code>composer install</code> I get everything is up to date. I've tried running <code>composer dump-autoload</code> and then <code>composer install</code> and get the same thing.</p>
<p>So how can I get around this so that I can apply the latest project config changes?</p>

CC BY-SA 4.0
2023-10-30T07:01:56.860Z
When I rebuild the project config, the schema version changes(fixed the issue), but also it has an impact on multiple files. For example, in the 'servd\AssetStorage\AssetsPlatform\Fs' type, the subfolder path value changes from 'staging/images' to 'local/images' in the 'project.yml' file. Is this potentially dangerous for the live site because the path now indicates the local file path, and the 'changedFieldIndicator' value of supertable plugin is set to null? [![subfolder Path is changed from staging to live](https://i.sstatic.net/QDsbW.png)](https://i.sstatic.net/QDsbW.png) [![change
Dialedin Team
<composer><projectconfig><project.yaml>
Your project config YAML files are expecting different versions to be installed
# Your project config YAML files are expecting different versions to be installed

(Asked by: username_0 on 2022-04-06)

I'm working on a site on shared hosting and I can't run `composer install` from CLI to install the vendor folder because I get

> The Process class relies on proc\_open, which is not available on your PHP installation

and `proc_open` can't be enabled because it's a security risk.

I can upload the vendor folder from my local and everything works fine but when I go to apply YAML changes, I get:

> Your project config YAML files are expecting different versions to be installed
> Try running `composer install` from your terminal to resolve.

With the vendor folder already in place, if I run `composer install` I get everything is up to date. I've tried running `composer dump-autoload` and then `composer install` and get the same thing.

So how can I get around this so that I can apply the latest project config changes?

**Tags:** composer, projectconfig, project.yaml

> **Comments:**
> **username_1**: When I rebuild the project config, the schema version changes(fixed the issue), but also it has an impact on multiple files. For example, in the 'servd\AssetStorage\AssetsPlatform\Fs' type, the subfolder path value changes from 'staging/images' to 'local/images' in the 'project.yml' file. Is this potentially dangerous for the live site because the path now indicates the local file path, and the 'changedFieldIndicator' value of supertable plugin is set to null? [![subfolder Path is changed from staging to live](https://i.sstatic.net/QDsbW.png)](https://i.sstatic.net/QDsbW.png) [![change  

---

## 1 answers

### Answer by username_2 on 2022-04-06. Score: 7 | Accepted answer

That error occurs when there is a discrepancy between the schema versions listed in your incoming project config YAML, and what’s actually installed.

If you have the site installed locally, try rebuilding the project config (**Utilities** → **Project Config** → **Rebuild**), and then upload the new `config/project/` folder to production.

> **Comments:**
> **username_0**: That did it, thanks Brandon.   

---

