Problem/Motivation
When upgrading to Drupal 11.3, this error occurs:
PHP Fatal error:
Drupal\layoutbuilder_search_api\Plugin\search_api\processor\LayoutBuilderReferencesandDrupal\layout_builder\LayoutEntityHelperTraitdefine the same property ($sectionStorageManager) in the composition ofDrupal\layoutbuilder_search_api\Plugin\search_api\processor\LayoutBuilderReferences. However, the definition differs and is considered incompatible. Class was composed in [...]layoutbuilder_search_api/src/Plugin/search_api/processor/LayoutBuilderReferences.phpon line 34
Steps to reproduce
Upgrade from Drupal 11.2 to 11.3 while using this module, then run drush deploy
Proposed resolution
Add a type declaration to the $sectionStorageManager variable to appease PHP.
Remaining tasks
MR forthcoming.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | layoutbuilder_search_api_d11_compatibility-3566471-10.patch | 712 bytes | dench0 |
Issue fork layoutbuilder_search_api-3566471
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
lanny heidbreder commentedComment #4
danflanagan8Instead of adding a type to the declaration, would it make more sense to remove the re-declaration of
$sectionStorageManager?I think so. We don't use that property internally. We should just let the trait manage that property.
Comment #7
webflo commented@danflanagan8 yes!
The property is already defined in the trait. No need to duplicate it in the module.
Comment #8
danflanagan8RTBC for MR 4
Amusingly, I'm using the patch from MR3 on a project because it, of course, works perfectly well. It's just not as good as MR 4 for merging into the project.
Thanks all!
Comment #9
rollins commentedMR 4 works perfectly!
It finally allows me to update Drupal core to 11.3.
Thank you!
Comment #10
dench0D11.3 patch
Comment #13
heddnThanks for the fixes.
Comment #15
cassioalmeida commentedHey, guys
This is working properly, however, I can't find a new release with the patch.
Can we have a new release that includes the fix?
Thank you!