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.
This module just does exactly what my site needs!
What are your plans for D7?
Comment | File | Size | Author |
---|---|---|---|
#26 | 1012064-d7.patch | 43.24 KB | cafuego |
Comments
Comment #1
xjmWell, none of my sites are in D7 (nor will likely be this calendar year), so I don't have the funding to create a D7 version currently. I think the first step to a D7 version is #720600: Views 3 compatibility. Marking postponed for now.
Comment #2
TimelessDomain CreditAttribution: TimelessDomain commentedsubscribing
Comment #3
puya CreditAttribution: puya commentedsubscribing
Comment #4
puya CreditAttribution: puya commentedwow this is exactly what I need right now and unfortunately I'm forced to do this site in d7.. is there any other way of achieving this functionality with whatever that's available in d7 ?
Comment #5
xjmNot that I'm aware of, but it should be straightforward to port.
Comment #6
Taxoman CreditAttribution: Taxoman commentedSubscribing
Comment #7
Summit CreditAttribution: Summit commentedHi, Is there a timeframe for porting this to D7 please?
I need a module dependent on this module in D7.
Thanks a lot in advance!
Greetings, Martijn
Comment #8
xjmSee #1. I'm pretty busy with TAC at the moment. If anyone wants to try a hand at #720600: Views 3 compatibility or test the patch in #1201218: Patch to add theme support, that could help move things along.
Also, just out of curiosity, is this dependent module another contrib project?
Comment #9
Summit CreditAttribution: Summit commentedHi, Yes it is in this link: http://drupal.org/node/231911#comment-4555864
Thanks for your hard work! sorry that I am not a programmer..
Greetings, Martijn
Comment #10
Jason Jaeger Geoprobe CreditAttribution: Jason Jaeger Geoprobe commentedsubscribing
Comment #11
rggoode CreditAttribution: rggoode commentedsubscribe
Comment #12
mototribe CreditAttribution: mototribe commentedsubscribe
Comment #13
mckinleymedia CreditAttribution: mckinleymedia commentedsubscribe
Comment #14
mckinleymedia CreditAttribution: mckinleymedia commentedSheesh! This is super frustrating - they use this exact function in Drupal 7 to display the taxonomy in the admin interface. Can't we just duplicate that admin function and change the links and content?
Comment #15
mototribe CreditAttribution: mototribe commentedhmm, that's a good observation. How can you debug to see which functions and template page is used on the admin page?
Also, checkout the forum module in core, I believe they are displaying a nested tree as well.
http://drupal.org/project/taxonomy_block is another solution
Comment #16
xjm#13: What is super frustrating?
For all subscribers, to see a D7 port more quickly, there are two options:
It's probably a pretty straightforward port.
Comment #17
basicmagic.net CreditAttribution: basicmagic.net commentedsubscribe
Comment #18
adixb CreditAttribution: adixb commentedSubscribe
Comment #19
colanFor Drupal 7, can we deprecate this module in favour of the more general View tree? If that's not possible, maybe missing functionality can be merged into it?
Folks are already using it for D7 (even though there isn't an official release yet).
Comment #20
Summit CreditAttribution: Summit commentedHi,
Any progress on a D7 version of taxonomy lineage. I need a solution for another submodule, and this is depended on Lineage..so.
Thanks a lot in advance for your reply.
Greetings, Martijn
Comment #21
xjmRegarding #20: See #16. Thanks!
Comment #22
xjmComment #23
jantoine CreditAttribution: jantoine commentedHi xjm,
First I would like to thank you for all your taxonomy contributions. I spent a lot of time yesterday researching the different options for storing hierarchical data in a relational database. The following link had a lot of good information: http://stackoverflow.com/questions/4048151/what-are-the-options-for-stor...
After starting my own custom module based on the nested tree model (I did not yet know about this project), I found the closure table method and I must say after having researched it, it seems to offer better performance than even the nested tree model. I also happened to find a d.o project that is already using this method and has a D7 release here: http://drupal.org/project/taxonomy_edge.
It was suggested in #19 to merge this project into the Views Tree module, but that would only answer the views part of the problem, not the efficient querying of the taxonomy structure. In order for that to work, the Views Tree module would need to become dependent on this module. I am wondering instead if we can deprecate this module and merge any missing functionality into the Taxonomy Edge module, or is there a specific reason to keep this as a separate project?
Many hands make light work, and if we can merge all the modules that attempt to fix the taxonomy hierarchy issues in Drupal, perhaps that would go hand in hand with your core issue: #1207326: Refactor taxonomy hierarchy API for performance, consistency, and convenience
Comment #24
Summit CreditAttribution: Summit commentedHi,
Wouldn't not step 1 be to build a D7 Taxonomy Lineage, so modules which depend on this can also move forward?
Greetings, Martijn
Comment #25
xjmYes, please keep the discussions separate. #720600: Views 3 compatibility is the blocker for this right now so please test.
Comment #26
cafuego CreditAttribution: cafuego commentedPatch from 6.x-1.x to a working 7.x version attached. This patch already includes the patch from #720600-5: Views 3 compatibility.
Please test.
I've moved some files around and renamed the term_lineage table to be more in line with the core taxonomy tables.
Comment #27
cafuego CreditAttribution: cafuego commentedA 7.x-1.x-dev download should be available soon.
Comment #28
cafuego CreditAttribution: cafuego commentedClosing issue.