Reference value pair module conflict with Taxonomy reference.

Steps to replicate the problem

1. Install reference value pair
2. Add new field as taxonomy reference (save and continue)
3. Type of item to reference: Taxonomy term /or Taxonomy Vocabulary (either one)
4. Save field settings
5. It shows the "reference value pair.
6. In manage field tab, it shows "reference value pair" instead of "Entity reference" as Field Type.

In other words: every time you try to add a taxonomy field, reference value pair take place instead of taxonomy field.

CommentFileSizeAuthor
#4 reference_value_pair-2805783-4.patch1.68 KBmiiimooo

Comments

rivedav created an issue. See original summary.

miiimooo’s picture

Status: Active » Postponed (maintainer needs more info)

Could you re-test this using the dev version?

rivedav’s picture

I tried the dev version an has the same issue. Once you installed, it converts all taxonomy term in a form into "Reference value pair".

miiimooo’s picture

Version: 8.x-1.1 » 8.x-1.x-dev
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new1.68 KB

Attached a patch that fixes the issue. Thanks for spotting this.

  • miiimooo committed 588b7d2 on 8.x-1.x
    Issue #2805783 by miiimooo, rivedav: Reference Value Pair conflict with...
rivedav’s picture

Hi miiimooo,

I installed the module but during configuration, it only references to entity types (content, basic page, etc). I would like to use the module referencing to "vocabulary" (Taxonomy Terms) too.

Updated:

After saving the value pair (with entity "content") you can go back and:
1. Edit the "Type of item to reference" and changed from "content" to "Taxonomy term"
2. Save
3. Go back and edit the "Reference value pair" and then it allows you to select from the "Vocabulary term".

Please revise it in order to avoid this work around

Thanks for your fast response,

Dave

miiimooo’s picture

Status: Needs review » Fixed

I'm setting this to fixed. I see you have created a new issue for your new problem.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.