I believe this is part of uuid views integration.
Currently, when you want to display let's say documents but only of a specific type, you add a filter to your view which can be "Content: Has taxonomy terms" and you specify which document types you want to allow in this view.
However, this is not portable: Content: Has taxonomy terms stores tids in its configuration, so if you export the view to a feature, and later import it to another site, chances are your tids will have changed. The best way to avoid this issue would be to have a filter such as "Content: Has taxonomy terms (UUID)" which would store the UUIDs and filter on the term UUIDs.
I would be interested in working on that, but would like to have the community's opinion on it first...
Comment | File | Size | Author |
---|---|---|---|
#3 | uuid-has_taxonomy_term-1594230-3.patch | 13.16 KB | guillaumev |
#2 | uuid-has_taxonomy_term-1594230-2.patch | 13.65 KB | guillaumev |
Comments
Comment #1
dixon_I would be positive to add better Views integration. But one needs to be a bit careful, since the UUID column is of the type
varchar
, it makes it a lot slower to join on, etc.But again, it could be useful in some cases, if we just document the implications.
Comment #2
guillaumev CreditAttribution: guillaumev commentedOk here is a first patch, which adds a "Has Taxonomy Term (UUID)" filter. You will see that I had to add the uuid column to taxonomy_index.
Concerning your comment, the UUID column is of the type char, not varchar, so yes there are performance issues compared to using tids, but I don't think they are that important, at least for let's say 90 % of Drupal sites out there...
Comment #3
guillaumev CreditAttribution: guillaumev commentedNew patch which fixes a small bug
Comment #5
kristiaanvandeneyndeIs this issue still unresolved and, if so, could it be that the patch failed because it's doing too much? (hook_install, hook_uninstall, updte hook...)