Not sure if this is an issue with Field Collections or Hierarchical Select, so will post in both in the hope that someone else is experiencing the same issue and the community can assist.

FC = Field Collection Group
F1 = text field
F2 = Hierarchical Select

Now I add a new item:

FC1
- F1 = 1111
- F2 = Banana

FC2
- F1 = 2222
- F2 = Apple

FC3
- F1 = 3333
- F2 = Pear

Save and this works. PROBLEM is when I remove an item, for example if I remove FC2 you would expect the result to be:

FC1
- F1 = 1111
- F2 = Banana

FC3
- F1 = 3333
- F2 = Pear

Instead the result is:

FC1
- F1 = 1111
- F2 = Banana

FC3
- F1 = 3333
- F2 = Apple (not Pear)

Whilst the correct text field item is removed, it's always the last (newest) Hierarchical Select field that is removed regardless of which field collection group is deleted.

I hope this makes sense and the wonderful developers that maintain this module may be able to shed some light and hopefully patch. I'll add this same issue to HS.

Thanks in advance!

Comments

Stephen Ollman’s picture

You can try for yourself here: http://drupal7.opcit.net.au/node/add/fchs to see what I mean.

This is a D7.26 install using Filed Collection 7.x-1.0-beta5 and Hierarchical Select 7.x-3.0-alpha6.

Stephen Ollman’s picture

Has no one else experienced this issue?

jmuzz’s picture

Status: Active » Postponed (maintainer needs more info)

I did some tests using the hierarchical select widget on a taxonomy term reference and I saw a problem but I wasn't able to reproduce what you describe.

3 different field collections sharing the same fields: Worked fine

Cardinality 3 field collection: Worked fine

Unlimited cardinality field collection:
- Add link on node: Worked fine.
- Embedded: Adding more items messed up the hierarchical select widget and I was not able to create the node properly using the embedded form.

Can you provide more details about your case?

jmuzz’s picture

I don't know if this is related to what you are seeing, but there is a patch on a Hierarchecal Select issue about compatibility with Field Collections.

https://drupal.org/node/1349868

Stephen Ollman’s picture

Patch #25 made no difference in this case.

Issue still exists in its basic and patched form.

Can I please confirm that someone else is seeing the issue as well using the link: http://drupal7.opcit.net.au/node/add/fchs

Use this link and replicate what is stated in the original post as far as adding items. Save and then try and remove any item other than the last one. Whilst it looks like it works have a look at the last taxonomy element. its incorrect.

jmuzz’s picture

I tried it again following the steps in the original issue report using the latest versions and everything seemed to work correctly.

Is this still happening for anybody? If so how can it be duplicated?

The provided link shows an access denied message.

jmuzz’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)