The exposed filter for a string has a maximum of 128 characters, this should be unlimited since the value searching for might have a length up to an infinity number of characters (in theory offcourse :-) ).

The restriction can be removed by editing views/handlers/views_handler_filter_string.inc line 180:

      $form['value'] = array(
        '#type' => 'textfield',
        '#title' => t('Value'),
        '#size' => 30,
        '#default_value' => $this->value,
      );

Should be:

      $form['value'] = array(
        '#type' => 'textfield',
        '#title' => t('Value'),
        '#size' => 30,
        '#default_value' => $this->value,
        '#maxlength' => null,
      );
CommentFileSizeAuthor
#4 views_62_fix.patch498 bytesrv0
#2 views.patch499 bytesmarkwittens
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

Can you provide a patch for it?

markwittens’s picture

FileSize
499 bytes

Uploaded patch.

iamjon’s picture

Status: Active » Needs review

Changing status.

rv0’s picture

FileSize
498 bytes

null should be NULL

did a quick edit of the patch file

dawehner’s picture

Status: Needs review » Needs work
+++ views_handler_filter_string.inc	2011-01-26 13:42:55.000000000 +0100
@@ -182,6 +182,7 @@ class views_handler_filter_string extend
+        '#maxlength' => NULL,

It would be really helpful to document what this line means.

dawehner’s picture

The rest of the patch looks fine, but i guess as 6.x-2.x is on a only critical bug-fixes status this will only land in 6.x-3.x and 7.x-3.x

rv0’s picture

additionally, i've got an exposed filter somewhere that takes usernames (comma seperated, ajax autocomplete).. it's not working there.

EDIT: This required a similar fix in views_handler_filter_user_name.inc

MustangGB’s picture

Issue summary: View changes
Status: Needs work » Closed (won't fix)