V2.x not supported anymore?

Thank you.

> How urgent is updating ...
2.x was a transition from contrib Media to core one. It should have gone since contrib Media was being deprecated a long long time ago, years. No urgency, nor immediate forces, 2.x had been around for far long too much. In fact, delayed too much due to time constraints in making it matured enough.

Take your time, though.

> ... and what is really important to look for concerning compatibility?

1. D8 is dead. D12 is already rising. Anyone should update to higher versions anytime. No negos.
2. We had fatal error issues against PHP8 vs PHP7 compatibility. I cannot afford supporting PHP7, anymore. People speak nasty with fatal errors, and I have to reduce such issues for my own mental health. I am a very kind and sensitive artist, and I love around non-toxic, good and supporting people.
3. Upgrade documentation has been provided and socialized for quite a while.
4. 7k successful upgrades convinced me enough to move forward. It says 3.x upgrade is working properly.
5. I no longer have enough free time to maintain things I no longer use when their replacements work just as finely and more stable, see successful upgrades.

Should you have troubles in upgrades, do not hesitate to post them to benefit others.

Just be sure to read project home Upgrade section.

I hope you can move on and forward, too :)

Thank you for your detailed answer.

just tried to update corresponding modules in a DEV.
tried to update the modules one after another and always got blocking errors from composer.
the only command that seems to work, is requiring all modules at one:

composer require drupal/slick_extras:^2.0 drupal/slick:^3 drupal/slick_views:^3 drupal/blazy:^3 -W

Had the same problem, #4 worked for me. Thanks nojj!!

Hi, Yes I had the same problem also, thanks for #4, this worked great!

+1 for an awesome fix, thank you for that combined command, I hadn't seen that before but it's super handy in these cases with multiple dependencies across modules.

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