Closed (fixed)
Project:
Field States UI
Version:
8.x-1.0-rc1
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Oct 2016 at 10:44 UTC
Updated:
9 Jul 2018 at 04:44 UTC
Jump to comment: Most recent

Comments
Comment #2
Huelfe commentedI got the same problem in my field collection issue.
Comment #3
nickdickinsonwilde@Huelfe. Yes, I'm thinking that now that the remaining issue for your field collection is solely this issue.
This issue is a slightly tricky one. Core doesn't give the right hook to alter that point. I'm investigating the best way to work around/fix this without kitten slaughter. I think I have a functional solution but have to do some testing.
Comment #4
nickdickinsonwildeComment #5
nickdickinsonwildeComment #7
nickdickinsonwildeWell I've fixed it I think. Latest dev version and requires a core patch. If using composer you can easily add that to your composer.json. Otherwise manually apply the patch :(.
Comment #8
nickdickinsonwildeNote: you can also if using composer just add
"enable-patching": trueto your composer.json's 'extra' key; in which case the patch will be applied by Field States UI/composer.Comment #9
idebr commentedComposer is picking up the additional patch defined in field_states_ui/composer.json, but fails to apply the patch since it can no longer be applied. The composer project to apply patches (cweagans/composer-patches) currently has a bug where ignoring patches does not work (#112). As a result, our build server now reports the build is unsuccesful.
Can i suggest either:
Considering projects can use different branches for Drupal, I would prefer option 1.
Comment #10
nickdickinsonwildeI was about to do write some tests and do a push to get that patch merged... So I go to the logical tests file and ah what?! There's a test for
hook_field_widget_multivalue_form_alter. That sure didn't exist. Takes a look:added in 8.5.x. So I've closed as duplicate my issue and will be adjusting Field States UI to work with the new hook that got added to core. (I think all I'll have to do is adjust my usage to that name, but I'll test it out).
Comment #12
nickdickinsonwildeImplementation adjusted to use the new core hook.