Closed (outdated)
Project:
Conditional Fields
Version:
7.x-3.x-dev
Component:
Compatibility w/ other modules
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Nov 2010 at 18:38 UTC
Updated:
4 Mar 2024 at 01:48 UTC
Jump to comment: Most recent
Comments
Comment #1
itserich commentedI also have Views, and would like to have some fields appear and others not appear based on Conditional Fields.
I am going to change this to a feature request because there don't seem to be any other issues on it and I am guessing it is not a current feature.
Comment #2
peterpoe commentedWe'll get there someday.
Comment #3
epawel commentedsub!
Comment #4
itqan-2010 commentedyou can use, views dependent filter, I did try it and it is working ..
Comment #5
spidersilk commentedAdding another vote for this feature request.
Specifically, it would be great if there was a way that, when a particular field is shown or hidden on a node page as a result of another field's state, specific views could be exempted from that. For example, if there's an image field on a content type, which is normally used both on the node's page and in a views slideshow on the front page of the site, and the site owner would like to specify for each node whether its image should be used only in the slideshow and not on the page (there is already a boolean field that controls whether the images are used in the slideshow at all, but they would also like to be able to specify some images for use ONLY in the slideshow, not on the page.
I suppose for the time being, I could just rely on the fact that according to the original poster of this issue, fields displayed conditionally will show up in a view no matter what, so I can just worry about hiding the field on the pages where it needs to be hidden, but it would be nice to have the flexibility of being able to control the settings for specific views.
Comment #6
dqdThanks 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.