By etron770 on

I do not find the reason for this error message.
Is there any "manual" how to debug those messages?
 

Drupal 10
#composer update
#composer require 'drupal/commerce_ticketing:^2.0@alpha'  --with-all-dependencies
./composer.json has been updated
Running composer update drupal/commerce_ticketing --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/commerce_ticketing ^2.0@alpha -> satisfiable by drupal/commerce_ticketing[2.0.0-alpha1, ..., 2.0.0-alpha7].
   - drupal/commerce_ticketing[2.0.0-alpha1, ..., 2.0.0-alpha7] require drupal/core ^9 -> found drupal/core[9.0.0, ..., 9.5.11] but these were not loaded, likely because it conflicts with another require.

 

⋅ Categories: Drupal 10.x

Comments

fkelly12054@gmail.com’s picture

fkelly12054@gmail.com commented

I'd look on the commerce ticketing module page and see if they don't have a version that supports at least Drupal 10.4.  Oh, I looked on the module page.  They have a dev release that looks like it might support 10.

composer require 'drupal/commerce_ticketing:2.x-dev@dev'

But you have to deal with the same caveat as you do for all dev releases ... not recommended for production.  Reading quickly through the issue queue it appears that support for this module is at best "iffy".  You'll have to do your own research and I'd recommend you try it on a test or local system.  

jaypan’s picture

jaypan
Location Victoria, BC
commented

I would probably not use this module as-is. It never got past an alpha version for D9, and dev for D10, which says it's probably very buggy. It's the type of module that if one wants to use it, they should be ready to do a lot of bug testing and fixing, and contributing code back to the module to get it working.

Contact me to contract me for D7 -> D10/11 migrations.

etron770’s picture

etron770 commented

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.