Linkit fails silently and throws an exception if you enable autocompletion on terms and then say you want to limit your query by bundle. This is because we make the assumption that there should be a bundle column in the base table of any entity, which is sadly not true.
Core doesn't have a column matching the actually bundle in taxonomy_term_data, instead it has a vid column which points to the vocabulary table.
I suggest that we convert our bundle names to vids before we do the query for terms to resolve the issue.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | term-bundles-1508148-5.patch | 3.56 KB | anon |
| #3 | term-bundles-1508148-3.patch | 2.22 KB | anon |
| #2 | term-bundles-1508148-2.patch | 2.51 KB | anon |
Comments
Comment #1
fabsor commentedBetter title
Comment #2
anonTry this one, do you think we need an update hook for this aswell?
Comment #3
anonOr we could actually reduce that code abit.
Comment #4
fabsor commentedIf we do this on buildSettingsForm the vids will be saved in the linkit profile which might be exported. The vids might change if you add more vocabularies and reinstall an installation profile, so this could potentially show different terms than you intended if you add/remove vocabularies.
Comment #5
anonYes fabsor, thats correct.
Here is an other patch.
I also included the buildGroup method here, as that also will fail because of the vids.
Comment #6
markusbroman commentedThe patch looks good and the term autocompletion works like a charm
Comment #7
anonCommited.