asset_compress | asset compression plugin for CakePHP | Plugin library

In case I understood correctly, you need your bash script to exit in case it encounters errors ? if so, you can use set -e command : What does set -e mean in a bash script?

So actually it was a BUG ndm mentioned in the comments: github.com/cakephp/cakephp/issues/12603

These are only suggestions that may extend the functionality of already installed packages, but everything should work fine without them. For example monolog/monolog will suggest a couple of plugins that will allow logging into different backends. But monolog/monolog will work without them - you may not be able to log for example to Sentry, but monolog will still be usable without this feature.

So usually you can just ignore these suggestions. But you can take a few minutes to check what these suggested packages are actually doing - you can learn about new technologies and solutions that can make your app better and easier to maintain.

If you're really not interested in these suggestions, you can use --no-suggest switch to avoid displaying them on install/update/require:

From the CakeDC installation docs, you need to run composer require cakedc/users.

You need to run this in the same directory as your composer.json file. Your error message says ./composer.json has been created. It will say ./composer.json has been updated if you run it in the correct directory.

Alternatively, you could add "cakedc/users": "^7.0" to the required packages in your composer.json manually, and then run composer install

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.