Cannot update Slick module collection

Thank you.

The messages says it all, try:
composer require drupal/slick_extras:^2.0 drupal/slick_views:^3.0 drupal/slick:^3.0 drupal/blazy:^3.0 -W -n

Add more as required.

Basically you must explicitly composer require the modules that were spit out in the message.

Try consulting composer documentations for details. This project has nothing to do with composer for real.

Thanks @gausarts,

That seemed to work a treat in terms of the composer updating

I naively thought that the -w switch would achieve the same.

However, after several cache clears (just in case), I have a dead local site with this message...

TypeError: Drupal\blazy\BlazyBase::__construct(): Argument #1 ($libraries) must be of type Drupal\blazy\Asset\LibrariesInterface, string given, called in C:\Users\nick\Sites\sirclickalot.co.uk\public_html\core\lib\Drupal\Component\DependencyInjection\Container.php on line 261 in Drupal\blazy\BlazyBase->__construct() (line 118 of modules\contrib\blazy\src\BlazyBase.php).
Drupal\Component\DependencyInjection\Container->createService(Array, 'slick.manager') (Line: 179)
Drupal\Component\DependencyInjection\Container->get('slick.manager') (Line: 197)
Drupal::service('slick.manager') (Line: 26)
slick() (Line: 85)
slick_page_attachments(Array) (Line: 311)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}(Object, 'slick') (Line: 395)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('page_attachments', Object) (Line: 308)
Drupal\Core\Render\MainContent\HtmlRenderer->invokePageAttachmentHooks(Array) (Line: 285)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 284)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 186)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 53)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 741)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

It appears to be something to do with the way Slick is calling the Blazy code?

I am using Drupal 10.3.6 and PHP 8.3.7

Checkout Update SOP:
https://git.drupalcode.org/project/blazy/-/blob/3.0.x/docs/UPDATING.md?r...

This combo an sich:

drush cr
drush updb
drush cr

after composer require hardly failed.

Be sure to follow upgrade steps as noted at project home, which points to Blazy:
Upgrading from 1.x to 2.x or 3+

The above suffices, however only if you got a brick, see WSOD section on that link.

> It appears to be something to do with the way Slick is calling the Blazy code?

As noted in the above link, your #3 issue had been properly identified and documented. It is all about cache.

Failing to clear caches properly, you'll get a brick.

The combo drush with the mentioned silly sequence is the only cure, never failed.

However, if you don't drush, the Update SOP covers it with plan B and C, just as well.

Failing to clear caches might also involve permissions of the folder where PHP is dynamically generated. Check out your sites/default|blah.com/files/php, see Drupal folder permissions documentation in general for more accurate info.

Thank you again @gausarts, very helpful indeed.

I have now got it all working again ;-)

I have seen the need for double-drush-cr many times to avoid the WSD and nobody has hever really been able to explain it either - it just seems 'to work'.

What I have also noticed many times is that if I go into the local database and manually truncate all cache_ tables then that also solves the problem.

It does make me wonder whether the good old drush cr does actually miss out something - what do yu think, is that worth investigating?

> double-drush-cr many times to avoid the WSD
Be sure to update your drush.

I did notice your drush issues during likely drush 9-10, not sure. I even wrote a notice at project homes to use the good old Drupal UI if CLI failed. Some people at later drush versions thought I made up things with CLI failures. Now I see you had similar issues like mine years ago. And also see few others.

Updating drush should avoid multiple drush cr, but twice is still needed in between drush updb.

The reason for double drush cr was explained in the docs.

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