Hello everyone,
the GUI (admin/modules) says:
System name: simplenews
Version: 3.0.0-beta5
in the composer.json it says
“drupal/simplenews": ‘^4.1’,
When trying to update, the following appears:
#composer update drupal/simplenews --with-all-dependencies
Do not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]?
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating autoload files
Hardening vendor directory with .htaccess and web.config files.
49 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Scaffolding files for drupal/core:
- Copy [web-root]/.htaccess from assets/scaffold/files/htaccess
Cleaning installed packages.
No security vulnerability advisories found.If I want to install Webform Simplenews Handler install, the error message appears:
#composer require 'drupal/webform_simplenews_handler:^2.0'
./composer.json has been updated
Running composer update drupal/webform_simplenews_handler
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/webform_simplenews_handler ^2.0 -> satisfiable by drupal/webform_simplenews_handler[2.0.1].
- drupal/webform_simplenews_handler 2.0.1 requires drupal/simplenews ^1.0 || ^2.0 || ^3.0 -> found drupal/simplenews[dev-1.x, dev-2.x, dev-3.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.0-alpha1, ..., 2.x-dev (alias of dev-2.x), 3.0.0-alpha1, ..., 3.x-dev (alias of dev-3.x)] but it does not match your minimum-stability.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Any hints for me?
Drupal 10
It doesn't work for me with a bootsrap 3 theme either (anymore).
It had worked, then I uninstalled the module. After some time, I reinstalled it and now it have no more function.
Precisely because it is not a stable release, but the function is increasingly part of the current web design, the core team should take over the development. It should be standard without installing a module.
At least in Europe, more and more web designers are demanding this function. The attention span of users is decreasing. There is less and less opportunity to persuade users to register over several clicks.
An important module, it should be incorporated into the core.
Feature Request:
https://www.drupal.org/project/drupal/issues/3513014
✨
Add register login form block
Active
etron770 → created an issue.
Yes, I had tried the module for test purposes on a test installation.
If it works together with the ticket scanner
https://www.drupal.org/project/commerce_ticketing_scanner →
would work, it would be usable.
However, I have come to the conclusion that it is much more effective to use a paid service and pay a few cents per ticket instead of doing the work of finding and fixing bugs.
The same at my site
uninstalling the module fixed this issue.
The explanation and solution:
The theme was created with Ludwig.
Drupal recommends using only composer.
That's why I deleted Ludwig.
But then you have to reinstall all installed modules with composer require
The explanation and solution:
The theme was created with Ludwig.
Drupal recommends using only composer.
That's why I deleted Ludwig.
But then you have to reinstall all installed modules with composer require
The shortest error message comes with:
#composer update "drupal/core-*" --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/address ^1.0, found drupal/address[1.0.0, ..., 1.12.0] but the package is fixed to 2.0.2 (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.
etron770 → created an issue.
in the composer.lock file I found direct links to commerce guys:
[...]
"notification-url": "https://packagist.org/downloads/",
"license": [
"GPL-2.0-or-later"
],
"description": "Drupal code generator",
"support": {
"issues": "https://github.com/Chi-teck/drupal-code-generator/issues",
"source": "https://github.com/Chi-teck/drupal-code-generator/tree/3.6.1"
},
"time": "2024-06-06T17:36:37+00:00"
},
{
"name": "commerceguys/addressing",
"version": "v2.2.2",
"source": {
"type": "git",
"url": "https://github.com/commerceguys/addressing.git",
"reference": "4d23e46ea32534268ea121453c93ceda2bc3ee69"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/commerceguys/addressing/zipball/4d23e46ea32534268ea121453c93ceda2bc3ee69",
"reference": "4d23e46ea32534268ea121453c93ceda2bc3ee69",
"shasum": ""
},
[...]composer require 'drupal/commerce_stock' (without Version throws:)
Problem 1
- drupal/commerce_stock[1.1.0, ..., 1.3.0] require drupal/commerce ~2.0 -> satisfiable by drupal/commerce[2.0.0, ..., 2.40.0].
- drupal/commerce_stock 1.0.0 requires drupal/core ^8 || ^9 -> found drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.3.6 (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/commerce[2.0.0, ..., 2.6.0] require drupal/address ~1.0 -> found drupal/address[1.0.0, ..., 1.12.0] but it conflicts with your root composer.json require (^2.0).
- drupal/commerce[2.7.0, ..., 2.12.0] require drupal/address ^1.4 -> found drupal/address[1.4.0, ..., 1.12.0] but it conflicts with your root composer.json require (^2.0).
- drupal/commerce 2.13.0 requires drupal/address ^1.6 -> found drupal/address[1.6.0, ..., 1.12.0] but it conflicts with your root composer.json require (^2.0).
- drupal/commerce[2.14.0, ..., 2.36.0] require drupal/address ^1.7 -> found drupal/address[1.7.0, ..., 1.12.0] but it conflicts with your root composer.json require (^2.0).
- drupal/commerce[2.17.0, ..., 2.18.0] require drupal/core ^8.7.7 || ^9 -> found drupal/core[8.7.7, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.3.6 (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/commerce[2.19.0, ..., 2.24.0] require drupal/core ^8.8 || ^9 -> found drupal/core[8.8.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.3.6 (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/commerce[2.25.0, ..., 2.28.0] require drupal/core ^8.9 || ^9 -> found drupal/core[8.9.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.3.6 (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/commerce[2.37.0, ..., 2.40.0] require drupal/inline_entity_form ^1.0@RC || ^3.0@RC -> found drupal/inline_entity_form[dev-1.x, dev-3.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 3.0.0-rc15, ..., 3.x-dev (alias of dev-3.x)] but it does not match your minimum-stability.
- Root composer.json requires drupal/commerce_stock * -> satisfiable by drupal/commerce_stock[1.0.0, 1.1.0, 1.2.0, 1.3.0].
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/commerce_stock:*" to figure out if any version is installable, or "composer require drupal/commerce_stock:^2.1" if you know which you need.
The command provided from the module page f.e.
https://www.drupal.org/project/commerce_stock →
composer require 'drupal/commerce_stock:^1.3'
I had inserted it in the source code editor...
and apparently noticed and corrected it at the same time you asked19 Oct 2024 at 15:32 CEST by etron770