Closed (fixed)
Project:
Hierarchical Select
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2012 at 04:21 UTC
Updated:
4 Dec 2014 at 12:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
guypaddock commentedThe attached patch converts HS taxonomy over to using the machine name of vocabularies in config names, instead of the serial vocabulary ID. Since Features just rolls with whatever HS calls the configs, there was no change necessary to the features export code.
This might need additional work to add logic to update the profiles when vocabularies are renamed, but I'll leave that as an open exercise for now.
After applying this patch, you will need to run
update.phpto rename old configs to follow the new convention.Comment #2
guypaddock commentedI found a few more places where the VID was being used instead of the machine name. In addition, I wanted to make sure that HS taxonomy reacts to changes in the vocabulary machine name or deletion of vocabularies.
The attached patch should address all of these concerns, as well as including all of the changes from #1. Use this one instead.
Comment #3
rwilson0429 commentedI received errors when trying to apply the patch.
Comment #4
takki commentedI could apply the patch without errors. I have only tested a content type feature and it works fine. As config id the machine name of the taxonomy is now used. But this needs more testing to be sure there are no issues.
Comment #5
hani.movahed commentedWell the patch almost works. The only thing missing was the actual include of the common.inc in the hierarchical_select.features.inc around line 88. I made a small update to that patch and attached it for review.
Comment #6
ruloweb commented#5 works for me :). Thanks!!!
Comment #7
mrsimonelliott commentedPatch in #5 works for me. Thanks
Comment #8
ryan_courtnage commentedPatch in #5 is working for me as well.
Comment #9
core44 commentedThanks for the patch... this is a very useful addition, will this be committed?
Comment #10
scottrigbyThe patch in #5 allows exportability and features integration, but it's full of spacing and no newline errors - also odd HTML markup inside Doxygen comments. I re-rolled a patch (and attached interdiff to #5) to make this more commit-worthy.
Other places in the module have wonky coding standards issues, but at least this patch ensures no more of those are added by this issue!
Comment #11
mpgeek commented#10 Worked for me. Thanks.
Comment #12
wim leersWow, thanks for cleaning up the mess in #5, scottrigby!
Patch no longer applies, and I have some feedback:
Docs say "_save()", hook is "_update()" -> mismatch!
These wrappers don't make sense to me.
This wrapper makes sense — thanks!
Comment #13
guillaumev commentedNew patch which applies on the latest dev and takes into account the comments made by Wim Leers.
Comment #13.0
guillaumev commentedAdded link.
Comment #14
NaX commented#13 applied cleanly and worked great for me.
Thanks.
Comment #15
one_orange_cat commentedIn case it helps anyone - I have created a new patch building on the patch in #13 but incorporating enhancements to support the request in https://www.drupal.org/node/1280994 to allow separate configurations per field (i.e. not just per vocabulary). The patch is currently available at: https://www.drupal.org/node/1280994#comment-9331047
Comment #17
stefan.r commentedCommitted #13 for now -- the per field patch still needs some further review.
Comment #18
stefan.r commented