Hello,

I am trying to use Content Taxonomy Term Tree but on the node edit page the terms do not expand.
I have created the vocabulary 'example' with terms as shown in attachment images.

1.png - image of term tree not expanding on node edit. A and B have been clicked and should be showing the child terms (indicated by ' - ' for expanded) but no child terms are shown.

2.png - image of http://www.example.com/admin/content/node-type/profile/fields/field_example showing that term tree is selected in Manage Fields setting for the Content Taxonomy field

3.png - image of Taxonomy Manager setting of this vocabulary showing the complete hierarchy of the terms that should be showing on the node edit page.

Would someone be able to comment on this issue? Your help would be very much appreciated.

Thank you very much in advance!

CommentFileSizeAuthor
3.png19.9 KBBilmar
2.png4.43 KBBilmar
1.png8.06 KBBilmar

Comments

Bilmar’s picture

Bilmar commented

Hello, I was wondering if anyone can confirm this and have any advice for a fix?
I am still seeing this issue. Thanks

sabesneit’s picture

sabesneit commented

Hi, i'm having the same issue here.

When the tree is rendered, the minus/plus buttons are switching when clicked but it does not expending or collapsing the branch.

mh86’s picture

mh86 commented
Status: Active » Postponed (maintainer needs more info)

This seems to be an multilingual vocabularies issue.
as far as I can see from your screenshots, you are using the i18n module. which translation mode are you using for your vocabulary? and are all terms of the same language?

Bilmar’s picture

Bilmar commented
Status: Postponed (maintainer needs more info) » Active

I am using Localize terms: Terms are common for all languages, but their name and description may be localized and Language negotiation：Path prefix only.

If I use anything other than the term tree I am able to see all the terms in each language on the path prefix, but when I use term tree I get the issue above.

Please let me know if more information is needed. Thank you

mh86’s picture

mh86 commented

Thanks for the fast response.
It seems like there are still some issues with the tree widget and multilingual terms. The thing is, that i18n does not rewrite any query under the /admin path, so it's going to display fine in the Taxonomy Manager, but on the node add form, i18n might want to change something which results in a strange behaviour in the tree widget.
Until now, I wasn't really working on the multilingual support for the tree widget in content taxonomy (different to the taxonomy manager), so I would suggest you to switch to the select list or take a look at the code in the tree widget to identify the problem.

Bilmar’s picture

Bilmar commented

Thank you for the quick reply.
I understand. I unfortunately do not have any programming skills and so will use the checkboxes option to achieve multilingual support.

Many thanks

jbfelix’s picture

jbfelix commented

Hello,

I have the same issue, i18n is enabled, but i don't use translation for this vocabulary (option: None. No multilingual options for this vocabulary)

Strange ...