Magento 2 - Readiness check fails on Check Component DependencyInstalling Magento 2 develop branchHowto install Magento2 Testframework as dev requirementMagento 2 Component Manager Won't Load componentGrid/components Times OutUpdating from 2.1.3 to 2.1.4 on magentoRequire specific Magento 2 Github commit with composerMagento extension install - Dependancy errorComponent Manager Readiness Check ErrorsUpgrade Magento 2.2.0 to 2.2.5 giving problemscomposer connection refusedReadiness Check Failure in Magento 2

What is bodily formation? Does it refer to the breath or the body?

How could Tony Stark wield the Infinity Nano Gauntlet - at all?

Installing the original OS X version onto a Mac?

Show two plots together: a two dimensional curve tangent to the maxima of a three dimensional plot

Unsolved Problems due to Lack of Computational Power

Are there any OR challenges that are similar to kaggle's competitions?

Sinc interpolation in spatial domain

Peterhead Codes and Ciphers Club: Weekly Challenge

What allows us to use imaginary numbers?

Virtual destructor moves object out of rodata section

What was the intention with the Commodore 128?

Are there categories whose internal hom is somewhat 'exotic'?

Number of matrices with bounded products of rows and columns

Does the Temple of the Gods spell nullify critical hits?

What's the point of writing that I know will never be used or read?

Earliest evidence of objects intended for future archaeologists?

Outer Class can have how many inner class(es)

My new Acer Aspire 7 doesn't have a Legacy Boot option, what can I do to get it?

Is there a commercial liquid with refractive index greater than n=2?

My father gets angry everytime I pass Salam, that means I should stop saying Salam when he's around?

Meaning of words заштырить and отштырить

Postdoc interview - somewhat positive reply but no news?

9 hrs long transit in DEL

Why is su world executable?



Magento 2 - Readiness check fails on Check Component Dependency


Installing Magento 2 develop branchHowto install Magento2 Testframework as dev requirementMagento 2 Component Manager Won't Load componentGrid/components Times OutUpdating from 2.1.3 to 2.1.4 on magentoRequire specific Magento 2 Github commit with composerMagento extension install - Dependancy errorComponent Manager Readiness Check ErrorsUpgrade Magento 2.2.0 to 2.2.5 giving problemscomposer connection refusedReadiness Check Failure in Magento 2






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















I have Magento Community 2.2. installed on managed VPS (Hetzner).
I am trying to install component and before installation it starts "Readiness check".
All checks out except for:



Check Component Dependency

We found conflicting component dependencies. Hide detail

For additional assistance, see component dependency help .


I don't get any details on error.



WHAT I HAVE TRIED



I have followed instructions from here: https://devdocs.magento.com/guides/v2.2/comp-mgr/trouble/cman/component-depend.html



  • I have run command for file permissions described here: https://devdocs.magento.com/guides/v2.2/install-gde/prereq/file-sys-perms-over.html

  • I have tried with removing files /var/.update_cronjob_status and /var/.setup_cronjob_status and regenerating them starting Module Manager (probably previously known as Component manager)

POSSIBLE CAUSE
I was running installation of a module through composer and when asked for authorization (public and private keys) i have saved them in composer.json.
Since this is one of possible reasons listed in their documentation (changing of composer.json) all it says is to "edit composer.json" but it doesn't say how or what...
I have opened composer.json but I didn't find any keys there...




UPDATE



I have 2 locations for file composer.json:



  • public_htmlcomposer.json

  • public_htmlvarcomposer.json

Also have 2 locations for file auth.json:




  • public_htmlcomposer_homeauth.json

  • .composerauth.json

I appreciate help with this :)




Sorry for updates, I am slowly remembering everything I did :)



I have tried to install this: - Iazel_RegenProductUrl - https://github.com/elgentos/regenerate-catalog-urls



I have installed this: - OlegKoval_RegenerateUrlRewrites - https://github.com/olegkoval/magento2-regenerate_url_rewrites



While installing through SSH I had some memory problems and got Killed in process.
I found a way to run commands again and installed 1 module listed above.



Module wasn't working as expected so I have tried to install one from Magento Marketplace https://marketplace.magento.com/itcolony-seooverwrite.html. This is where I got error with "Readiness check" and started to investigate on possible causes and solutions.



After that I checked composer.json and saw both modules (Iazel_RegenProductUrl and OlegKoval_RegenerateUrlRewrites) are listed in require: section so I deleted the line where Iazel_RegenProductUrl because I thought it caused problems (since install got killed).



Here it my composer.json:




"name": "magento/project-community-edition",
"description": "eCommerce Platform for Growth (Community Edition)",
"type": "project",
"version": "2.2.7",
"license": [
"OSL-3.0",
"AFL-3.0"
],
"require":
"magento/product-community-edition": "2.2.7",
"composer/composer": "@alpha",
"olegkoval/magento2-regenerate-url-rewrites": "^1.4"
,
"require-dev":
"phpunit/phpunit": "~6.2.0",
"squizlabs/php_codesniffer": "3.2.2",
"magento/magento2-functional-testing-framework": "2.3.8",
"phpmd/phpmd": "@stable",
"pdepend/pdepend": "2.5.2",
"friendsofphp/php-cs-fixer": "~2.2.1",
"lusitanian/oauth": "~0.8.10",
"sebastian/phpcpd": "2.0.4"
,
"autoload":
"psr-4":
"Magento\Framework\": "lib/internal/Magento/Framework/",
"Magento\Setup\": "setup/src/Magento/Setup/",
"Magento\": "app/code/Magento/"
,
"psr-0":
"": [
"app/code/",
"generated/code/"
]
,
"files": [
"app/etc/NonComposerComponentRegistration.php"
],
"exclude-from-classmap": [
"**/dev/**",
"**/update/**",
"**/Test/**"
]
,
"autoload-dev":
"psr-4":
"Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/",
"Magento\Tools\": "dev/tools/Magento/Tools/",
"Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
"Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
"Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/"

,
"minimum-stability": "stable",
"repositories":
"0":
"type": "composer",
"url": "https://repo.magento.com/"

,
"extra":
"magento-force": "override"












share|improve this question
































    1















    I have Magento Community 2.2. installed on managed VPS (Hetzner).
    I am trying to install component and before installation it starts "Readiness check".
    All checks out except for:



    Check Component Dependency

    We found conflicting component dependencies. Hide detail

    For additional assistance, see component dependency help .


    I don't get any details on error.



    WHAT I HAVE TRIED



    I have followed instructions from here: https://devdocs.magento.com/guides/v2.2/comp-mgr/trouble/cman/component-depend.html



    • I have run command for file permissions described here: https://devdocs.magento.com/guides/v2.2/install-gde/prereq/file-sys-perms-over.html

    • I have tried with removing files /var/.update_cronjob_status and /var/.setup_cronjob_status and regenerating them starting Module Manager (probably previously known as Component manager)

    POSSIBLE CAUSE
    I was running installation of a module through composer and when asked for authorization (public and private keys) i have saved them in composer.json.
    Since this is one of possible reasons listed in their documentation (changing of composer.json) all it says is to "edit composer.json" but it doesn't say how or what...
    I have opened composer.json but I didn't find any keys there...




    UPDATE



    I have 2 locations for file composer.json:



    • public_htmlcomposer.json

    • public_htmlvarcomposer.json

    Also have 2 locations for file auth.json:




    • public_htmlcomposer_homeauth.json

    • .composerauth.json

    I appreciate help with this :)




    Sorry for updates, I am slowly remembering everything I did :)



    I have tried to install this: - Iazel_RegenProductUrl - https://github.com/elgentos/regenerate-catalog-urls



    I have installed this: - OlegKoval_RegenerateUrlRewrites - https://github.com/olegkoval/magento2-regenerate_url_rewrites



    While installing through SSH I had some memory problems and got Killed in process.
    I found a way to run commands again and installed 1 module listed above.



    Module wasn't working as expected so I have tried to install one from Magento Marketplace https://marketplace.magento.com/itcolony-seooverwrite.html. This is where I got error with "Readiness check" and started to investigate on possible causes and solutions.



    After that I checked composer.json and saw both modules (Iazel_RegenProductUrl and OlegKoval_RegenerateUrlRewrites) are listed in require: section so I deleted the line where Iazel_RegenProductUrl because I thought it caused problems (since install got killed).



    Here it my composer.json:




    "name": "magento/project-community-edition",
    "description": "eCommerce Platform for Growth (Community Edition)",
    "type": "project",
    "version": "2.2.7",
    "license": [
    "OSL-3.0",
    "AFL-3.0"
    ],
    "require":
    "magento/product-community-edition": "2.2.7",
    "composer/composer": "@alpha",
    "olegkoval/magento2-regenerate-url-rewrites": "^1.4"
    ,
    "require-dev":
    "phpunit/phpunit": "~6.2.0",
    "squizlabs/php_codesniffer": "3.2.2",
    "magento/magento2-functional-testing-framework": "2.3.8",
    "phpmd/phpmd": "@stable",
    "pdepend/pdepend": "2.5.2",
    "friendsofphp/php-cs-fixer": "~2.2.1",
    "lusitanian/oauth": "~0.8.10",
    "sebastian/phpcpd": "2.0.4"
    ,
    "autoload":
    "psr-4":
    "Magento\Framework\": "lib/internal/Magento/Framework/",
    "Magento\Setup\": "setup/src/Magento/Setup/",
    "Magento\": "app/code/Magento/"
    ,
    "psr-0":
    "": [
    "app/code/",
    "generated/code/"
    ]
    ,
    "files": [
    "app/etc/NonComposerComponentRegistration.php"
    ],
    "exclude-from-classmap": [
    "**/dev/**",
    "**/update/**",
    "**/Test/**"
    ]
    ,
    "autoload-dev":
    "psr-4":
    "Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/",
    "Magento\Tools\": "dev/tools/Magento/Tools/",
    "Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
    "Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
    "Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/"

    ,
    "minimum-stability": "stable",
    "repositories":
    "0":
    "type": "composer",
    "url": "https://repo.magento.com/"

    ,
    "extra":
    "magento-force": "override"












    share|improve this question




























      1












      1








      1








      I have Magento Community 2.2. installed on managed VPS (Hetzner).
      I am trying to install component and before installation it starts "Readiness check".
      All checks out except for:



      Check Component Dependency

      We found conflicting component dependencies. Hide detail

      For additional assistance, see component dependency help .


      I don't get any details on error.



      WHAT I HAVE TRIED



      I have followed instructions from here: https://devdocs.magento.com/guides/v2.2/comp-mgr/trouble/cman/component-depend.html



      • I have run command for file permissions described here: https://devdocs.magento.com/guides/v2.2/install-gde/prereq/file-sys-perms-over.html

      • I have tried with removing files /var/.update_cronjob_status and /var/.setup_cronjob_status and regenerating them starting Module Manager (probably previously known as Component manager)

      POSSIBLE CAUSE
      I was running installation of a module through composer and when asked for authorization (public and private keys) i have saved them in composer.json.
      Since this is one of possible reasons listed in their documentation (changing of composer.json) all it says is to "edit composer.json" but it doesn't say how or what...
      I have opened composer.json but I didn't find any keys there...




      UPDATE



      I have 2 locations for file composer.json:



      • public_htmlcomposer.json

      • public_htmlvarcomposer.json

      Also have 2 locations for file auth.json:




      • public_htmlcomposer_homeauth.json

      • .composerauth.json

      I appreciate help with this :)




      Sorry for updates, I am slowly remembering everything I did :)



      I have tried to install this: - Iazel_RegenProductUrl - https://github.com/elgentos/regenerate-catalog-urls



      I have installed this: - OlegKoval_RegenerateUrlRewrites - https://github.com/olegkoval/magento2-regenerate_url_rewrites



      While installing through SSH I had some memory problems and got Killed in process.
      I found a way to run commands again and installed 1 module listed above.



      Module wasn't working as expected so I have tried to install one from Magento Marketplace https://marketplace.magento.com/itcolony-seooverwrite.html. This is where I got error with "Readiness check" and started to investigate on possible causes and solutions.



      After that I checked composer.json and saw both modules (Iazel_RegenProductUrl and OlegKoval_RegenerateUrlRewrites) are listed in require: section so I deleted the line where Iazel_RegenProductUrl because I thought it caused problems (since install got killed).



      Here it my composer.json:




      "name": "magento/project-community-edition",
      "description": "eCommerce Platform for Growth (Community Edition)",
      "type": "project",
      "version": "2.2.7",
      "license": [
      "OSL-3.0",
      "AFL-3.0"
      ],
      "require":
      "magento/product-community-edition": "2.2.7",
      "composer/composer": "@alpha",
      "olegkoval/magento2-regenerate-url-rewrites": "^1.4"
      ,
      "require-dev":
      "phpunit/phpunit": "~6.2.0",
      "squizlabs/php_codesniffer": "3.2.2",
      "magento/magento2-functional-testing-framework": "2.3.8",
      "phpmd/phpmd": "@stable",
      "pdepend/pdepend": "2.5.2",
      "friendsofphp/php-cs-fixer": "~2.2.1",
      "lusitanian/oauth": "~0.8.10",
      "sebastian/phpcpd": "2.0.4"
      ,
      "autoload":
      "psr-4":
      "Magento\Framework\": "lib/internal/Magento/Framework/",
      "Magento\Setup\": "setup/src/Magento/Setup/",
      "Magento\": "app/code/Magento/"
      ,
      "psr-0":
      "": [
      "app/code/",
      "generated/code/"
      ]
      ,
      "files": [
      "app/etc/NonComposerComponentRegistration.php"
      ],
      "exclude-from-classmap": [
      "**/dev/**",
      "**/update/**",
      "**/Test/**"
      ]
      ,
      "autoload-dev":
      "psr-4":
      "Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/",
      "Magento\Tools\": "dev/tools/Magento/Tools/",
      "Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
      "Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
      "Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/"

      ,
      "minimum-stability": "stable",
      "repositories":
      "0":
      "type": "composer",
      "url": "https://repo.magento.com/"

      ,
      "extra":
      "magento-force": "override"












      share|improve this question
















      I have Magento Community 2.2. installed on managed VPS (Hetzner).
      I am trying to install component and before installation it starts "Readiness check".
      All checks out except for:



      Check Component Dependency

      We found conflicting component dependencies. Hide detail

      For additional assistance, see component dependency help .


      I don't get any details on error.



      WHAT I HAVE TRIED



      I have followed instructions from here: https://devdocs.magento.com/guides/v2.2/comp-mgr/trouble/cman/component-depend.html



      • I have run command for file permissions described here: https://devdocs.magento.com/guides/v2.2/install-gde/prereq/file-sys-perms-over.html

      • I have tried with removing files /var/.update_cronjob_status and /var/.setup_cronjob_status and regenerating them starting Module Manager (probably previously known as Component manager)

      POSSIBLE CAUSE
      I was running installation of a module through composer and when asked for authorization (public and private keys) i have saved them in composer.json.
      Since this is one of possible reasons listed in their documentation (changing of composer.json) all it says is to "edit composer.json" but it doesn't say how or what...
      I have opened composer.json but I didn't find any keys there...




      UPDATE



      I have 2 locations for file composer.json:



      • public_htmlcomposer.json

      • public_htmlvarcomposer.json

      Also have 2 locations for file auth.json:




      • public_htmlcomposer_homeauth.json

      • .composerauth.json

      I appreciate help with this :)




      Sorry for updates, I am slowly remembering everything I did :)



      I have tried to install this: - Iazel_RegenProductUrl - https://github.com/elgentos/regenerate-catalog-urls



      I have installed this: - OlegKoval_RegenerateUrlRewrites - https://github.com/olegkoval/magento2-regenerate_url_rewrites



      While installing through SSH I had some memory problems and got Killed in process.
      I found a way to run commands again and installed 1 module listed above.



      Module wasn't working as expected so I have tried to install one from Magento Marketplace https://marketplace.magento.com/itcolony-seooverwrite.html. This is where I got error with "Readiness check" and started to investigate on possible causes and solutions.



      After that I checked composer.json and saw both modules (Iazel_RegenProductUrl and OlegKoval_RegenerateUrlRewrites) are listed in require: section so I deleted the line where Iazel_RegenProductUrl because I thought it caused problems (since install got killed).



      Here it my composer.json:




      "name": "magento/project-community-edition",
      "description": "eCommerce Platform for Growth (Community Edition)",
      "type": "project",
      "version": "2.2.7",
      "license": [
      "OSL-3.0",
      "AFL-3.0"
      ],
      "require":
      "magento/product-community-edition": "2.2.7",
      "composer/composer": "@alpha",
      "olegkoval/magento2-regenerate-url-rewrites": "^1.4"
      ,
      "require-dev":
      "phpunit/phpunit": "~6.2.0",
      "squizlabs/php_codesniffer": "3.2.2",
      "magento/magento2-functional-testing-framework": "2.3.8",
      "phpmd/phpmd": "@stable",
      "pdepend/pdepend": "2.5.2",
      "friendsofphp/php-cs-fixer": "~2.2.1",
      "lusitanian/oauth": "~0.8.10",
      "sebastian/phpcpd": "2.0.4"
      ,
      "autoload":
      "psr-4":
      "Magento\Framework\": "lib/internal/Magento/Framework/",
      "Magento\Setup\": "setup/src/Magento/Setup/",
      "Magento\": "app/code/Magento/"
      ,
      "psr-0":
      "": [
      "app/code/",
      "generated/code/"
      ]
      ,
      "files": [
      "app/etc/NonComposerComponentRegistration.php"
      ],
      "exclude-from-classmap": [
      "**/dev/**",
      "**/update/**",
      "**/Test/**"
      ]
      ,
      "autoload-dev":
      "psr-4":
      "Magento\Sniffs\": "dev/tests/static/framework/Magento/Sniffs/",
      "Magento\Tools\": "dev/tools/Magento/Tools/",
      "Magento\Tools\Sanity\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
      "Magento\TestFramework\Inspection\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
      "Magento\TestFramework\Utility\": "dev/tests/static/framework/Magento/TestFramework/Utility/"

      ,
      "minimum-stability": "stable",
      "repositories":
      "0":
      "type": "composer",
      "url": "https://repo.magento.com/"

      ,
      "extra":
      "magento-force": "override"









      magento2 extensions






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 31 at 11:51







      Oktarin

















      asked Mar 30 at 17:54









      OktarinOktarin

      576 bronze badges




      576 bronze badges























          3 Answers
          3






          active

          oldest

          votes


















          1














          This is according to the documentation.



          Typically, component dependency conflicts result from someone manually editing the Magento 2 composer.json file. It can also be caused by third-party modules that depend on earlier Magento components than the ones you have installed. Meaning you have to check the composer.json of the component you are trying to install and determine from its require modules which dependency might be the cause of the issue.



          Lastly, authentication keys are saved in auth.json file, not inside composer.json. try to check it you should see your keys there.






          share|improve this answer

























          • Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

            – Oktarin
            Mar 31 at 10:23











          • Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

            – fmsthird
            Mar 31 at 10:37











          • which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

            – fmsthird
            Mar 31 at 10:39











          • I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

            – Oktarin
            Mar 31 at 11:34











          • In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

            – fmsthird
            Mar 31 at 11:42


















          1














          auth.jsonis located at ~/.composer/auth.json






          share|improve this answer
































            0














            For this problem you have to delete these lines in Composer.json, and it is solved:



            "require-dev": 
            "allure-framework/allure-phpunit": "~1.2.0",
            "friendsofphp/php-cs-fixer": "~2.13.0",
            "lusitanian/oauth": "~0.8.10",
            "magento/magento-coding-standard": "~1.0.0",
            "magento/magento2-functional-testing-framework": "~2.3.14",
            "pdepend/pdepend": "2.5.2",
            "phpmd/phpmd": "@stable",
            "phpunit/phpunit": "~6.5.0",
            "sebastian/phpcpd": "~3.0.0",
            "squizlabs/php_codesniffer": "3.3.1"
            ,





            share|improve this answer





























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "479"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f268073%2fmagento-2-readiness-check-fails-on-check-component-dependency%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














              This is according to the documentation.



              Typically, component dependency conflicts result from someone manually editing the Magento 2 composer.json file. It can also be caused by third-party modules that depend on earlier Magento components than the ones you have installed. Meaning you have to check the composer.json of the component you are trying to install and determine from its require modules which dependency might be the cause of the issue.



              Lastly, authentication keys are saved in auth.json file, not inside composer.json. try to check it you should see your keys there.






              share|improve this answer

























              • Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

                – Oktarin
                Mar 31 at 10:23











              • Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

                – fmsthird
                Mar 31 at 10:37











              • which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

                – fmsthird
                Mar 31 at 10:39











              • I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

                – Oktarin
                Mar 31 at 11:34











              • In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

                – fmsthird
                Mar 31 at 11:42















              1














              This is according to the documentation.



              Typically, component dependency conflicts result from someone manually editing the Magento 2 composer.json file. It can also be caused by third-party modules that depend on earlier Magento components than the ones you have installed. Meaning you have to check the composer.json of the component you are trying to install and determine from its require modules which dependency might be the cause of the issue.



              Lastly, authentication keys are saved in auth.json file, not inside composer.json. try to check it you should see your keys there.






              share|improve this answer

























              • Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

                – Oktarin
                Mar 31 at 10:23











              • Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

                – fmsthird
                Mar 31 at 10:37











              • which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

                – fmsthird
                Mar 31 at 10:39











              • I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

                – Oktarin
                Mar 31 at 11:34











              • In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

                – fmsthird
                Mar 31 at 11:42













              1












              1








              1







              This is according to the documentation.



              Typically, component dependency conflicts result from someone manually editing the Magento 2 composer.json file. It can also be caused by third-party modules that depend on earlier Magento components than the ones you have installed. Meaning you have to check the composer.json of the component you are trying to install and determine from its require modules which dependency might be the cause of the issue.



              Lastly, authentication keys are saved in auth.json file, not inside composer.json. try to check it you should see your keys there.






              share|improve this answer













              This is according to the documentation.



              Typically, component dependency conflicts result from someone manually editing the Magento 2 composer.json file. It can also be caused by third-party modules that depend on earlier Magento components than the ones you have installed. Meaning you have to check the composer.json of the component you are trying to install and determine from its require modules which dependency might be the cause of the issue.



              Lastly, authentication keys are saved in auth.json file, not inside composer.json. try to check it you should see your keys there.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Mar 30 at 20:57









              fmsthirdfmsthird

              3,6234 gold badges8 silver badges31 bronze badges




              3,6234 gold badges8 silver badges31 bronze badges















              • Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

                – Oktarin
                Mar 31 at 10:23











              • Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

                – fmsthird
                Mar 31 at 10:37











              • which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

                – fmsthird
                Mar 31 at 10:39











              • I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

                – Oktarin
                Mar 31 at 11:34











              • In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

                – fmsthird
                Mar 31 at 11:42

















              • Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

                – Oktarin
                Mar 31 at 10:23











              • Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

                – fmsthird
                Mar 31 at 10:37











              • which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

                – fmsthird
                Mar 31 at 10:39











              • I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

                – Oktarin
                Mar 31 at 11:34











              • In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

                – fmsthird
                Mar 31 at 11:42
















              Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

              – Oktarin
              Mar 31 at 10:23





              Thank you. I have updated the question with file locations - it seems I have double files (is that normal?). I am not sure what am I supposed to do with composer.json - should I remove lines where suspicious modules are mentioned?

              – Oktarin
              Mar 31 at 10:23













              Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

              – fmsthird
              Mar 31 at 10:37





              Yeah that's normal , but you should only work with those from your Magento root directory, public_htmlcomposer.json and public_htmlauth.json

              – fmsthird
              Mar 31 at 10:37













              which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

              – fmsthird
              Mar 31 at 10:39





              which module are you trying to install when you get the error? probably check from there, open it check its composer.json and look for dependencies that has an old version change it to the latest version and it should work

              – fmsthird
              Mar 31 at 10:39













              I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

              – Oktarin
              Mar 31 at 11:34





              I have installed this: github.com/olegkoval/magento2-regenerate_url_rewrites and have tried to install this: github.com/elgentos/regenerate-catalog-urls

              – Oktarin
              Mar 31 at 11:34













              In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

              – fmsthird
              Mar 31 at 11:42





              In this https://github.com/elgentos/regenerate-catalog-urls module's composer.json, try to remove everything in require, like leave it as "require": ,

              – fmsthird
              Mar 31 at 11:42













              1














              auth.jsonis located at ~/.composer/auth.json






              share|improve this answer





























                1














                auth.jsonis located at ~/.composer/auth.json






                share|improve this answer



























                  1












                  1








                  1







                  auth.jsonis located at ~/.composer/auth.json






                  share|improve this answer













                  auth.jsonis located at ~/.composer/auth.json







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 30 at 23:59









                  NSwanson7NSwanson7

                  537 bronze badges




                  537 bronze badges
























                      0














                      For this problem you have to delete these lines in Composer.json, and it is solved:



                      "require-dev": 
                      "allure-framework/allure-phpunit": "~1.2.0",
                      "friendsofphp/php-cs-fixer": "~2.13.0",
                      "lusitanian/oauth": "~0.8.10",
                      "magento/magento-coding-standard": "~1.0.0",
                      "magento/magento2-functional-testing-framework": "~2.3.14",
                      "pdepend/pdepend": "2.5.2",
                      "phpmd/phpmd": "@stable",
                      "phpunit/phpunit": "~6.5.0",
                      "sebastian/phpcpd": "~3.0.0",
                      "squizlabs/php_codesniffer": "3.3.1"
                      ,





                      share|improve this answer































                        0














                        For this problem you have to delete these lines in Composer.json, and it is solved:



                        "require-dev": 
                        "allure-framework/allure-phpunit": "~1.2.0",
                        "friendsofphp/php-cs-fixer": "~2.13.0",
                        "lusitanian/oauth": "~0.8.10",
                        "magento/magento-coding-standard": "~1.0.0",
                        "magento/magento2-functional-testing-framework": "~2.3.14",
                        "pdepend/pdepend": "2.5.2",
                        "phpmd/phpmd": "@stable",
                        "phpunit/phpunit": "~6.5.0",
                        "sebastian/phpcpd": "~3.0.0",
                        "squizlabs/php_codesniffer": "3.3.1"
                        ,





                        share|improve this answer





























                          0












                          0








                          0







                          For this problem you have to delete these lines in Composer.json, and it is solved:



                          "require-dev": 
                          "allure-framework/allure-phpunit": "~1.2.0",
                          "friendsofphp/php-cs-fixer": "~2.13.0",
                          "lusitanian/oauth": "~0.8.10",
                          "magento/magento-coding-standard": "~1.0.0",
                          "magento/magento2-functional-testing-framework": "~2.3.14",
                          "pdepend/pdepend": "2.5.2",
                          "phpmd/phpmd": "@stable",
                          "phpunit/phpunit": "~6.5.0",
                          "sebastian/phpcpd": "~3.0.0",
                          "squizlabs/php_codesniffer": "3.3.1"
                          ,





                          share|improve this answer















                          For this problem you have to delete these lines in Composer.json, and it is solved:



                          "require-dev": 
                          "allure-framework/allure-phpunit": "~1.2.0",
                          "friendsofphp/php-cs-fixer": "~2.13.0",
                          "lusitanian/oauth": "~0.8.10",
                          "magento/magento-coding-standard": "~1.0.0",
                          "magento/magento2-functional-testing-framework": "~2.3.14",
                          "pdepend/pdepend": "2.5.2",
                          "phpmd/phpmd": "@stable",
                          "phpunit/phpunit": "~6.5.0",
                          "sebastian/phpcpd": "~3.0.0",
                          "squizlabs/php_codesniffer": "3.3.1"
                          ,






                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Aug 7 at 3:40









                          where

                          5214 silver badges15 bronze badges




                          5214 silver badges15 bronze badges










                          answered Aug 6 at 22:27









                          Ricardo VegaRicardo Vega

                          11 bronze badge




                          11 bronze badge






























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Magento Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f268073%2fmagento-2-readiness-check-fails-on-check-component-dependency%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Grendel Contents Story Scholarship Depictions Notes References Navigation menu10.1093/notesj/gjn112Berserkeree

                              Area configuration aggregation error after install Porto themeMagento 2.1 CE Installed but front/backend not loading/workingCSS not loading on page within Magento 2 pageCannot install module in Magento 2no commands defined in the “setup” namespace. in Magento2Magento 2: Static files are present but shows 404Why do i have to always run the commands to clean cache in Magento 2.1.8?Failure reason: 'Unable to unserialize value.'Error 500 after magento migrationIn production mode the site does not loadMagento 2 : Error 500 after installing

                              Middle Expansion Olielle Resaix Definition: Uttering songs of triumph shouting with joy triumphant exulting Sejunction Journal 붙다 달 고급 품목 외출 The stretch trades the screeching tin. Definition: The act of speaking with a drawl a drawl Cough Sand Definition: An uproar a quarrel a noisy outbreak Shake Iron Publicize Horse House Baby 사과 Resaix Flaggy Jelly Temporary Unequaled Puppet A drop in the bucket Shrew 성격 회원 성질 미팅 The burn frames the tacky quality. Materialistic The smoke reduces the way. Yammoe Nondescript Cheek 얼굴 배 약하다 날리다 타다 The illegal country shows the iron. Help Rule Drearien Smoke Teaching Meaty Wasp Abraham Lincoln Jaws 진심 수리하다 Size Cork Idea Convert Think Lark John Lennon 거울 청소 군 추천하다 아이스크림