Closed (fixed)
Project:
Multistep (D7)
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Aug 2009 at 15:08 UTC
Updated:
22 Sep 2009 at 13:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
vkareh commentedTry this patch. When editing the content type information, you will be able to select a step for each individual taxonomy vocabulary. Let me know if it works for you. Use the latest development snapshot.
Comment #2
arbel commentedthanks for the patch, but it seems not to work.
I see the new fields but the extra non cck fields always appear on the first step.
I applied the patch manually but I'm pretty sure I didn't miss anything. I also ran the update.php.
i'll try setting it up on a new content type.
thanks again for the effort and great work.
Comment #3
arbel commentedI think I found the issue in this line here:
$form[$field_name]['tags'][$vid]['#access'] = FALSE;If you take out the ['tags'] it works, not sure what it does....
but i've found another issue, if the vocabulary that is hidden, is a required field, you can't move onto the next step.
Idan
Comment #4
arbel commentedok, small update, my test was using a multiple select taxonomy field using the hierarchical select module. with this setting I'm guessing with multiple select taxonomy you the ['tags'] isn't correct. but when using a taxanomy field set to tags, then it is required. I also did a check about the required field, and it worked great with your patch - setting the access to false makes it ignore the required field.
the question is how do you change the code to get it to work with multi select taxonomy, how to solve the issue with the required field.
another issue, not completely related is that the hierarchical select doesn't work on any step other than the first, when you try to add a selection, it simply doesn't add and sometimes gives a javascript error of some sort. I have no idea how to debug this. where should I open an issue for this, here or in the hierarchical select module?
thanks
Comment #5
vkareh commentedThanks for all your feedback, arbel!
You made me realize that the
['tags']array only works for tags. I fixed it so that it also takes into account non-tag taxonomy fields. Test the new patch and let me know if you find any other problems.Note: open a new issue here for the hierarchical select issue with a description on how your hierarchical select field is configured. I think it might be due to the way multistep handles field permissions, but I'm not entirely sure.
Comment #6
arbel commentedthanks for the patch.
I've noticed that the multiple selection isn't saved if you move to the next step and then back to the step with the multiple select.
other than that it looks like it's working great, other than the fact the the heirarchal select isn't working when on any step other than the first - opened and issue on this.
Idan
Comment #7
vkareh commentedUpdated the patch to remove the empty "Vocabularies" fieldgroup that appears whenever you have multiple taxonomy fields of different types across multiple steps.
I cannot seem to replicate the problem with the multiple selection not being stored. Try doing it without the hierarchical select and let me know if it works that way. It's all being saved properly for me.
Comment #8
vkareh commentedPatch committed to development snapshot.