I Have set up some conditional fields that work fine in the standard node display. I have set them so they are only hidden on the node display (ie I have checked "Don't use javascript. Fields are only hidden on node view").

I am using content permissions and the permission is set to view for the controlled field (which is a text field containing a phone number) but not for the controlling field (an on/off check box for the user to indicate whether to display the phone number or not.

As I say, all works fine on the node display and I can hide the controlled field as required but if I use a panel page to display the node the controlled field is not hidden.

the node in question is set as a content profile but I get the same result with a content type not set as a profile.

I'm not sure if this is the expected behaviour when using panels with conditional fields or whether I need to pursue another route to achieve what I'm after.

Comments

azmchichi’s picture

azmchichi commented
Issue tags: +panels, +conditional fields

subscribing

vlooivlerke’s picture

vlooivlerke commented
Version: 6.x-2.0-beta2 » 7.x-3.x-dev
Category: Support request » Bug report
Priority: Normal » Major
Issue summary: View changes

I have tried this with 3 fresh installs and can confirm this is a bug. When using panels visibility rules are ignored.
Could this be a module weight problem?
This module is broken when used with panels that's why I mark it a major.
Please change to what is considered appropriate.

To reproduce make a check box select list and make a text field dependant. Put the dependant field in a panel and no matter what you try it will not get hidden.
Pleas help

jweirather’s picture

jweirather commented

Was there ever any good solution for this? I'll be facing this issue soon and am trying to look at options.

Thanks!

VenDG’s picture

VenDG commented

Also wondering if anyone ever solved this issue?

jweirather’s picture

jweirather commented

@VenDG: In my install (maintained and current), conditional_fields are working exactly as expected in panels, and they have worked from the beginning.

I had thought it might be a problem, which is why I posted to/followed this thread, but when I went to try it, it just worked.

I would note that the conditions I'm using are very simple, and that the forms themselves are not overly complex, or multi-page, etc. That said, I am able to individually place conditional fields into panels regions, and the basic show/hide functionality is working properly.

jweirather’s picture

jweirather commented
Status: Active » Postponed (maintainer needs more info)

If you're having a specific issue, please follow up with the details.

For now, in the interest of housekeeping, I'm taking the liberty of setting this to "need more info".

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Priority: Major » Normal
Status: Postponed (maintainer needs more info) » 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.