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.
Hi! Any plans for d7??
Comment | File | Size | Author |
---|---|---|---|
#13 | drupal_7_port-1044362-13.patch | 5.91 KB | geerlingguy |
#11 | drupal_7_port-1044362-11.patch | 5.46 KB | geerlingguy |
#6 | views-style-settings.jpg | 31.14 KB | geerlingguy |
#3 | views_tree_D7.zip | 3.02 KB | vingborg |
Comments
Comment #1
WilliamV CreditAttribution: WilliamV commentedsubscribe
Comment #2
WilliamV CreditAttribution: WilliamV commentedAny updates on a drupa 7 port?
Comment #3
vingborg CreditAttribution: vingborg commentedI've attached a straight D7 port of Views Tree 2.0 (Views 3 compatible).
Crell, feel free to contact me directly if more work is needed on this, or simply commit it.
Comment #4
Murzsubscribe
Comment #5
geerlingguy CreditAttribution: geerlingguy commented@vingborg - is this port compatible with the references or relations modules? I'd like to use it if at all possible, so I can have a hierarchy of nodes displayed that simply reference "parent" nodes using a node reference field provided by the references module.
[
Edit: Just tried it using the node:nid as the "Main" field, and the network reference field as the "Parent" field, but that showed no content. I'm not exactly sure how this is supposed to work regardless, but I'm ready and willing to test :-)]Edit 2: Nevermind. This module's working very well for what I need. The code in #3 would make a great start for the 7.x branch! I wasn't actually outputting the correct node ID in my view, causing the problem I had above.
Comment #6
geerlingguy CreditAttribution: geerlingguy commentedThe only problem I have is that I can't actually set the 'Wrapper class' or 'List class' for the display. This makes it a lot more annoying to theme the view (I have to override item-list for everything, since I can't change that class...). See attached screenshot for clarification.
Comment #7
vingborg CreditAttribution: vingborg commentedgeerlinguy, is your comment directed at my port (#3) ? These two are remnants of the original D6 version, where they are not used either. It's a piece of software archeology, so to speak ;-)
Comment #8
geerlingguy CreditAttribution: geerlingguy commentedAh, well, then, it seems everything else is working great!
Comment #9
geerlingguy CreditAttribution: geerlingguy commentedThis theme function inside my theme's template.php file seems to work for what I need... gets rid of the .item-list class, at least:
Comment #10
Crell CreditAttribution: Crell commentedIf there are vestigial bits of form lying around still, this isn't RTBC. :-) Well, maybe as a starting point. Either way, please provide a patch against 6.x-2.x, not a zip file. A zip file is much harder to properly merge into the code base. Thanks.
Comment #11
geerlingguy CreditAttribution: geerlingguy commentedPatch against 6.x-2.x (I didn't create a new branch; I assume you'd do that after applying the patch...?).
Comment #12
vingborg CreditAttribution: vingborg commentedThe vestigial form bits are carried over from the D6 version, and stems from the fact that the views style plugin inherits from another plugin that (supposedly) uses them. In essence, I should write code that explicitly removes those particular elements in both versions ... or write code that uses them properly (such as demoed in #9). In either case, it's not a D7 port issue as such, but I shall gladly give it a go at some point in the future :-)
Comment #13
geerlingguy CreditAttribution: geerlingguy commentedAttached patch (adding onto patch in #11) simply removes the two settings (for row class and 'item-list' wrapper class) from the display settings. I imagine we might someday wish to reinstate those settings, but for now, since they're not in use (and I don't think they were in 6.x-2.x either), we can simply remove them.
Patch is working great on a site I'm working on right now. Saved me a few hours' work already :)
Comment #14
geerlingguy CreditAttribution: geerlingguy commentedUpdating title for those tracking via Tracker.
Comment #15
dboulet CreditAttribution: dboulet commentedSeems to me like we should be able to make use of the row and wrapper classes, since the 'HTML list' format makes use of them.
I also think that we could move most of the logic contained in the theme functions to preprocess functions, but maybe that is a separate issue altogether.
Comment #16
geerlingguy CreditAttribution: geerlingguy commented@Crell - might I request to be added as a maintainer of Views Tree for D7.x? I'm using this module pretty heavily on one of my sites, and I'd love to help make sure the 7.x branch is running smoothly (which it is, so far, with the patch in #13 above ;-).
Comment #17
webankit CreditAttribution: webankit commented+1
Comment #18
damiandab CreditAttribution: damiandab commented+1
Comment #19
vthirteen CreditAttribution: vthirteen commentedsubscribe
Comment #20
geek-merlinsub!
Comment #21
mototribe CreditAttribution: mototribe commentedthe zip in #3 worked for me too, pretty cool. Why not make it available in dev on the main page? There isn't much else available in D7 to show trees in a view
Comment #22
geerlingguy CreditAttribution: geerlingguy commentedThen maybe we can get this committed soon, and fix any new bugs in the 7.x branch. I'm still using the module on a pretty large site with the patch in #13 with nary a problem.
Comment #23
Todd Young CreditAttribution: Todd Young commentedTodd likes this.
Comment #24
casey CreditAttribution: casey commentedsub
Comment #25
basicmagic.net CreditAttribution: basicmagic.net commentedsubscribe
Comment #26
Crell CreditAttribution: Crell commentedOK, I finally got around to getting this committed. :-( Committed a slightly modified version of #13 (just whitespace cleanup and such, really) to a new 7.x-2.x branch, which has been pushed. A dev release should be available as soon as the packaging script gets around to it.
Also, somewhere around here I think I had an email from geerlingguy asking to com on as a co-maintainer for this module. Since he is using it and I'm barely touching it lately, I'm going to assume I wasn't imagining things and add him as a co-maintainer. Jeff, if I'm mistaking you for someone else I apologize. :-)
Thank you everyone for your patience.
Comment #27
geerlingguy CreditAttribution: geerlingguy commentedNo, I did send that email, and would love to help maintain this module :) I'm still far enough away from Dave Reid syndrome that I can take on a module or two.
Comment #28
Crell CreditAttribution: Crell commentedOh good. :-) You're already a co-maintainer. Have at. (I need to jettison modules again...)
Comment #29
Crell CreditAttribution: Crell commentedI just pushed an updated version of the port that does much more heavy refactoring to support Field API. The data structure for Field API in Views changed dramatically in Drupal 7, apparently, so I had to do some extra normalization to make everything work. geerlingguy, please verify that the stuff I just pushed works for you, too. If it does, then we can probably tag this at least a beta.
Comment #30
geerlingguy CreditAttribution: geerlingguy commentedHeading down to Texas tomorrow, so I'll try to test in between transit, otherwise I'll have to test things next week.
[Edit: Love the comment you added. I see you've added a little "magic" to the code...]
Comment #31
Crell CreditAttribution: Crell commentedMy code is easily recognized by obsessively detailed and highly opinionated comments detailing the crap I have to work around. :-)