fieldnamefilter and fieldvaluefilter not working?

  • Hi, great plugin,

    I’m trying to get the fieldnamefilter and fieldvaluefilter to work, but to no avail. Even a simple [userlist list=2 fieldnamefilter=first_name fieldvaluefilter=Maarten] yields no results while a [userlist list=2 filter=show first_name=Maarten] does work flawlessly.

    Just to be clear, I don’t need to use the fieldnamefilter/fieldvaluefilter for this instance, I wanted to use it elsewhere. But I can’t get it to work in any case though. Is it perhaps a functionality that got phased out in recent versions of the plugin?

    I tried it on a relatively clean wordpress 3.5.2 install as well as on the plugin demo page using the parameters in the url:
    https://directories.wpusersplugin.com/simple-user-list/?fieldnamefilter=display_name&fieldvaluefilter=auser

    it doesn’t work either way unfortunately.

    still loving the plugin, thanks,

    Maarten

    https://www.ads-software.com/extend/plugins/amr-users/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter maarteno

    (@maarteno)

    See https://www.ads-software.com/support/topic/parameters-work-in-url-not-in-shortcode?replies=6#post-4370453 for a solution to the shortcode issue. Didn’t check the URL version.

    Plugin Author anmari

    (@anmari)

    Hi Maarteno,

    I want to check that you are using fieldname/value filters because you absolutely have to.

    They are only meant for situations where people have squashed TWO or more different fields into one ‘column’ and then still want to filter on a SINGLE field that is part of the ‘column’. Most people do NOT have this situation.

    Unfortunately the use came about historically. Plugin started off being a pure admin list with csv and only expecting ONE field per column. Then a few folks wanted to create psuedo fields in a column by combining existing fields. THEN they still wanted to filter on the single field, part of the ‘column’. Technically it is a less than an ideal solution wrt to the way that the cache is stored – inefficient. The cache storage mechanism will be redone one day removing the need for so called ‘field’ filtering at all. (Very hard to indicate by language the difference.)

    For most folks, the plain ‘column value’ filter should be all they ever need.

    In addition S2 member has a less than ideal user field implementation. They do not use use meta as intended. It makes it hard to extract data and even harder to filter, compared to implementations that use the user meta as wp intended.
    See https://wpusersplugin.com/3086/user-lists-and-filtering-with-s2member-fields/

    Note: Field (as in partial column) filtering was not intended to be used in the shortcode.

    I will look through your notes in the other posts, and see if your suggestions make sense to implement given my comments above.

    Thread Starter maarteno

    (@maarteno)

    Hi, didn’t really need the fieldnamefilter/fieldvaluefilter if it wasn’t for the fact that you (seemingly?) can’t use hyphens in shortcode attribute names and the column-name I want to access unfortunately has a hyphen in it.

    I agree on the problem with the user-field implementation in S2Member, I might indeed use a different field for this particular functionality to circumvent this problem and speed up the caching. I tried it using Advanced Custom Fields, but my implementation was again a bit too complex as I pre-filled that field from a taxonomy. Getting to the actual values is more complex in that case and requires a custom piece of code querying the database.

    Thanks for the feedback!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘fieldnamefilter and fieldvaluefilter not working?’ is closed to new replies.