How to upgrade to solarium 5.1.x, 5.2.x or 6.0.x

Thank you #2 helped me update

I was having an issue where my Solr search only returned one or two results rather than the 21 results I expected. I had an error on the SEARCH API page of my drupal site, reading:

Solarium 5.0.2 is too old and has known issues. In order to get composer to upgrade solarium to a recent version a core patch or a workaround is required. Have a look at this Core issue and this Search API Solr issue.

Thanks to this page, I ran the following which fixed my search issue:-

#> composer require symfony/event-dispatcher:"4.3.4 as 3.4.99"
#> composer update

- note that I was happy to update the whole Drupal instance. Site wasn't yet live.

Cheers

Thank you @mkalkbrenner for taking the time to document this!

Thank you @mkalkbrenner and @rodtatham, it helped me to resolve the error

Thanks @mkalkbrenner. Should all installations tweak the version constraints, or is it mostly relevant for fresh installations?

I am sorry, I wasn't precise enough. I meant to ask if installations, which have already run the command, need to run the updated command again?

FWIW if you're using the new drupal/core-recommended package it explictly requires symfony/event-dispatcher:v3.4.35 for Drupal 8.8.1. So for now you can use this code:

composer require symfony/event-dispatcher:"4.3.4 as 3.4.35"

You'll likely have to bump this for future updates which is a real pain. It's probably easier to apply the patch.

Thanks for the comment @mstrelan. I hope the issue gets settled soon in #2876675: Allow symfony/event-dispatcher 4+ to be installed in Drupal 8, which has been RTBC since 16. October 2019 ...

Theoretically you could also override the composer managed solarium library (and dependencies) by putting them in the vendor tree of the module, the adjust the module to use it from the module's vendor tree.

This would remove the dependency issues for that module, until the drupal/civicrm/symfony stuff gets sorted.

I've done this to handle similar issues where some module requires an older version of a library that would break everything if it were in the master vendor tree.

There's a reason you can define and run your own autoloaders ;)

I have tried both the patch in #15 https://www.drupal.org/project/search_api_solr/issues/3083601 and this:

composer require symfony/event-dispatcher:"4.3.4 as 3.4.99" drupal/search_api_solr

Problem 1
- drupal/core-recommended 8.8.2 requires symfony/event-dispatcher v3.4.35 -> satisfiable by symfony/event-dispatcher[v3.4.35] but these conflict with your requirements or minimum-stability.
- drupal/core-recommended 8.8.2 requires symfony/event-dispatcher v3.4.35 -> satisfiable by symfony/event-dispatcher[v3.4.35] but these conflict with your requirements or minimum-stability.
- drupal/core-recommended 8.8.2 requires symfony/event-dispatcher v3.4.35 -> satisfiable by symfony/event-dispatcher[v3.4.35] but these conflict with your requirements or minimum-stability.
- Installation request for drupal/core-recommended (locked at 8.8.2, required as ^8.8) -> satisfiable by drupal/core-recommended[8.8.2].

What next??

@kebne read #15

@mstrelan

thx that worked! do you know why the patch #15 https://www.drupal.org/project/search_api_solr/issues/3083601 doesn't work?

All that patch does is allow the older version of solarium to be installed and display warnings that it needs updating.

comment #15 should be added in the INSTALL.md.

It's in particular the symfony/dependency-injection and symfony/event-dispatcher packages that are frozen in time. Both of these are two full versions ahead from what drupal core mandates, and these are drop in compatible with the v:~3.4.x that drupal ships with. I'm trying to install a few packages from packagist that need both of them to be >4.4, and it turns out to be nigh impossible. Installing older versions of the packages is definitely not optimal.

I assume the symfony/console and the symfony/class-loader packages are also suffering the same fate.

Can we like petition the powers that be to up the version of these in core or something?

Edit: I'm an idiot. I just checked and the actual list of packages in dire need of updating is embarrassing. Are we waiting for Drupal 9 to update these?

Does what it now says on #2876675-78: Allow symfony/event-dispatcher 4+ to be installed in Drupal 8 means this won't be an issue on D9?

Nevemind, just saw it on the issue summary, sorry.

Thank you for fixing this, this was quite an annoyance ;)

Hmm updated to 4.1.0 and removed the
composer require symfony/event-dispatcher:"4.3.11 as 3.4.35"

But now I get the following error when browsing the site.

Fatal error: Declaration of Drupal\search_api_solr\Solarium\EventDispatcher\Psr14Bridge::dispatch($event, ?Symfony\Component\EventDispatcher\Event $null = NULL) must be compatible with Psr\EventDispatcher\EventDispatcherInterface::dispatch(Psr\EventDispatcher\object $event)

Any hints?

Well I did an update --with-dependencies on drupal/core drupal /search_api and drupal/search_api_solr
Therefore I am on Drupal 8.9

OK I'll raise a new issue

I was able to update and browse a site fine on Drupal 8.9 with PHP 7.3. No errors. However, I haven't tested the Search API yet.

My problem from #36 was because of PHP7.1

Update worked fine on Drupal 8.9, PHP 7.4

In #38 it says

If you upgrade to 4.1.0 don't forget to revert to the symfony/event-dispatcher version that corresponds with your Drupal Core's requirement.

I know it's a composer question, but how do you do that?
The work around was composer require symfony/event-dispatcher:"4.3.11 as 3.4.35". So how to revert that?

Simply delete that line from your composer.json file and composer update, or if you must use CLI, I think you can run composer remove symfony/event-dispatcher.

I'm not able to run the following to create a new project going directly to Drupal 8.9.1.

I'm following the instructions from here to create the project.

composer create-project 'drupal/recommended-project:^8' drupal-site
pushd drupal-site
composer require drupal/search_api_solr
composer require symfony/event-dispatcher:"4.3.11 as 3.4.41"
popd

I'm using php 7.4 and composer 1.10.1 the output of this is the following... stipped straight to the error...

+ composer require 'symfony/event-dispatcher:4.3.11 as 3.4.41'
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/core-recommended 8.9.1 requires symfony/event-dispatcher v3.4.41 -> satisfiable by symfony/event-dispatcher[v3.4.41] but these conflict with your requirements or minimum-stability.
    - drupal/core-recommended 8.9.1 requires symfony/event-dispatcher v3.4.41 -> satisfiable by symfony/event-dispatcher[v3.4.41] but these conflict with your requirements or minimum-stability.
    - drupal/core-recommended 8.9.1 requires symfony/event-dispatcher v3.4.41 -> satisfiable by symfony/event-dispatcher[v3.4.41] but these conflict with your requirements or minimum-stability.
    - Installation request for drupal/core-recommended (locked at 8.9.1, required as ^8.8) -> satisfiable by drupal/core-recommended[8.9.1].


Installation failed, reverting ./composer.json to its original content.

If search_api_solr is installed after the symfony/event-dispatcher it seems to work. This is different from before...

composer create-project 'drupal/recommended-project:^8' drupal-site
pushd drupal-site
composer require symfony/event-dispatcher:"4.3.11 as 3.4.41"
composer require drupal/search_api_solr
popd

When you install Drupal 8.9.1 you do not need composer require symfony/event-dispatcher:"4.3.11 as 3.4.41" anymore.

When you install Drupal 8.9.1 you do not need composer require symfony/event-dispatcher:"4.3.11 as 3.4.41" anymore.

Wait, what? I think you mean when you install Search API Solr 4.1.x. Drupal 8.9.1 still uses symfony/event-dispatcher 3.4.41.

What I mean is that the work around suggested in in this issue is not required anymore. When you install Drupal 8.9.1 and Search API Solr 4.1.x you should be fine. Also check the release notes of Search API Solr. It's explained there.

I have Drupal 8.9.1 and search_api_solr:4.1.4. According to #48, this issue is resolved. However, I still see the status report error at /admin/reports/status:

Should a new ticket be created to address removing this error, or is this current ticket appropriate?

Disregard #50.