Views filter by node title as drop down

I think you want to show all search results in a drop down. I don't think any of the existing modules will be able to do that. You are better off creating a new module/hook for that or you can just modify the views template file.

However, if you are not aware of these techniques I can point you some handbooks.

-Babu
Drupal Projects showcase: http://paramprojects.com/website/drupal-servicesprojects
Promote Drupal with Tshirts/merchandise: http://paramprojects.com/drupalstore

There's a couple of modules in the downloads area that enhance views exposed filters. if one of those doesn't do it, then you should be able to do it with hook_form_views_exposed_form_alter in a little custom module.

I have this same issue and Better Exposed Filters didn't seem to add any kind of functionality for me at all. I'm thinking I have ghosts in my Views install, but does anyone have this working?

As far as I know there is no way to do this with node titles.
Some people want it, but it seems the powers that be have decided it is not a good idea.
http://drupal.org/node/840512
So unless you can code, the only option for a exposed node title filter seems to be a blank text box, which leaves users guessing as to what they might want to search for.

Honestly, I would love it if it could be a standard option. I think it should be up to the site designers to decide if a dropdown is practical or not. After all, many items that do have drop downs, such as taxonomy terms, could also have a huge result set and become impractical for large numbers. But for sites where the number of nodes is small, a dropdown for node titles makes sense.

I am using a view in a block as an alternative. The view lists my node titles and each title is a link to its node.
Not perfect but it works, plus the view can have a filter as well.

Jump Menu appears to be the simple solution, in many cases, but if you want the results in the same views page or block rather than to navigate to a node, it is not sufficient.

My needs target the resulting node content to ajax load on the current page.

Part 1 is to create a jump menu block, and disable submit on it by removing the go button.

#block-views-viewname-block .ctools-jump-menu-button {
	display: none;
}

Part 2 create a second block with exposed filter for node title (or nid)
set to display single item
turn on ajax
use better filters to hide results until filter supplied, (but don't set to required as that will cause required error we don't want)
this also provides default text so block is not hidden.
hide the input filter

#views-exposed-form-viewname-block-1 .views-exposed-widgets input, #views-exposed-form-viewname-block-1 .views-exposed-widgets label {
	visibility: hidden;
	height: 0;	
}

Note hide labels and input, but leave section visible for ajax throbber to show.
use visibility:hidden; not display:none; so form accessible to JS

add JS trigger on jump list combo box select, action copy the title to the exposed filter in second block and trigger submit.

jQuery('.view-viewname #edit-jump').change(function() {
        jQuery('.views-exposed-form-viewname-block-1 #edit-title').val(jQuery.trim(jQuery( this ).find('option:selected').text()));
         jQuery('.views-exposed-form-viewname-block-1 #edit-submit-information-about').click();
      });

Hi,

You can use Views Reference Filter module.

1) First, you have to create a views, select entityreference display, configure it as you want (ex.: Display all node from type article)

2) In your the view where you need to have an exposed filter with pre-populated titles nodes, go to Filter criteria section and then choose a field with reference filter.

I use this module to make an exposed filters list with username which have a specific role in another views that listed all my projects node attached to a user. My mistake, i saw that the version is only for D7.

I was able to create an exposed filter of titles as a dropdown by using the Entity Reference module. You just need to create a seperate view using the Entity Reference display mode giving the items you want to show in the dropdown. Then in your main view in the filter section create a new filter using NID (reference) and select the entity reference view you created in the previous step. This could be used for any entity.

This was for Drupal 7.

For Drupal 7, I found this kind solution

https://stackoverflow.com/questions/3881718/drupal-views-exposed-filter-...

You need to adapt to the entity you wish to handle and adjust the get_value_option as this code does not take the current views filters into account

I reproduce this post here:

You'll need a custom module for that.

I've done this for Drupal 7 this way: create a module, say, views_more_filters, so you have a views_more_filters.info file like this:

name = Views More Filters
description = Additional filters for Views.
core = 7.x

files[] = views_more_filters_handler_filter_author_select.inc
files[] = views_more_filters.views.inc

(file views_more_filters_handler_filter_author_select.inc will contain our filter handler).

A basic views_more_filters.module file:

<?php
/**
 * Implements of hook_views_api().
 */
function views_more_filters_views_api() {
  return array('api' => 3);
}

Then define your filter in views_more_filters.views.inc:

<?php
/**
 * Implements of hook_views_data().
 */
function views_more_filters_views_data() {
  return array(
    'node' => array(
      'author_select' => array(
        'group' => t('Content'),
        'title' => t('Author UID (select list)'),
        'help' => t('Filter by author, choosing from dropdown list.'),
        'filter' => array('handler' => 'views_more_filters_handler_filter_author_select'),
        'real field' => 'uid',
      )
    )
  );
}

Note that we set author_select as a machine name of the filter, defined filter handler ('handler' => 'views_more_filters_handler_filter_author_select') and a field we will filter by ('real field' => 'uid').

Now we need to implement our filter handler. As our filter functions just like default views_handler_filter_in_operator, we simply extend its class in views_more_filters_handler_filter_author_select.inc file:

<?php
/**
 * My custom filter handler
 */
class views_more_filters_handler_filter_author_select extends views_handler_filter_in_operator {

  /**
   * Override parent get_value_options() function.
   *
   * @return
   *   Return the stored values in $this->value_options if someone expects it.
   */
  function get_value_options() {
    $users_list = entity_load('user');

    foreach ($users_list as $user) {
      $users[$user->uid] = $user->name;
    }

    // We don't need Guest user here, so remove it.
    unset($users[0]);

    // Sort by username.
    natsort($users);

    $this->value_options = $users;

    return $users;
  }
}

We haven't had to do much here: just populate options array with a list of our users, the rest is handled by parent class.

For further info see:

• Views API
• Where can I learn about how to create a custom exposed filter for Views 3 and D7? on Drupal Answers
• Demystifying Views API - A developer's guide to integrating with Views
• Sophisticated Views filters, part2 - writing custom filter handler (in Russian, link to Google translator)
• Tutorial: Creating Custom Filters in Views