Select 2 library is not compatible as stated in https://www.drupal.org/project/select2/issues/3454104#comment-15899448.

We can use the fix suggested here: https://www.drupal.org/project/select2/issues/3454104#comment-15930670

CommentFileSizeAuthor
#2 3509122-jquery4-compatibility-1.patch600 bytesmichael.acampora

Issue fork select2-3509122

Command icon 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:

About issue forks

Comments

mike.vindicate created an issue. See original summary.

michael.acampora’s picture

michael.acampora commented
StatusFileSize
new 3509122-jquery4-compatibility-1.patch600 bytes

Attached a patch that applies the same fix as webform does.

michel.g made their first commit to this issue’s fork.

shivam_tiwari made their first commit to this issue’s fork.

shivam_tiwari opened merge request !48

shivam_tiwari’s picture

shivam_tiwari commented
Status: Active » Needs review
oulalahakabu’s picture

oulalahakabu commented
Status: Needs review » Reviewed & tested by the community
pacproduct’s picture

pacproduct commented

Patch in #2 works great, thanks!

cafuego’s picture

cafuego commented

Yup, nice.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Per https://www.drupal.org/project/select2/releases/2.0.0, you need to use the development version of select2 which is compatible.

sridhar52’s picture

sridhar52 commented

On Drupal 11, I still see the same issue with Development version of select2 but patch works great, Thanks

sridhar52’s picture

sridhar52 commented

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

torfj’s picture

torfj
Location Seattle, WA
commented

Upgrading to npm-asset/select2:4.1.0-rc.0 also fixed it for me. Thank you @sridhar52 !

dydave’s picture

dydave commented

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@RC

Make 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.

nagy.balint’s picture

nagy.balint commented

Then would simply installing this module work as well?
https://www.drupal.org/project/jquery_deprecated_functions

manav’s picture

manav commented

I was facing the same issue with Drupal 11.2.5.
So, I tried the above patch, which is working fine with 2.0 version.

RTBC
Drupal : 11.x
MariaDB : 10.11
PHP: 8.3

aaronbauman’s picture

aaronbauman
he/him
commented

Solved for me with, which many of my other projects rely on as well.
https://www.drupal.org/project/jquery_downgrade

I'm not sure if this MR will be backwards compatible, or whether https://www.drupal.org/project/jquery_deprecated_functions makes more sense, but something to keep in mind.

dafeder’s picture

dafeder
he/him
Location Philadelphia, PA
commented

For what it's worth there is now a stable 4.1.0 release that appears totally compatible with D10/11