Install 2.0.9 without term_merge

aaron.ferris → made their first commit to this issue’s fork.

term_merge is a dependency, so I think, unless im missing something we'd need to add it to composer.json?

MR added

Still referring to version 2.0.10, while downloading with Composer I had been getting the message “dependency not downloaded,” so I assume the instruction was already in the module composer.json.

I'm still a bit of a beginner with Composer, and I'm slowly learning how to handle exceptions and issues, but right now I have an online project with D 10.2.6 and about 20 modules fully managed with Composer, so I don't understand what I might have done wrong with TM.

Ok , I managed to install 2.1.9 with the command “ composer require ‘drupal/taxonomy_manager:<2.0.10’ ”
Everything seems to work fine at first when creating an initial list of terms, but once created they are not shown on the page, but I will open another post for that.
Thanks for everything

🐛 Version 2.0.10 breaks existing installations Needs work
Smoother update process

Oops...many thanks @Rajab
I will try in the morning to see if I can solve it by reinstalling with this your direction

Update
As I had specified, I don't need term_merge, so after the first attempt to install TM 2.0.10 which asked me for the module, uninstalled TM -JqueryUI and updated db, I attempted the installation of version 2.0.9 which, however, gave me the above problems.

Then I realized that traces of the previous attempt remained in composer.lock, and I, damn it, still haven't learned how to turn back with Composer.
So I tested locally: Drupal 10.2.6 and Taxonomy Manager 2.0.9 from scratch. Everything finally works as it should, and for the time being, at least until the major problems with the new version are fixed, I can keep this one.

All that remains to me is to learn how to properly revert the composer.lock. I have found online several methods, opinions and crash alert; can anyone recommend the best one?

Thank you very much for your patience and kindness

You should save your lock file using CVS system (git IMHO the best).
If you have an issue revert the lock file and run composer install to use proper lock deps.

BTW, https://www.drupal.org/project/taxonomy_manager/issues/3444071#comment-1... 🐛 Version 2.0.10 breaks existing installations Needs work is fixed.

Andriy Khomych → closed merge request !32

Automatically closed - issue fixed for 2 weeks with no activity.