Using the Rules module, I'm trying to collect and store user profile info during checkout with Drupal Commerce. I've made a custom checkout pane (using Fieldgroup and Commerce Fieldgroup Panes) that will gather user info and save it inside of their user profile.

What I'd like to do is have a checkbox in my custom pane that asks if the user's profile info is the same as their billing info. With Conditional Fields, I was able to make a dependency that asks if the checkbox is checked, to hide the profile fields (picture attached). But on checkout, the fields do not hide as expected. I've tested to make sure the module works with another basic content type that is unrelated to Drupal Commerce, and it works perfectly. The fields hide as the checkbox is selected.

Does Conditional Fields have a problem working with:

a) Fieldgroup?
b) Commerce Fieldgroup Panes?
c) Is it related with this issue: http://drupal.org/node/1270268 ?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

trevorkjorlien’s picture

Oops. Forgot to attach the image...

geek-merlin’s picture

Status: Active » Closed (duplicate)

looks like a dup of #1270268: Conditional Fields does not work with Commerce checkout profile fields - feel free to reopen when this is wrong

geek-merlin’s picture

Status: Closed (duplicate) » Active

rethinking, i'm not so sure...

geek-merlin’s picture

Title: Does not work with custom Commerce fieldgroup panes » Conditional Fields does not work with custom Commerce fieldgroup panes
trevorkjorlien’s picture

I tried running the patch in #1270268 with the current dev version, but the patch failed, presumably because it was for an older release.

JMOmandown’s picture

this is still an issue. The conditional fields work fine with field groups and on other content types. Fields in separate panes fail work with conditionals even when on the same page (if in same field group pane, things work fine).

dqd’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Thanks for the report and all the efforts in here. But due to inactivity in this issue for some years and because of the upcoming EOL of Drupal 7, I will close this issue on the way by cleaning up the issue queue.

Feel free to re-open as "Needs review" if you found a solution or have a patch to be reported to help others on this outdated version.

If you think this issue or missing feature should be addressed in a newer Drupal core 8 and above compatible version of this project, then please file a new issue to the latest dev.