Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
HS works wonderful with multy-parented terms well with "save linage" option enabled.
I don't need "save lineage" option. But i need "force deepest" option. I have multiple parents vocabulary.
HS breaks in my case. It saves last used root term instead.
See pictures 1-4 for details.
P. S. Sorry for pieces of Russian text on screenshots.
Comment | File | Size | Author |
---|---|---|---|
#5 | 729174-5.patch | 1.35 KB | Wim Leers |
#1 | 1 HS settings.png | 33.39 KB | fasdalf@fasdalf.ru |
#1 | 2 terms.png | 6.03 KB | fasdalf@fasdalf.ru |
#1 | 3 Create story C.png | 5.3 KB | fasdalf@fasdalf.ru |
#1 | 4 Story C created.png | 8.33 KB | fasdalf@fasdalf.ru |
Comments
Comment #1
fasdalf@fasdalf.ru CreditAttribution: fasdalf@fasdalf.ru commentedAttached images was missing.
Comment #2
Wim LeersThat's not a bug, it's by design — it's a limitation of Taxonomy. This is clearly described in the README:
Comment #3
fasdalf@fasdalf.ru CreditAttribution: fasdalf@fasdalf.ru commentedVocabulary has no "multy select" option enabled. Lineage, shown on edit page does not mean much in my case.
I need only last term saved. Core taxonomy saves term itself and shows first found parents during edit.
Core's taxonomy behaves exactly as i need, but it does not scale.
HS behavior is very strange. It does not save selected term as taxonomy does. It saves term's top parent. Why HS can't just show some (first found) lineage for multy-parented term?
Once again. One who disables "save lineage" does not care wich parents will be shown during node edit.
It does not matter, what shown on edit page: A->C or B->C. It's only matters to see "C" term under node teaser. Is it reasonable?
P.S. You didn't look at images at all, did you?
Comment #4
fasdalf@fasdalf.ru CreditAttribution: fasdalf@fasdalf.ru commentedI'm sorry, but i will repeat. I need only one trem, not lineage.
What's the problem?
Comment #5
Wim LeersYou say in your first post:
Which is confirmed in: http://drupal.org/files/issues/2%20terms_0_0.png (yes, I *did* look at your screenshots).
I never talk about a "multy select" option. Please work on your communication skills.
I understand what you mean now though. But that's the first time ever somebody has told me that they don't care which lineage is displayed.
And you're absolutely right: it shouldn't be misbehaving as badly as it is! So I've worked on a work-around that should make it work.
Patch attached. Please review. (See http://drupal.org/patch/apply.)
Comment #6
fasdalf@fasdalf.ru CreditAttribution: fasdalf@fasdalf.ru commentedI'm not stupid. I'm just russian :)
We call it "language barrier." Never mind.
I've tested patched hs_taxonomy in few hours and it works as core taxonomy does. It saves selected term now. There is no side effect found.
I hope to see it in next development build or release on project download page.
Thank you very much!
Comment #7
Wim LeersCommitted!
http://drupal.org/cvs?commit=336236
http://drupal.org/cvs?commit=336238
EDIT: I had forgotten, but I had this part of a reply already waiting:
Hey, I definitely understand your language isn't perfect. Just try even a little harder to improve it further (English is also not my native tongue). It'll give you a major advantage over other job applicants, too :)
I'm sorry if I came across as overly harsh. It's just that it's very difficult to help out if you're not using the exact terminology …
By the way: Russia FTW. It's very hard to kill a Lada (we've been driving Lada's for >20 years I think).
Comment #8
fasdalf@fasdalf.ru CreditAttribution: fasdalf@fasdalf.ru commentedThank you for patch once again. Thank you for English practice too.