Problem with custom query parameter

[jasonl99]

I have a set up where I allow the user to search by multiple tags, plus use the default text search provided by selectize. When both are filled out, it works great. here's the json sent to the server:

{
       "queries" => {
         "search" => "test"
          "order_type" => [
            [0] "retail"
            ]
  },
        "page" => "1",
     "perPage" => "10",
      "offset" => "0",
      "action" => "index",
  "controller" => "admin/entities",
      "format" => "json"
}

Note the "order_type" array of tags.

However, if the user uses only the tag function, and leaves the search blank, the 'processing' indicator does not go away (though the data loads fine). Here's what the json looks like sent to the server:

{
       "queries" => {
          "order_type" => [
            [0] "retail"
            ]
  },
        "page" => "1",
     "perPage" => "10",
      "offset" => "0",
      "action" => "index",
  "controller" => "admin/entities",
      "format" => "json"
}

Note that there is no 'search' query. Selectize is having a problem with this in this area of code:

   // For queries, we're going to handle each possible query parameter individually here instead of
          // handling the entire queries object below, since we need to make sure that this is a query controlled by dynatable.
          if (attr == "queries" && data[label]) {
            var queries = settings.inputs.queries || [],
                inputQueries = $.makeArray(queries.map(function() { return $(this).attr('name') }));

            if (settings.features.search) { inputQueries.push('search'); }

            for (var i = 0, len = inputQueries.length; i < len; i++) {
              var attr = inputQueries[i];
              if (data[label][attr]) {
                if (typeof urlOptions[label] === 'undefined') { urlOptions[label] = {}; }
                urlOptions[label][attr] = data[label][attr];
              } else {
                delete urlOptions[label][attr];
              }
            }
            continue;
          }

The delete UrlOptions[label][attr] has an issue because there is not a search attribute in the json sent to the server in this circumstance.

[jasonl99]

Quick update, I fixed it by disabling the built-in search (features search: false), and adding my own with an id of search. Probably a better idea anyway, since there's more complicated layout to deal with using multiple search options.

[jasonl99]

One quick comment that's related. If I pre-select items a select/option list, those options are not sent as queries (everything remains unfiltered). For example, in the order_type example above, consider the following input which is added as a query item to dynatable:

<select class='dynatable-query-item' multi>
  <option>Wholesale</option>
  <option selected>Retail</option>
</select>

When the page loads, the item is selected as expected, but dynatable acts as if nothing has been selected.

[JangoSteve]

Good point about the multi-select. To be honest, I've never tried using dynatable's queries functionality with a multi-select, so I'm not surprised there's some weirdness with it. Definitely something I'll want to fix. Any chance you could create a JSFiddle example with your multi-select input by modifying this one?

[jasonl99]

I have updated the jsFiddle...

http://jsfiddle.net/ty3b7/8/

But it's not working at all. In my case, I'm using an ajax data source, so the server is doing the filtering. But this one is failing in a similar way - the 'processing...' message stays up.