How to hide the referenced node title in select list with view

just ran into this and would like an answer as well, It seems the node reference's view feature is the issue here but one needs to select a view and only show what that view is querying not the extra "title foobar" bit.

you just need to setup the view correctly. if you're seeing "title" you need to remove the label from the field name. if you're seeing double values you need to remove the duplicate fields.

ah, you're right. talked to yched on irc and the solution is to exposed a views display and let you create your own fields.

Actually, this is not related to whether the custom view display we use is exposed or not. The fact is that we explicitly force the node title (or user name, in the case of userrefernce fields) to be present as a field in the view.
_nodereference_potential_references_views() :

    // We do need title field, so add it if not present (unlikely, but...)
    $fields = $view->get_items('field', $display);
    if (!isset($fields['title'])) {
      $view->add_item($display, 'field', 'node', 'title');
    }

This is because the 'autocomplete' widget needs the node title to fill in "node_title [nid:node_id]" in the textfield when the user picks an autocomplete suggestion. Granted, the other widgets (select, radios/checkboxes) don't need it, but the code workflow is pretty tight and it's hard to do special cases. I don't really see a workaround here.

yched, well that pretty much defeats most of the value of using views for the lists... are you sure we couldn't come up with some kind of a work around?

That sounds a little dramatic - it's been like that since 4.7, and I think the feature found a few use cases since then, even with that limitation ;-)

Well, thinking about it a little more, there should be a way to have a db field (node title) retrieved in the views results but not being part of the actual views 'fields' . If this can be done (and if we have a consistent way to get it from the results, whether 'node: title' field is actually present in the view or not), then we could alleviate that constraint.

Then, of course, comes the usual issue of changing the behavior of existing setups : after upgrading to cck 2.2, the titles disappear from my noderef widgets if my view didn't have the title field so far.

The Views UI has a checkbox for field options that are needed in the query but not to be displayed. Maybe there is some way to use that to include the field but not display it. I haven't looked into the Views code to see where that comes in to play or exactly what it would change in these results.

True, I forgot that option. This might be a solution - if the 'title' field is not present, we force it in as 'not displayed'.
Patch anyone ? :-)

yched, i think the option you're thinking of is "exclude from display"... but if the ajax needs the title to match nids then that seems like the bigger stumbling block...

Marked #350174: get rid of Title from autocomplete referenced field when using Views as duplicated.

Title is added in _nodereference_potential_references_views():

    // We do need title field, so add it if not present (unlikely, but...)
    $fields = $view->get_items('field', $display);
    if (!isset($fields['title'])) {
      $view->add_item($display, 'field', 'node', 'title');
    }

I've commented out this line:

$view->add_item($display, 'field', 'node', 'title');

Then it's throwing the error:

Fatal error: Cannot access empty property in cck\includes\views\handlers\content_plugin_style_php_array_ac.inc on line 24

That's:

    foreach ($sets as $title => $records) {
      foreach ($records as $label => $row) {
        $results[$row->{$base_field}] = array(
          'title' => $row->{$title_field_alias},
          'rendered' => $this->row_plugin->render($row),
        );
      }
    }

So I've changed this code to:

    foreach ($sets as $title => $records) {
      foreach ($records as $label => $row) {
        if (isset($row->{$title_field_alias})) {
          $results[$row->{$base_field}]['title'] = $row->{$title_field_alias};
        }
        $results[$row->{$base_field}]['rendered'] = $this->row_plugin->render($row);
      }
    }

And it's seems to work fine.

I don't care for now that there is no title in the field (#7). It should be replaced with some field as well.
I think without Title in autocomplete list is looks better than without Title in the field.
In some cases some people don't use title at all, because auto_nodetitle doesn't generate titles from the fields during creation, so for most of the cases Title contain rubbish.

Probably most of the people who wanted to hide the Title now will be interested with searching string in CCK fields as well via autocomplete:
Here is related case: #375690: Nodereference autocomplete doesn't match all of view's fields

thank you kenorb. so I'm curious if the dev version, or next drop of cck will include something to be able to drop the title via the UI?

I've been able to work around this issue:

1) add the title field to your view
2) check the 'exclude from display' box for that field

That should do it until the bug is fixed.

Jeff

I don't see this being an issue with latest -dev for me anymore.

I'm not sure if you talking on the same thing, but I don't see much changes and title is still hardcoded.

But I think #16 is a good solution.
I've tested and it's working.
The only issue is to replace the title of field somehow after selected some record.
If somebody will have better solution, please re-open it.

Changing the code to force-add the 'title' field as 'excluded' if it is not present in the original view seems an easy change.
My main worry is that it will break existing sites that might implicitly rely on the fact that the title was added no matter what.

yched: it can be solve in similar way to this one:
http://drupal.org/node/375690#comment-1263293
Most of the views used as argument have no fields defined because are not supported, so if there are some fields defined, we can replace them instead of default title. I think it will not break existing websites.

I fail to see how this is a fix.
Sample break case :
I created a view with filters and sorts to define the nodes that are refererencable in my field_noderef field. I didn't even have to bother about adding actual fields to the view, it works out of the box (displaying titles). Then I install the new version of CCK that behaves as decribed in #20. Nothing displays in my select box or in the autocompletion results anymore => I have to manually edit the view and add the title.

I don't think there's a workaround.

#16 worked perfect for me.

#16 is not a workaround re-opening since cck fields are still being appended with '- Title: Name' after content.

I know this issue is pretty old, but I used the following workaround: include the "Node: Title" in the fields, remove the label (i.e. make it blank), check the "rewrite the output of this field", and enter a "[space]" (i.e. a blank character). This works pretty well except for the " - " at the end of the select option when displayed.

I don't under comment #25. i have successfully applied the work-around in #16.

I'm using a nodereference with a select list. By applying #16, I no longer see 'title: name' after the field values.

I second this, it works fine.

#16 works for me as well.

I suspect that while the title is hardcoded, it does not unset any existing array configuring how to handle the Title field options (for a first use of the Title as a views field). As such, if you mark it as excluded or rewritten (or really any of the options not specifically configured in _nodereference_potential_references_views), they will carry over into the view shown in the widget.

#16 works fine for me too. It's definitely a workaround I can live with. So if it's really a problem to fix this problem at the root, I guess it should at least be documented. A simple additional bullet in the hints when choosing a view as source of the select items would be sufficient. And for those who don't RTFM: well they can still ask google and find this issue. :-)

#16 is the right way to do this.

Thanks jlevy, #16 works like a charm !

jlevy,
your solution #16 is simple and perfect!

#16 works perfectly.

http://drupal.org/node/230298 Marked as Duplicate

Changing title for better findability.

Thanks jlevy

#16 worked for me too. Thanks!

#16 didn't work for me but #26 did. I just added the "Node: Title" field and chose "rewrite output" then put a SPACE, like literally hit the space bar and it removed the title from the display.

EDIT: also works by just rewriting the output and inputting nothing in the field, rather than adding a SPACE

I did #16 too. Thanks.

But only for the title??....I wish to hide any kind of referenced view fields by selecting in the configured fields CCK UI...did I make clear?...