Hi,
I am building a demo website on my computer's localhost. I am new to Drupal, however I have notions of various coding languages.
My setup is: Drupal 11, MariaDB v11.5.2, nodejs v20.17.0, Composer v2.7.9 and PHP v8.3.12
I managed to get Drupal running and I can access my website's dashboard, settings, etc. I now wish to install CivicTheme's latest version. However, when I run the following command: composer require drupal/civictheme, the terminal returns the following message,
./composer.json has been updated
Running composer update drupal/civictheme
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/civictheme[1.8.0, ..., 1.8.1] require drupal/layout_builder_restrictions ^2.19 -> satisfiable by drupal/layout_builder_restrictions[2.19.0, 2.20.0].
- drupal/civictheme[1.4.2, ..., 1.5.1] require drupal/core ^9 || ^10 -> found drupal/core[9.0.0, ..., 9.5.11, 10.0.0, ..., 10.3.5] but the package is fixed to 11.0.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/civictheme[1.6.0, ..., 1.7.1] require drupal/core ^10 -> found drupal/core[10.0.0, ..., 10.3.5] but the package is fixed to 11.0.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/layout_builder_restrictions[2.17.0, ..., 2.20.0] require drupal/core ^9.3 || ^10 -> found drupal/core[9.3.0, ..., 9.5.11, 10.0.0, ..., 10.3.5] but the package is fixed to 11.0.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires drupal/civictheme * -> satisfiable by drupal/civictheme[1.4.2, ..., 1.8.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require drupal/civictheme:*" to figure out if any version is installable, or "composer require drupal/civictheme:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I tried running the command with --with-all-dependencies, eventually I feel like I got closer to the solution with
c:\Windows\System32\drupal>composer require drupal/civictheme:^1.8.1 --with-all-dependencies -W
./composer.json has been updated
Running composer update drupal/civictheme --with-all-dependencies
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/layout_builder_restrictions[2.19.0, ..., 2.20.0] require drupal/core ^9.3 || ^10 -> found drupal/core[9.3.0, ..., 9.5.11, 10.0.0, ..., 10.3.5] but these were not loaded, likely because it conflicts with another require.
- drupal/civictheme 1.8.1 requires drupal/layout_builder_restrictions ^2.19 -> satisfiable by drupal/layout_builder_restrictions[2.19.0, 2.20.0].
- Root composer.json requires drupal/civictheme 1.8.1 -> satisfiable by drupal/civictheme[1.8.1].Now I don't understand what "another require" could be or how to fix it, but I do understand that there seems to be a compatibility issue.
Can you please help me figure it out?
Apologies for any wrong formatting, I am not familiar with posting on technical forums either.
Sincerely,
Sarah.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | civictheme-drupal-11-support-3477127-5.patch | 475 bytes | kelvinwong |
Issue fork civictheme-3477127
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
avpadernoComment #3
tricarte commentedConfirming as a Drupal newbie.
Comment #4
avpadernodrupal/civictheme 1.8.1 requires either drupal/layout_builder_restrictions 2.19.0 or drupal/layout_builder_restrictions 2.20.0, but those require Drupal 9 or Drupal 10. You cannot install drupal/layout_builder_restrictions 2.19.0 nor drupal/layout_builder_restrictions 2.20.0 on Drupal 11.
Comment #6
kelvinwong commentedOnly layout_builder_restrictions 3.x supports Drupal 11. I've created a patch for that.
Comment #7
kelvinwong commentedLooks like layout_builder_restrictions is not the only module with the problem. There's also these modules, the version of the module is not compatible with Drupal 11.
"drupal/field_group": "^3.4",
"drupal/focal_point": "^2.0",
"drupal/layout_builder_restrictions": "^2.19",
"drupal/linkit": "^6.1",
"drupal/menu_block": "^1.10",
"drupal/paragraphs": "^1.16",
"drupal/pathauto": "^1.12",
"drupal/redirect": "^1.9",
"drupal/simple_sitemap": "^4.1",
"drupal/webform": "^6.2"
The Drupal 11 compatible version of field_group and linkit are still in alpha, and webform doesn't have D11 compatible version yet.
Perhaps the CivicTheme cannot be installed in Drupal 11 at this stage until other modules are D11 ready.
Comment #8
fionamorrison23 commented@richardgaunt can you please read through this one. Thanks.
Comment #9
thomas.wardin commented+1
Comment #10
yasnosos commentedDrupal CMS (with v11 core) was released, the only problem with install is drupal/linkit, which needs ^6.1, but on Drupal CMS it is ^7.0.
Please update the dependencies.
Comment #11
viniciusosouza commentedHi! I’m trying to install CivicTheme with Drupal CMS, and I’m getting the same error as @yasnosos. Could you please update drupal/linkit to ^7.0?
Comment #12
fionamorrison23 commentedI've raised this ticket with the CivicTheme TL again just now. We may need to split out into separate issues. I'll update here as soon as I can and link any new tickets if required.
Comment #14
richardgaunt commentedWe have solutions for these upcoming in the release being prepared and scheduled for tomorrow. There will be an alpha recipe for installing on Drupal CMS and we are now developing on Drupal 11.
We are using the following patches for incompatible modules. To install these module dependencies on Drupal 11 add these patches to your composer.json:
Comment #15
richardgaunt commentedComment #16
richardgaunt commentedComment #17
richardgaunt commentedComment #18
richardgaunt commentedComment #19
fionamorrison23 commentedComment #21
lautilg commentedHi CivicTheme team,
I'm currently evaluating a migration/new project using Drupal 11 with CivicTheme.
Since Webform 6.3 is still in Beta (which is a core dependency for most CivicTheme sites), I would like to know if you have any internal roadmap or updates regarding when this combination will be considered "officially stable" for production environments.
Are there any specific recommendations from your side for those of us who need to start D11 projects today but are concerned about the Beta status of such a critical module?
Best regards.
Comment #22
richardgaunt commentedHi Lautlig,
The webform coupling is very loose older versions of webform, 6.2.x should work just fine. Let me know if it does not.
We take our dependencies from GovCMS Australia who seem to be using this beta stream of webform for their websites.
Although noting the dependency on is ^10.2 on webform 6.2.x - so for D11 the beta version is the required version so I would assume that every production site on D11 which has webform is running the beta version, I personally have not encountered any issues.
It would be worth evaluating the webform issue queue and carrying out QA on any webforms but from my experience it has been rock solid in its core functionality. Hope that helps