zend-di | Di component from Zend Framework | Dependency Injection library

It seems the package that you are using is not compatible with your PHP version

You need a compatible PHP version, which is 7.0.0 - 7.0.5 || ^7.0.7.

To solve this issue you can either update your PHP version or downgrade package

This error can be realted to PHP compatibility :

• For Magento 2.3.1+ : PHP 7.1 or PHP 7.2

• For Magento 2.3.0 : PHP 7.1

• For Magento 2.2 : PHP 7.1 or PHP 7.0

• For Magento 2.1 : PHP 7.1, PHP 7.0 or PHP 5.6

• For Magento 2.0 : PHP 7.0, PHP 5.6 or PHP 5.5

Check your PHP version, and upgrade or downgrade PHP if needed.

You will never make Magento 2 works fine without the good version of PHP

Have you checked that file at line 83?

I did, on Github, I see the only question mark on that line is a ?int in the method signature.

I googled for 15seconds and found that it's a new feature of PHP 7.1 . So I checked composer.json of that package and see that it requires "php": "^7.1".

Are you sure you are running PHP 7.3.5 on that machine? Please put a phpinfo(); exit(); in your public/index.php and double check because that error is a symptom you are running a version of php lower than 7.1

The cause of this is that Drupal (drupal/drupal) specifically merges core/composer.json into the project (root) composer.json.

try creating an alias first and then provide it to a factory

A fresh Laravel install comes with a bootstrap/cache/.gitignore file. Its presence (and contents) in the respository ensures that the directory exists in a deployment, but that nothing else within that directory winds up in source control.

The error you're receiving indicates that you didn't check it into your repository (or removed it for some reason). Checking it in should clear up the message, as the folder will exist for your app to write to it.

There are several other instances of this, like storage/logs, a variety of subfolders of storage/framework, etc. If you receive similar errors in these directories, the same fix applies.

That's because you are using https://github.com/nikic/FastRoute router and correct syntax would be:

I finally understood that the problem was not in my php.ini.

As I’m working with userdir, I had to go to /etc/apache2/mods-available/userdir.conf

And change

It looks like your composer packages got out of sync.

To force a refresh delete the vendor folder also delete composer.lock and then run

composer install

It will download everything again, rebuild your vendor and make sure Phinx and Symphony are in sync again.

After you do this, you run your migrations again and see what happens.

This statement of yours

"I dropped all tables and hoped that it will just re-run the migrations as before."

worries me a bit, because the Phinx migration manger keeps its log in the database in a table called phinxlog (sometimes prefixed with a plugin name if you're talking about a plugin). If you deleted that then phix does not know what migrations did you run already and which ones are new. To fix this you may need to mark some of the earlier migrations are migrated so phinx does not attempt to do things that were already done.