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.
Sorry if this has already been answered somewhere and I didn't find it. I'd like to know if there are plans to port Hierarchical Select to Drupal 7. I realize that there hasn't been a stable release yet for Drupal 6, but hopefully there will be a Drupal 7 version.
Comment | File | Size | Author |
---|---|---|---|
#75 | hierarchical_select_582484_1.patch | 22.27 KB | ELC |
#6 | hierarchical_select-D7PORT.patch | 13.85 KB | JohnWoltman |
Comments
Comment #1
Wim LeersThe Drupal 6 version is stable, but hasn't had a stable release yet because not all "integration modules" have been ported yet. I'm going to ignore that fact and start making releases.
I haven't begun working on a Drupal 7 version yet. It wouldn't have to change much from the current Drupal 6 version probably.
If you're interested in helping with development, let me know!
Comment #2
Bilmar CreditAttribution: Bilmar commentedsubscribing - looking forward to this great module in Drupal 7!
I would like to help with any testing in the future.
http://webchick.net/node/74
Comment #3
JohnWoltman CreditAttribution: JohnWoltman commentedSubscribing to this as well. I read some discussion on taxonomy in D7 and the inclusion of HS into core. I guess that isn't happening, but I'd be willing to help test a D7 port of HS.
Comment #4
BenK CreditAttribution: BenK commentedSubscribing...
Comment #5
Wim LeersD7 into core didn't happen because unit tests are required, HS in its current state is too messy and FAPI is not flexible enough to allow for clean code.
Before HS can be in core, FAPI needs to be cleaned up, preferably rewritten. So it's D8 material for sure.
The D7 port should and will be done much faster than the D6 port. At this point I can't guarantee a release of HS for D7 on the day that D7 will be released though …
Anyway, thanks for the volunteering to test! :) I'll definitely need you!
Comment #6
JohnWoltman CreditAttribution: JohnWoltman commentedWhen you're ready for help I can use IRC. I tried making HS work in D7, and I got rid of all the installation errors, but I don't know enough about Drupal (yet!) t o make the whole thing work. Most of the work was getting rid of db_result calls. There were some other function calls that were removed in D7, so I updated them as well. I hope the effort was worthwhile, but like I said I don't know much about how it all ties together.
There are lots of errors when loading a page, but I can't figure out what I'm doing wrong.
Comment #7
YK85 CreditAttribution: YK85 commented+1 subscribing, it would be awesome to have a d7 version of HS for testing before Drupal 7 stable is released. Thanks!
Comment #8
JohnWoltman CreditAttribution: JohnWoltman commentedI'm just about to hang up my hat. My offer of helping with the testing still stands, but I don't think I've got the skill to code a port.
Comment #9
Wim LeersWhy would you hang up your hat? Just wait for the Drupal 7 port to emerge :) If you want it *now*, then I'm sorry, I can't do that.
Comment #10
JohnWoltman CreditAttribution: JohnWoltman commentedI mean that I can't figure out how to do the port on my own :) so I will have to wait.
Comment #11
YK85 CreditAttribution: YK85 commentedHello everyone,
Just wanted to share that Drupal 7.0 Alpha 2 has been released (http://drupal.org/drupal-7.0-alpha2)
Comment #12
tutumlum CreditAttribution: tutumlum commented+1 subscribing
Comment #13
BenK CreditAttribution: BenK commented@Wim Leers: With Drupal 7 beta right around the corner, I just wanted to check in and see if you had any updated D7 porting plans.
Thanks!
--Ben
Comment #14
Isostar CreditAttribution: Isostar commented+1 subscribing
Comment #15
davidzz CreditAttribution: davidzz commented+1 subscribing. Thanks for all the hard work Mr. Leers!
Comment #16
tsvenson CreditAttribution: tsvenson commented+1 following. Would be sweet to be able to use the linage feature in HS on Drupal 7 among other things.
Comment #17
Unnamed CreditAttribution: Unnamed commented+1 subscribing.
Comment #18
that0n3guy CreditAttribution: that0n3guy commentedsub..
Comment #19
psycho-surfer CreditAttribution: psycho-surfer commented+1 subscribing
Comment #20
zandros CreditAttribution: zandros commentedsubscribing
Comment #21
Danic CreditAttribution: Danic commentedSubscribing …
Comment #22
dgastudio CreditAttribution: dgastudio commentedsubscribe
Comment #23
pcambrasuscribe
Comment #24
V I R U S CreditAttribution: V I R U S commentedSubscribing!
Looking toward using this awesome plugin!
Comment #25
b777 CreditAttribution: b777 commentedsubscribe
Comment #26
indigoblue CreditAttribution: indigoblue commented+1 subscribing Happy to help with D7 testing
Comment #27
gorillaz.f CreditAttribution: gorillaz.f commentedsubscribing
Comment #28
Bevan CreditAttribution: Bevan commentedsubscribe
Comment #29
beautifulmindMe too... subscribing..
Comment #30
Balbo CreditAttribution: Balbo commented+1 sub
Comment #31
anantagati CreditAttribution: anantagati commentedSubscribing and ready for testing.
Comment #32
Wim LeersI won't have time for this module during the academic year (which lasts until the first week of July in Belgium), since I'm in my last master year at Hasselt University.
Therefore, this module will not be ported to Drupal 7 until at least July 2011, possibly even September 2011. I'll be doing an internship (as part of my master) in September 2011— November 2011, and with very high probability, I will work on a D7 port of HS as part of my internship.
However, I don't plan on doing a simple port of HS, I plan on doing a full rewrite. HS has become too messy due to its organic (feature) growth. I've said "yes" too often to new features, resulting in the current mess.
I of course understand that many people would like to see a D7 port of HS sooner than that. I welcome patches and volunteers — I'm definitely open to comaintainership :) So, if you feel like you'd like to comaintain this module, please let me know!
Comment #33
dgastudio CreditAttribution: dgastudio commentedreally bad news...
Comment #34
that0n3guy CreditAttribution: that0n3guy commentedWe could always go in together and just sponsor someone to do a basic (meaning not a rewrite) port. Then when Wim is able he can create a 4.x branch that is the rewrite.
Comment #35
Wim Leers@kervi: Yeah, well, that's not my fault. I've already contributed many hundreds of hours of my free time to this project.
@that0n3guy: Yep :) And there are a few people around who know HS pretty well, so that scenario should definitely be feasible.
Comment #36
dgastudio CreditAttribution: dgastudio commentedwim, i understand you perfectly. Thanks for all!
Comment #37
avo_liao CreditAttribution: avo_liao commentedsuscribing
Comment #38
Bevan CreditAttribution: Bevan commentedI tweeted that Wim is seeking a co-maintainer. Please retweet if you would like to see a straight/simple D7 port of Hierarchical Select sooner rather than later.
Wim; Thank you for communicating this to us so we can help you out.
Comment #39
BenK CreditAttribution: BenK commented@Bevan: Good call. I'll re-tweet.
@Wim Leers: You mentioned that there are a few other people who know HS pretty well. Who are those people? If you can provide the usernames, perhaps we can ping them and see their interest in a D7 port.
--Ben
Comment #40
brianV CreditAttribution: brianV commented+1 subscribe.
Having looked at the HS code, a straight port is not a simple operation by any stretch of the imagination.
FWIW, I am looking forward to seeing Wim's rewrite. HS is a great module as is, but you always learn lessons from your initial implementations that pass on to your next.
Comment #41
avo_liao CreditAttribution: avo_liao commentedWhat are other alternatives for this module in Drupal 7? (while we wait for a D7 version)
Comment #42
dgastudio CreditAttribution: dgastudio commentedno
Comment #43
jenpasch CreditAttribution: jenpasch commentedsubscribing
Comment #44
green monkey CreditAttribution: green monkey commentedsubscribing
Comment #45
denisanokhin CreditAttribution: denisanokhin commentedsubscribing
Comment #46
momper CreditAttribution: momper commentedComment #47
anruethersubscribe...good luck with your studies, Wim!
Comment #48
thomas1977 CreditAttribution: thomas1977 commented+1 subscribing
Comment #49
wa2nlinux CreditAttribution: wa2nlinux commentedsubscribing
Comment #50
verynic CreditAttribution: verynic commentedHow about the port progress?
Comment #51
bryancasler CreditAttribution: bryancasler commentedsubscribe
Comment #52
mastervissie CreditAttribution: mastervissie commentedSubscribing
Comment #53
marcoka CreditAttribution: marcoka commentedsubscribing
Comment #54
Coupon Code Swap CreditAttribution: Coupon Code Swap commentedComment #55
Wim LeersI've got great news: I've got more time than anticipated and PingV will be sponsoring a basic port, that will include the core HS functionality and Taxonomy integration. This will be delivered by February 11 at the latest.
Hurray! :)
Comment #56
beautifulmindFeeling Great to hear!
Thanks.
Comment #57
YK85 CreditAttribution: YK85 commentedGreat news!!
Comment #58
tsvenson CreditAttribution: tsvenson commentedBrilliant news Wim, looking forward to test.
Comment #59
thomas1977 CreditAttribution: thomas1977 commentedGreat to hear that!
Comment #60
tutumlum CreditAttribution: tutumlum commentedGreat!!
Comment #61
dreeds CreditAttribution: dreeds commentedThank you Wim! Thank you PingV!
Comment #62
ropaolle CreditAttribution: ropaolle commentedSubscribe
Comment #63
gael_kl CreditAttribution: gael_kl commentedGreat! subscribing.
Comment #64
Tebb CreditAttribution: Tebb commentedSubscribing.
Comment #65
webankit CreditAttribution: webankit commented+1
Comment #66
zeezhao CreditAttribution: zeezhao commented+1.
Fyi - content_taxonomy has just released a 7.x too.
Comment #67
Wim LeersFortunately, that's barely any significant code. It merely adds one setting. It's mostly code to migrate from D6 to D7. Meaning that I won't need to do anything special to support Content Taxonomy. Which I also most definitely won't do. I will avoid Content Taxonomy support like the plague.
Comment #68
andypostGreat news! @Wim Leers, please, could you explain a bit summary about things that you wanna rewrite? Suppose architectural descriptions is enough.
Comment #69
Wim LeersNo architectural changes for now. This will just be a port to get HS up and running ASAP in D7. Architectural changes will be for the complete rewrite that will hopefully happen in October/November of this year, during my internship :)
Comment #70
andypost@Wim Leers, I mean what changes are planing in architecture? If you explain your thoughts it could be easy to start work on rewrite for volunteers and others to plan usage of this great module
Comment #71
zeezhao CreditAttribution: zeezhao commentedIn relation to #67, does this mean that HS can't be used in cck in D7, as currently being done in D6 via content_taxonomy? Please confirm. Thanks
Comment #72
Wim LeersFor details about HS 4, please see #1052840: HS 4 roadmap. Regarding Content Taxonomy support in D7: Content Taxonomy will no longer exist as such: these fields will be migrated to Drupal's core Taxonomy fields. Hence they will be supported, since CCK is now effectively in core.
Comment #73
klonosStanding by...
Comment #74
MyXelf CreditAttribution: MyXelf commentedSubscribing...
Comment #75
ELC CreditAttribution: ELC commentedOops .. I was starting to port this over but got pulled off it. I'm guessing that you've probably got a lot of work/changes done by now but I've attached the changes I made as a patch, just in case they come in handy.
I upgraded most of the install and uninstall code to use DB:TNG .. and I can't really remember what else. This is against commit a249f45714d6eef338b43100cf482a25e65a7fdc from Fri Oct 8 16:04:55 2010 +0000 and includes the patch from JohnWoltman on January 23, 2010 at 4:06pm.
Alas, I'm guessing it's mostly useless to you now. : / It was in no way working yet.
Does not touching Content Taxonomy support meant that it wont support Taxonomy Fields in D7 core? That seemed like the mostly likely thing to port over to get the D7 taxonomy stuff working.
Comment #76
Wim LeersI'm afraid that's useless now, yes.
And please see http://drupal.org/node/582484#comment-4055304, Taxonomy Fields in D7 core will definitely be supported. That just means Content Taxonomy support can finally die, since Content Taxonomy also won't exist in D7.
Comment #77
Wim LeersSee http://bit.ly/h9Wvz2, as some may have already seen in my tweet. Details will be provided when the patch is posted.
Making progress! :)
Comment #78
Coupon Code Swap CreditAttribution: Coupon Code Swap commentedWonderful news Wim! I'll send a donation your way soon. Thanks for the nice surprise :)
Comment #79
oseldman CreditAttribution: oseldman commentedGreat news. Looking forward to using this in D7. Thanks Wim and thanks PingV!
Comment #80
JJSON CreditAttribution: JJSON commentedSubscribing
Comment #81
dgastudio CreditAttribution: dgastudio commentedany update?
Comment #82
InternetDevels CreditAttribution: InternetDevels commentedsubs
Comment #83
fubhy CreditAttribution: fubhy commentedsubscribing
Comment #84
Nikeev CreditAttribution: Nikeev commentedsubscribing
Comment #85
FiNeX CreditAttribution: FiNeX commentedsubscribing
Comment #86
lancee CreditAttribution: lancee commentedsubscribing
Comment #87
Wim LeersA few days later than promised, but here it is: http://drupal.org/cvs?commit=500248. I did send the result (a zipped variant of this very commit) to PingV on Friday and then took a much needed few days off. I was exhausted, because the port was far from trivial — it was far more complex than I anticipated. As you will see, Drupal 7 brings major improvements, but they are very often severely underdocumented (if they're documented at all).
Please do read the commit message. More detail is provided in the included TODO.txt file.
I'm also pleased to announce that PingV will also sponsor the "dropbox" support for Taxonomy! I will be working on that, starting tomorrow.
As for the other functionality: it is right now unclear how/when/by whom that will be implemented. We'll see how things work out, and I'll keep everybody up-to-date through this issue, as always.
In your testing, please only test what is not marked as still to be done in the TODO.txt file. E.g. if you complain that "create new item" support does not yet work, well … that's not quite helpful. That would only add noise. So please focus on what has been ported and is supposed to work, but doesn't.
A few happy notes:
- HS no longer has to use its own form cache, thanks to improvements in Drupal 7's Forms API.
- HS no longer has to use hackery to be able to render an updated HS in an AJAX callback, thanks to improvements in Drupal 7's Forms API.
- You will most likely never see "Invalid response from server" errors due to other modules not properly including files, since they must now use
form_load_include()
.- HS now needs to use less theme overrides for rendering the form elements it uses, thanks to the introduction of
#theme_wrappers
in Drupal 7.I.e. a lot of code has been thrown out and a lot of problems will now be avoided thanks to the improved infrastructure that Drupal 7 provides. In HS 4, we should therefore be able to focus even more than I anticipated on a better architecture and significantly better performance!
Comment #88
Wim Leersd.o double posted my last follow-up.
Comment #89
klonosGreat news! Thanx Wim for all your hard work. A well-deserved weekend off. Hope you rested as mush as possible ;)
Comment #90
goldlilys CreditAttribution: goldlilys commentedSubscribing
Comment #91
klonos@Wim: ...PS: you double-posted (#87 & #88), but I'm sure you'll see that. The projects front page says:
...I'm sure you meant 2011, but then again this whole comment is not required after the commit ;)
Comment #92
Wim Leers@klonos: Drupal.org is to blame for the double post — nothing I can do about that. You're right about that error on the project page — I've fixed that by linking to follow-up #87 :)
Comment #93
klonosThanx for the prompt reply Wim. I know about d.o 'hiccups', but I just thought you might want to edit the second post and delete its contents - just to keep this issue tidy(er). Waiting for the system to generate the 7.x-3.x-dev (in an hour or so I guess) ;)
Comment #94
klonosFor everyone subscribed here: The 7.x-3.x-dev is out! Start testing people ;)
Comment #95
klonos@Wim: I went on and switched all issues tagged with 'HS4' to the 7.x-3.x-dev version (since there's no 7.x-4.x branch yet). Thought you'd do it yourself at some point, so I did it for you as a thank you for all your hard work (+ it was a graceful way of me subscribing to all current HS4 issues, so I am kept up to date as new features are added and need testing).
PS: Hope I didn't make a poop and caused any mess. Let me know if so and I'll fix it back.
Comment #96
Wim LeersThanks klonos :) I was first shocked: "WHAT THE FUCK HAPPENED HERE?" but then I saw it all made sense. Thanks! :)
Comment #97
Wim LeersIn case it's not yet clear, Taxonomy Views integration has not yet been ported (was reported in #1062278: Fatal error: Call to undefined function _hierarchical_select_setup_js() i, but as per #87, it should be clear this has not yet been ported…).
Comment #98
brianV CreditAttribution: brianV commentedNice work, Wim!
Comment #99
dgastudio CreditAttribution: dgastudio commentedwim, thank u for the explanation.
please, tell me, are u going to make a port of Taxonomy Views integration now, or you going to postpone it until september?
Comment #100
Wim LeersDropbox support has now also been ported, thanks to PingV Creative! See the commit: http://drupal.org/cvs?commit=502452.
I've tagged the 7.x 3.0 alpha 1 release: http://drupal.org/node/1066602.
Comment #101
henryblyth CreditAttribution: henryblyth commentedSubscribing, looking forward to HS4 this fall.
All the best to you with your Masters, Wim :)
H
Comment #102
zeezhao CreditAttribution: zeezhao commentedHi. Had a quick look at the new port. I could not find the way to limit the "Depth of taxonomy tree" which we have in D6 version. Is this not yet ported? Please confirm. Thanks.
Comment #103
Tesmon CreditAttribution: Tesmon commentedsubscribing
Comment #104
klonosComment #105
acoustika CreditAttribution: acoustika commented+1...
Tried to theme me out with css of things this module can do == alot of messy css code... So glad I found this module....
Comment #106
Ericmaster CreditAttribution: Ericmaster commentedsubscribe
Comment #107
rogueturnip CreditAttribution: rogueturnip commentedsubscribe
Comment #108
geerlingguy CreditAttribution: geerlingguy commentedSubscribe.
Comment #109
rogueturnip CreditAttribution: rogueturnip commentedIt's been 2 months since alpha1 was released. ANy updates on the 7.x work?
Comment #110
g76 CreditAttribution: g76 commentedsub
Comment #111
bancarddata CreditAttribution: bancarddata commentedHi, can anyone please tell me where best to get support for this module? Are the general forums a good place? I am new to using this module and am uncertain how to proceed past installation. Both the core module and the HS Taxonomy module are installed and enabled, but beyond that, I do not know how to get the select boxes to show up on a node. The README.TXT file, step 3 of 3, says:
3) If you want to use it for one or more of your vocabularies, go to
admin/content/taxonomy and click the "edit" link for a vocabulary. Now scroll
down and you'll find a whole range of Hierarchical Select settings. All
settings are explained there as well.
I believe however that this is for D6. I have also found the settings I am interested in from the demo page (the first one on the Taxonomy tab) but am not sure what exactly to do with it. Basically, I just want to use Taxonomy as my source for my hierarchy, and render the drop boxes (starting with just the first and then using AJAX to populate each child as selections are made) onto a page whereby I can have users pick their way through the hierarchy, ultimately arriving at a specific set of selections which I can then use to point them to a specific URL.
Can anyone provide any pointers? I am pretty good at figuring things out, if I could just be given some sort of a starting point.
Thanks,
Scott
Comment #112
ian.patterson CreditAttribution: ian.patterson commentedJust encountered a bug in hierarchical_select.module 7.x-3.0-alpha1 in the function _hierarchical_select_hierarchy_enforce_deepest on line 1937.
After checking I discovered that the bug is present in the latest dev as well (line 1936 in dev)
The error occurred during a request for child fields.
The error was message was
using php 5.3.5
I was able to fix the error by changing line 1937 from:
to the lines:
Comment #113
lahode CreditAttribution: lahode commentedHi,
Any new dates of the next release? Still postponed for September 2011?
The "add term option hierarchically" like we had on D6 would be so great. Didn't find any other module doing that.
Cheers
Comment #114
spessex CreditAttribution: spessex commentedsubscribing
Comment #115
spessex CreditAttribution: spessex commentedsubscribing
Comment #116
Anonymous (not verified) CreditAttribution: Anonymous commentedsubscribed
Comment #117
cluthersubscribing
Comment #118
modstore CreditAttribution: modstore commentedsubscribe
Comment #119
aristeides CreditAttribution: aristeides commentedI hate bugging you Wim with "spam" posts, but... any updates on this?
Comment #120
aristeides CreditAttribution: aristeides commentedhas anyone seen this issue? http://drupal.org/node/1211186
Any bright ideas?
Comment #121
marcoscanosubscribe
Comment #122
Wim LeersI can now see that I didn't make this very clear, but:
• please use separate issues from now on to continue the further porting of HS to D7 — e.g.: #1068462: HS Taxonomy: "entity count" support — sponsorship needed, #1068366: Port "save lineage" functionality to D7 + support for multiple parent taxonomies …
• please create separate issues from now on to report bugs in the existing port (but: search before you create a new one, the many duplicate issues overwhelm me and are a waste of time, which means that bugs are fixed slower for everybody) — e.g. #1068070: When multiple HS widgets exist on the same page, and #process order != displayed order: Drupal's JS setting handling breaks HS
So, in summary: please *don't* use this issue anymore for *anything*. It's so incredibly long that it's impossible to work efficiently here. Use separate issues, each with a small area of focus.
You can track what has been ported and what has not yet been ported via the TODO.txt file. This will gradually be updated (and I'll add links to relevant issues) as we make progress.
Thanks!
Comment #123
klonosHey Wim, you might wanna update the issue's summary (by copy-pasting your previous post). I'd do it in order to take some of the burden off of you, but I think its better if the last update had your name (since the "I can now see that I didn't make this very clear..." part has kinda a personal tone and all I mean).
Comment #124
pgingao CreditAttribution: pgingao commentedsubscribe