- Issue created by @mike.vindicate
- 🇳🇱Netherlands mike.vindicate
Attached a patch that applies the same fix as webform does.
- First commit to issue fork.
- @shivam_tiwari opened merge request.
- Status changed to RTBC
3 months ago 7:13am 15 May 2025 - 🇨🇭Switzerland berdir Switzerland
Per https://www.drupal.org/project/select2/releases/2.0.0 → , you need to use the development version of select2 which is compatible.
On Drupal 11, I still see the same issue with Development version of select2 but patch works great, Thanks
ignore the above comment, development version works but also need to upgrade the npm-assest
composer require npm-asset/select2:4.1.0-rc.0- 🇺🇸United States torfj Seattle, WA
Upgrading to npm-asset/select2:4.1.0-rc.0 also fixed it for me. Thank you @sridhar52 !
- 🇫🇷France dydave
Thanks a lot everyone for the great advice!
For those upgrading the module, updating the library constraint for the RC in project's composer.json fixed the issue for us as well:
"npm-asset/select2": "^4.1@RC"Followed by a
composer update (-W)command, or simply:
composer require npm-asset/select2:^4.1@RCMake sure the minimum-stability property allows
'RC'versions though.Is there anything we could do to make the update more automated? Perhaps in module's composer.json file?
Any feedback, suggestions, comments or reviews would be greatly appreciated.
Thanks again for the great help on this issue.