Sylius: 1.7.3 fails to install with composer (payum token_storage issue)

[mjhca]

| Q | A
| ---------------- | -----
| Bug report? | yes
| Sylius version | 1.7.3

Following the install instructions . Environment is Ubuntu 20.04, composer 1.10.1, php 7.4

Run:

composer create-project sylius/sylius

... usual "Configuring" options appear, and then the error:

Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! In BaseNode.php line 441:
!!
!! Invalid configuration for path "payum.security.token_storage": Only one tok
!! en storage could be configured.
!!
!!
!! In MainConfiguration.php line 154:
!!
!! Only one token storage could be configured.
!!
!!
!!
Script @auto-scripts was called via post-update-cmd

Is this a bug? Seems unusual to run into this with just the basic create-project step.

[lchrusciel]

Hey!

Thanks for asking your question. I hope someone will be able to help you with it. However, please consider that our official support channels are:

• Slack
• StackOverflow
• Forum

You can read more about them here: https://docs.sylius.com/en/latest/support/index.html

[Prometee]

@mjhca this is not a Sylius bug, this is happening because you try to install sylius/sylius and not sylius/sylius-standard like the doc explains it : https://docs.sylius.com/en/latest/book/installation/installation.html

Anyway, to those who wants to know why this error is happening : it's because the file symfony.lock file is not aware of the installation of payum/payum-bundle so when the recipes are checked then the payum recipe is run, causing the bug described.

@lchrusciel some other packages are missing in symfony.lock maybe it needs to be updated or deleted and ignored ?

[Catalin-Ionut]

This is still hapening, i want to install the developer edition and i get this error aswell Invalid configuration for path "payum.security.token_storage": Only one token storage could be configured.

[Prometee]

@Catalin-Ionut same answer https://github.com/Sylius/Sylius/issues/11438#issuecomment-628072507, read the documentation carefully it's sylius/sylius-standard not sylius/sylius.

[Catalin-Ionut]

@Prometee based on the docs here if i want to contribute i need to fork the developer edition which is sylius/sylius . After cloning and after composer install at the clear cache step the said error occures.

[Prometee]

@Catalin-Ionut ah ok, so this is not related to the installation of Sylius. As I comment before the symfony.lock file has to be updated.

[foxou33]

Like @Catalin-Ionut said, following instructions here: https://docs.sylius.com/en/latest/book/contributing/code/patches.html leads you to clone Sylius/Sylius. In order to make changes and test them, we need to install and ultimately run into this error.

[foxou33]

Following @Prometee 's suggestion (https://github.com/Sylius/Sylius/issues/11438#issuecomment-628072507), I tried updating symfony.lock by adding these lines:

    "payum/payum-bundle": {
        "version": "2.4.1"
    },

It seems to fix the initial problem but now I get stuck with this error:

Executing script cache:clear [KO]
 [KO]
Script cache:clear returned with error code 1
!!  
!!  In HWIOAuthExtension.php line 164:
!!                                                                                 
!!    You must setup php-http/httplug-bundle to use the default http client servi  
!!    ce.                                                                          
!!                                                                                 
!!  
!!  
Script @auto-scripts was called via post-update-cmd

[Prometee]

@foxou33 don't try to resolve it by hand. There is composer commands to exec missing recipes because there is not only one missing.

[Prometee]

@foxou33 be aware that there will be modified/created files doing this recipe execution so revert all modified/created files except symfony.lock file

[foxou33]

Ok I just tried to run composer symfony:sync-recipes, then reverted everything except symfony.lock then re-ran composer install and it works! :smiley:
Thanks a lot @Prometee , I'm gonna push my branch in a PR so we can check that everything is right because you were right there are a lot of changes in that file...

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[Zales0123]

I believe it can be closed 🖖