Ken Sander

Just yesterday I updated a 4.0 site to 4.4.4 and it worked fine. But now on that same site if I run composer update, it gives that error.

Ken Sander

Why was I able to install numerous SS4 sites with this exact setup before then?

null

You'll need to run it from the CLI with PHP7

null

Composer itself is a PHP program

null

If composer is running with PHP 5.4, it cares not for your PHP7 configs

Ken Sander

The parse error I’m getting is not in the web browser, it’s in the terminal from running composer update

Ken Sander

Right but the whole purpose of using the platform config in composer.json is so that it installs using the php 7 version, then runs perfectly in MAMP. I did this for years.

jkersu

Ok actually, I think the file abstraction layer handles all the paths for you without having to edit the database @nightjarnz. Some assets are coming through while some are missing. I had to go pass the first page and then I found some assets coming through 🙂 At least the published ones are coming through, its just the draft assets that aren't

null

Yes. You're building it with PHP5.4 outside of MAMP. You need to run composer install with the version of PHP7 that MAMP is using

Ken Sander

Well actually it still does. Because if I remove it that config, the composer error I get is that my version of php (5.4 from CLI) is not compatible with Silverstripe. So not sure what changed or if this is even the issue.