@alexandergull could you tag a release? Drupal 11 is released.
For people looking for a solution.
I found a gist online, untested, but it's a start.
https://gist.github.com/beerendlauwers/03acb112c80af0bf91546a05f790057a
aspilicious → created an issue.
Is there a reason we limit drupal 10 versions?
core_version_requirement: ^8.8 || ^9 || ~10.0.0 || ~10.1.0 || ~10.2.0
Why don't you add
core_version_requirement: ^8.8 || ^9 || ~10
Anybody → credited aspilicious → .
Filter on redirect
aspilicious → created an issue.
"The big thing though is retaining AJAX autocomplete for scalability."
This is very important for a lot of projects.
I know that select2 implementations of a normal select can go wrong with +1000 elements.
So something like this, strike through can be colors
My node title | article | published | fr es
in Drupal 7 this is usually solved with one row for each entity and sometimes an extra column with all the language codes and the translated ones look different thas the others.
The current state is too confusing for most clients.
I'm sorry, I meant column.
I'm a JS noob, so I can't say anything useful, but I think when it's done we need to manual test this with 1000+ tags to see if it has any effect. Just to be sure. I'm always ready for doing that when needed.
It will gain me lots of credits with the UX designers at work ;)
We have a site with more than 6000 tags and counting (since september 2014). We can't use select fields for those in combination with select2 because it's nearly impossible to render.
Making tags a select field would introduce severe performance issues.
As I do see the advantage for 95% of the use cases I would like to have a fallback to the current behaviour. But that would be hard because one widget is a textfield and the other a select widget :s
Damn...
Can't we fund a JS genius to make a drupalSelect fork of select2? XD
Tag autocompletion still has issues. I made two tags:
"Some tag", "a new tag"
When editing the node you get 1 merged tag: "some tag, a new tag". The tag list in the backend looks ok, so it's a js thingie.
I WANT this patch so I tested it but found some problems.
- tags with spaces don't get recognised
- When editing the same node nothing gets recognised
- Why is timezone a select 2 field and country not?
- Can there be multiple authors? That's confusing. After the first author the autocomplete doesn't work anyway.