Problem/Motivation
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | select2_d11_compatibility_3454104_10.patch | 18.14 KB | jaswinsingh |
Issue fork select2-3454104
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
samitk commentedI reviewed this there are some issues related to Facets Module, as it is not converted to Drupal 11 yet.
Thanks
Samit K.
Comment #4
dqdApplies cleanly and upgrade status under Drupal 10.3 goes green and test install on a Drupal 11 test installation was without flaws. Regarding the scope of this issue RTBC from here +1
Comment #6
hswong3i commentedApply this MR for D11 now with:
Merged with https://www.drupal.org/node/3211796
Comment #7
chr.fritschTests are all failing. Far away from done...
Comment #9
ankitv18 commentedHi @chr.fritsch,
I noticed branch and MR is raised against 8.x-1.x branch and I think this needs to be raised with 2.x branch
Comment #10
jaswinsingh commentedHello,
I have created a patch for 8.x.1.15 to make it compatible with Drupal 11.
Since there is a scripting code
info.ymlfile added by the packaging script from DO. So this patch will fail to apply, We can use orakili/composer-drupal-info-file-patch-helper package that prevents patch from failing as a workaround.Comment #14
jeroentTests are green again.
Comment #15
ankitv18 commentedChanges looks good and great to see all jobs are green now ~~ marking this one RTBC.
Comment #16
ruslan piskarovLooks good too. We need a D11 release as soon as possible. Could the author of the module create a new release?
Comment #17
chr.fritschThanks for fixing the tests. I will review them soon. I am still concerned that this only works with the dev version of the select2 library, but there is nothing we can do about it.
Comment #18
dafederThanks chr.fritsch. Looking forward to a D11-compatible release, for now getting by with the patch plus https://github.com/mglaman/composer-drupal-lenient
Comment #19
heddnTagging
Comment #20
dafederHmm not sure what I'm doing wrong, I have both a select2 field on a content type and use the element in a custom field, with D10 it works but with 11.0.9, after applying the patch and rebuilding I am able to install the module and add fields etc but on both custom form and content type I get a broken field and console errors:
This happens with JS aggregation on or off.
Comment #21
adamzimmermann commentedI ran into the same issue and it stumped me as I'm not a front-end developer. Another developer on my team pointed out that Drupal 11 ships with jQuery 4, Select2 doesn't seem to support jQuery 4 yet, and the
isArraymethod is deprecated in jQuery 4, hence the issue.Here are some links that provide more context:
So we decided to go with the Tagify module/library until this is resolved.
Hope that helps!
Comment #22
dafederOh silly me, that's what chr.fritsch was referring to - I needed to explicitly install the dev version of select2 from npm, which does have support for Jquery4. That's fine, although tagify looks very nice thanks for the tip, may try this at some point. Select2 JS is definitely showing its age.
Comment #23
mably commentedThis is how Webform seems to have fixed it:
https://git.drupalcode.org/project/webform/-/merge_requests/576/diffs
Comment #25
chr.fritschFinally... Thx everyone for your patience