- Issue created by @4kant
- 🇨ðŸ‡Switzerland Gealion Lausanne
Same problem over here. Looks like a Composer problem more than a proper bug of the module as if you download the Zip file or install it via the Drupal GUI it works flawlessly.
I did take a look at the composer.json file to see if I could patch it and use Drupal Lenient to install it anyway, But no cigare : I don't see any reference to domain_access.
Went by the Manual Install route for now.
- Status changed to Postponed: needs info
7 months ago 11:28am 25 May 2024 - 🇧🇪Belgium tim-diels Belgium 🇧🇪
I've used https://github.com/drupal/recommended-project/blob/10.2.x/composer.json as base to set up a site and this installed Drupal 10.2.6
Then I installed this module in 2 different ways and both without any problem.1. Install domain with
composer require 'drupal/domain:^2.0'
and then this module withcomposer require 'drupal/domain_menu_access:^2.0'
where dependencies are met => >works
2. Install this module withcomposer require 'drupal/domain_menu_access:^2.0'
which also installs the dependencies (domain) => worksSo please share the exact commands you use to install the module and also your composer.json so to see if there is a conflict.
To me it seems
drupal/domain_menu_access dev-2.0.x requires drupal/domain_access * -> found drupal/domain_access[dev-1.x, dev-2.0.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.0-beta1, 2.0.x-dev (alias of dev-2.0.x)] but it does not match your minimum-stability.
is more a setting you did not change in your composer.json to allow to install dev versions. It is however not encouraged to use dev versions, this is mostly at own risk. But if you do, you need to set your minimum-stability to match that. For example"minimum-stability": "dev"
- 🇬🇧United Kingdom joehuggans Harrogate, UK
I have been seeing something similar:
Problem 1
- Root composer.json requires drupal/domain_menu_access ^2.0 -> satisfiable by drupal/domain_menu_access[2.0.0].
- drupal/domain_menu_access 2.0.0 requires drupal/domain_access * -> found drupal/domain_access[dev-1.x, dev-2.0.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.0-beta1, 2.0.x-dev (alias of dev-2.0.x)] but it does not match your minimum-stability.Drupal version: 10.2.6
Domain: 2.0.0-beta1Command run to install: composer require 'drupal/domain_menu_access:^2.0'
I think this problem is because the Domain module is in beta??
Changing "minimum-stability" to "dev" in my composer.json file allowed domain_menu_access to be installed.
For what it's worth, my composer.json file
{ "name": "drupal/recommended-project", "description": "Project template for Drupal projects with a relocated document root", "type": "project", "license": "GPL-2.0-or-later", "homepage": "https://www.drupal.org/project/drupal", "support": { "docs": "https://www.drupal.org/docs/user_guide/en/index.html", "chat": "https://www.drupal.org/node/314178" }, "repositories": [ { "type": "composer", "url": "https://packages.drupal.org/8" } ], "require": { "composer/installers": "^2.0", "drupal/admin_toolbar": "^3.4", "drupal/backup_migrate": "^5.0", "drupal/bootstrap5": "^4.0", "drupal/config_ignore": "^3.3", "drupal/core-composer-scaffold": "^10.2", "drupal/core-project-message": "^10.2", "drupal/core-recommended": "^10.2", "drupal/domain": "^2.0@beta", "drupal/domain_menu_access": "^2.0", "drupal/entity_update": "^3.0", "drupal/mail_safety": "^2.0", "drupal/metatag": "^2.0", "drupal/object_log": "^1.1", "drupal/paragraphs": "^1.17", "drupal/paragraphs_ee": "^10.0", "drupal/redirect": "^1.9", "drupal/twig_tweak": "^3.3", "drupal/ultimate_cron": "^2.0@alpha", "drush/drush": "^12.5" }, "conflict": { "drupal/drupal": "*" }, "minimum-stability": "dev", "prefer-stable": true, "config": { "allow-plugins": { "composer/installers": true, "drupal/core-composer-scaffold": true, "drupal/core-project-message": true, "phpstan/extension-installer": true, "dealerdirect/phpcodesniffer-composer-installer": true, "php-http/discovery": true }, "sort-packages": true }, "extra": { "drupal-scaffold": { "locations": { "web-root": "web/" } }, "installer-paths": { "web/core": [ "type:drupal-core" ], "web/libraries/{$name}": [ "type:drupal-library" ], "web/modules/contrib/{$name}": [ "type:drupal-module" ], "web/profiles/contrib/{$name}": [ "type:drupal-profile" ], "web/themes/contrib/{$name}": [ "type:drupal-theme" ], "drush/Commands/contrib/{$name}": [ "type:drupal-drush" ], "web/modules/custom/{$name}": [ "type:drupal-custom-module" ], "web/profiles/custom/{$name}": [ "type:drupal-custom-profile" ], "web/themes/custom/{$name}": [ "type:drupal-custom-theme" ] }, "drupal-core-project-message": { "include-keys": [ "homepage", "support" ], "post-create-project-cmd-message": [ "<bg=blue;fg=white> </>", "<bg=blue;fg=white> Congratulations, you’ve installed the Drupal codebase </>", "<bg=blue;fg=white> from the drupal/recommended-project template! </>", "<bg=blue;fg=white> </>", "", "<bg=yellow;fg=black>Next steps</>:", " * Install the site: https://www.drupal.org/docs/installing-drupal", " * Read the user guide: https://www.drupal.org/docs/user_guide/en/index.html", " * Get support: https://www.drupal.org/support", " * Get involved with the Drupal community:", " https://www.drupal.org/getting-involved", " * Remove the plugin that prints this message:", " composer remove drupal/core-project-message" ] } } }
- Status changed to Closed: works as designed
7 months ago 1:23pm 10 June 2024 - 🇧🇪Belgium tim-diels Belgium 🇧🇪
This has nothing to do with this module indeed. But changing "minimum-stability" to "dev" fixes this. So closing this issue.
- 🇨ðŸ‡Switzerland handkerchief
Same issue here, #5 is fixing the problem. thx.