Is it possible to have 'conditional fields' in views?

Related: What if the field value is null? I would like to exclude it from the list. I would have thought I could add a filter to exclude it from the view, but since I have chosen this field to display in the view, it has disappeared from the list of available filter fields. Why is this? Anyone suggest a workaround?

I'm looking for exactly the same thing and bumped into this thread.

I have a (grid block) view where long node titles look bad. So I've defined an optional field for that content type called "short title". I want my view to display the short title field if it is not empty, else the node title.

Any pointers?

You are going to have to override the view's template at some level to add custom "if this is empty then show this" logic, you can find out the info from click the "Theme: Information" link for the view you are editing. This can get tricky as it depends on the 'Style' of the view (table, grid, etc) and possible the associated row style of the view.

Solved, FYI:

Note that I am a Drupal and PHP newbie, so use this at your own risk. Works for me.

Here is my example:

• For content type "story", I have a field "Short title" (field_short_title).
• This field is not required.
• In my view, I want to show the short title if the user has filled in that field, else I want to show the regular node title.

1. Install the computed field module.
2. In your content type, add a new field. For type, you will be able to pick "computed field". Let's call it "field_computed_short_title"
3. Edit that new computed field. In "Computed code", I put without the surrounding "<?php ... ?>"
   

   if (!$node->nid) {
   node_save($node);
   }
   if (!$node->field_short_title['0']['value']) {
   $node_field[0]['value'] = check_plain($node->title);
   }
   else {
   $node_field[0]['value'] = check_plain($node->field_short_title[0]['value']);
   }
   

   The first if-statement is needed because in a newly edited node, the node title is empty and would return null.

4. Leave "Display Format" at its default. Tick "Display this field". Choose data type "varchar" and data length "100" (as you wish). Save field.
5. Now use this field_computed_short_title in your view.

Notes:
The computed field will have no value for existing nodes, so nothing will show up in your view. You will need to update those (edit and save). Does anyone have a good way to update multiple nodes?

I have a site setup (d6.17, cck, views, conditional fields, views attach - plenty of other modules) (system setup: linux OS, apache 5.2.x, plenty of php_memory, mysql)
The owner wants to allow for users to add a taxonomy term, without 'tagging' (this almost always results in content forking).
So my solution is that the content type has a conditional field which is ticked yes/no box (other*) when ticked (*yes) then there is a webform displayed with a submission for a new taxonomy term. I was thinking of embedding the webform with views attach to the certain content types (*edit page: build modes).

Then in theory the user will be able to submit a new taxonomy term if the relevant one is not available.

Can anyone advise on a better solution?

Views If Then module or something. This: http://drupal.org/node/945268 looks like the same issue, as does this: http://drupal.org/node/869286. I'm not adept enough yet to build a module, but it seems like there's enough demand for sure.

I understand that field output in Views 2 cannot be managed conditionally in the UI. Can it in Views 3 (D7)? So far I’ve hit a wall, suggesting it cannot.

I’m building a D7 site for our German Shepherd rescue group and need to solve the problem of presenting fields conditionally within views. Here are the bones of the scenario:

Query pulls all unadopted dogs from DB to display in a mini-pane. Conditional fields needed:

• If ‘date_added’ field is less than 21 days ago, display “new” icon or text.
• If ‘living_with’ field is not Foster OR Permanent Foster OR Family OR Shelter, display “Foster Needed” icon or text.
• Both fields are required in CCK, so testing for NULL or replacing a NULL is not an issue

Managing both of these manually is possible but would offend the DB gods.

My thought was to do another query to identify the new dogs, for example, and join that with the unadopted dogs query to add the necessary ‘new’ field. Same with ‘Foster Needed’. I guess that’s not what Views Relationships is for, huh. Is there some way to accomplish this that I’m not seeing?

In searching I’ve come across a PHP solutions outlined in this thread and the CSS solution in jakepyne’s tutorial. I have even considered the terrifying power (power for a noob like me to screw up) of Computed Field and Views PHP. I guess what I’m hoping for is the moron solution as, until I started with Drupal, I thought PHP was that new drug the kids were on and CSS was the acronym for and embarrassing skin condition.

Any help with a simple solution to what seems to be a common problem would be greatly appreciated. I am hoping that D7 offers some functionality in this area that I simply haven’t stumbled upon.

This might come in handy: http://drupal.org/project/views_conditional

If there are two fields that you only want one of them to show => add both fields to views, and then exclude second one from display (check "Exclude from display"). Now in first field go to "No results behavior" setting and enter the "Replacement pattern" of second link. (Just remember that second field should be upper that first one in list in order to see it as Replacement)
Now every thing's OK. Whenever first link is null the second appears instead...