[choward]

Hi Ernest!

1. Unfortunately, text fields are the more significant concern. The static list to generate a dropdown isn’t a big deal and from the performance perspective is probably a good idea. We’d like to allow a filter for presenters and series names whose dropdowns would look like this:

Null || [Empty]
Presenter One || Presenter One
Presenter Two || Presenter Two
Presenter Three || Presenter Three

The default selection would always be [Empty] which would allow searching across the full post set, but any other selection would offer a filter. I figured this was built into the custom field search so that when the search is triggered if the value selected is equal to “null” it bypasses the filter altogether, otherwise it performs the search as usual with the filter.

2. Credentials are attached as requested. Let me know if you have any issues accessing the server.

[choward]

Hi Ernest,

Thanks for the great plugin.

1. Basically, our problem is that we have a custom fields for data like ‘event’ and ‘presenter’. The custom field dropdown works fine if we simply have a list of ‘2014,2015,2016’ but that forces the search to one of the values which breaks the search for users that don’t use the advanced options. I assumed there was a ‘null’ value that basically told the search to ignore the field, basically if “null || (blank)” which would automatically be bypassed. If that’s not possible, we’ll have to think of a more creative way to implement that type of filter.

2. Credentials attached for our development server. This is probably something simple that we’re overlooking.

Thanks again for the help!
Charles

[choward]

The second image is attached. ‘Add another file’ didn’t seem to like Chrome 47.

[Author]

Posts