Case sensitive

bleen18, sorry #3 doesn't work as expected. I tried to look into it but my drupal module experience is not sufficient to do this task.

side note: I saw that exposed filters in views also supplies the autocomplete widget, I tried to select the autocomplete widget but it doesn't seem to function at all.

Well, for example the following list, the days of the week:
Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday (on separate lines in the form field)
I would like to have te option of case insensitive input, when an user types "mon", Monday should occur and be able to get selected.
This case insensitive setting can be set in the edit tab next to the widget tab.
---
Case sensitive
o Disabled
o Enabled
Case-insensitive queries are implemented using the LOWER() function in combination with the LIKE operator. Note that MySQL might ignore case sensitivity depending on the collation used in your database definition (see Internationalization and Localization chapter in the MySQL manual). If you need case insensitive checks, it is recommended (for performance reasons) to use a case insensitive collation as well (such as utf8_general_ci), rather than disabling the case sensitive option here.
---
By disabling case sensitive I expect the behaviour as I describe above.
Note: Node reference and Term reference have the same behaviour

Finaly I took time to look into this item since it's not working.

First of all on line 133 and 177 of 'autocomplete_widgets.common.inc' $case_sensitive is retrived from $field['widget']['autocomplete_case'], this should be $field['widget']['settings']['autocomplete_case']

Next item is that the use of empty() gives strange behaviour, if Case Sensitive is disabled (=0) then empty() returns true. If Case Sensitive is enabled (=1) then empty() returns false. I don't see the point.

Furthermore I made the following changes to function _autocomplete_widgets_get_options_suggested() to fit my expectations for the function:

function _autocomplete_widgets_get_options_suggested($field, $string = '', $match = 'contains', $keys = NULL, $limit = NULL) {
  $case_sensitive = $field['widget']['settings']['autocomplete_case'];

  $options = explode("\n", $field['widget']['settings']['suggested_values']);
  $options = array_map('trim', $options);
  $options = array_filter($options, 'strlen');

  switch ($match) {
    case 'contains':
    case 'starts_with':
      $matched_options = array();
      
      if (!$case_sensitive) {
        foreach ($options as $option) {
          if ($match == 'contains' && stripos($option, $string) !== FALSE) {
            $matched_options[] = $option;
          }
          elseif ($match == 'starts_with' && stripos($option, $string) === 0) {
            $matched_options[] = $option;
          }
        }
      } else {
        foreach ($options as $option) {
          if ($match == 'contains' && strpos($option, $string) !== FALSE) {
            $matched_options[] = $option;
          }
          elseif ($match == 'starts_with' && strpos($option, $string) === 0) {
            $matched_options[] = $option;
          }
        }
      }
      $options = $matched_options;
      break;
    case 'equals':
      if (in_array($string, $options, TRUE)) {
        $options = array($string);
      }
      break;

  }

  return $options;
}

This returns the case sensitive value in the 'Suggeset values list' even the search has be done case insensitive.

I think that the 'equal case' should also be changed in the same manner, this has not been implemented in code above.

• 7.x-1.0-beta2
• I've use an field with the following properties:
  Text processing: Plain text
  Autocomplete matching: Contains
  Case sensitive: Disabled
  Filter HTML: Disabled
  Suggeset values list: (states of The Netherlands)
  Drenthe
  Flevoland
  Friesland
  Gelderland
  Groningen
  Limburg
  Noord-Brabant
  Noord-Holland
  Overijssel
  Utrecht
  Zeeland
  Zuid-Holland

  When I use an exposed filter in a view, or just entering data in a new or existing node, I would expect the module to return for 'hol' both Noord-Holland and Zuid-Holland. This is not the case with 7.x-1.0-beta2. The reason why I'm expecting this behaviour is that this is the same for taxonomies for example.

• I would love to but I've never applied a patch nor how to do so