Hi, yesterday I tried to download and install "Conditional Fields".
I tried to install it in a drupal 8.1.10 instance and 8.2.6 too.
My test was this (in a new standard installation of drupal):
1) I created a taxonomy term with "value1", "value2","value3".
2) Edit "Article content type" adding a new field of my new taxonomy type and set, on "manage form display", to show it as "select list"
3) on "manage dependencies" I added a dependency:
- on "add new dependency" I select "Image", "controlled by" by my new field (taxonomy), "the dependent field is.. visible" , "when the dependee.. has value", then "Add dependency"
- on the new screen on "insert value from widget" I select "value2"
- I leave all the other options unchanged
4) Go into "add content" of type article, "image field" is not visible then I try to select the "value2" from select list and nothing happens.
Doesn't work with drupal 8.1.10 and Drupal 8.2.6 too.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

girtri created an issue. See original summary.

beltofte’s picture

Title: Doesn't work on Drupal 8 » Configuration saved wrong in input mode widget
Component: User interface » Code
FileSize
1.45 KB
149.8 KB

When adding or editing a conditional field and choose "Values input mode" = "Insert value from widget", is the value chosen in the widget not saved correct and expected in the configuration object.

Instead of being saved as value_form (as expected in http://cgit.drupalcode.org/conditional_fields/tree/conditional_fields.ap...), is it saved as e.g. field_tags). See the attached screenshot.

The attached patch try to solve this. It will probably break if the field widget allow multiple values configured. Have not been able to track down how the values should be saved in config if multiple values are selected.

heshanlk’s picture

Status: Active » Reviewed & tested by the community

This appeared to fix the issue.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 2: fix_value_form_issue.patch, failed testing.

OlgaRabodzei’s picture

Status: Needs work » Fixed

Was fixed in the last release(2017-Apr-07). Can someone check it, please?

Status: Fixed » Closed (fixed)

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