I would like the link to appear in more than one term, but it becomes unclassified in the Links Page if the taxonomy field for the Web Links vocab is used in a Field Collection within the Web Links content type rather than in a regular field in the Web Links content type.

CommentFileSizeAuthor
#4 screenshot2.JPG38.98 KBJudyPJHsu
#4 screenshot1.JPG55.12 KBJudyPJHsu
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

JudyPJHsu created an issue. See original summary.

GStegemann’s picture

GStegemann CreditAttribution: GStegemann as a volunteer commented

As a first guess I would say that such a configuration is not considered in the Web Links implementation.

Can you provide for a screenshot of your Web Links content type setup and how the links appear on the Links page.

@Jonathan: do you have an idea what causes this behaviour?

jonathan1055’s picture

jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented

I don't know. When JudyPJHsu posts the screenshots we can try to replicate the behaviour.

JudyPJHsu’s picture

JudyPJHsu CreditAttribution: JudyPJHsu commented
FileSize
screenshot1.JPG55.12 KB
screenshot2.JPG38.98 KB

I've attached 2 screenshots. First is the default setup of the Web Links content type. Then I added a Field Collection and used the same Web Links vocabulary for the term reference field field_subject. The default setup works fine fine, but any term selected via field_subject is uncategorized in the Links Page. I'm guessing the Links Page is hardcoded to work with taxonomy_weblinks field AND the Web Links vocabulary rather than just with the Web Links vocabulary.

I just realized that I can set taxonomy_weblinks to have more than one term, but I need it to be paired with a separate description that's unique to each link. I think I'll use a second vocabulary list and work around it that way.

GStegemann’s picture

GStegemann CreditAttribution: GStegemann as a volunteer commented

Many thanks for your screenshots.

I'm guessing the Links Page is hardcoded to work with taxonomy_weblinks field AND the Web Links vocabulary rather than just with the Web Links vocabulary.

Not really. The code uses the 'taxonomy_term_reference' field which matches the assigned Vocabulary from the Settings page. So using a field collection will not work on the Links Page.

I just realized that I can set taxonomy_weblinks to have more than one term,

What do you mean by 'to have more than one term'?

I think I'll use a second vocabulary list and work around it that way.

Possible. Can you explain in more detail what you intend to do and what you expect from Web Links?

JudyPJHsu’s picture

JudyPJHsu CreditAttribution: JudyPJHsu commented

What do you mean by 'to have more than one term'?

I wanted the link to be listed under more than one group. I can set taxonomy_weblinks field to accept multiple inputs, but I can't have a different description field for each input unless I put it in a Field Collection.

Possible. Can you explain in more detail what you intend to do and what you expect from Web Links?

I'd like the link to be listed in the Links Page of more than one group, with a description of how it is useful under the context of that group. For example, a site like http://www.worldtimebuddy.com/, I might put in under a group 'World Clocks' and then have a description of how it can be used to display world times. On the other hand, I might have a group called 'US Time Zones' and describe how the site can convert the US time zones PDT to EDT.

As you said indicated earlier, it appears that Web Links just isn't made to work with a Field Collection. That's fine. I like the link checking and click count features so I am still going to use it, but otherwise it works better for me to create my own views pages rather than using the Links Pages.

GStegemann’s picture

GStegemann CreditAttribution: GStegemann as a volunteer commented

Sorry, for responding so late.

I wanted the link to be listed under more than one group.

Interesting idea. I never tried to do that.

I'd like the link to be listed in the Links Page of more than one group, with a description of how it is useful under the context of that group.

I see.

it appears that Web Links just isn't made to work with a Field Collection

Yes, Web Links is not Field Collection aware. And I'm not sure if it ever will be.

but otherwise it works better for me to create my own views pages rather than using the Links Pages

If that is OK for you I will keep this issue open for a while and close it at some time when no one has time and an idea how to implement Field Collection support in Web Links.