Forums Forums Search & Filter Pro Return results which match specific post meta data.

Tagged: 

Viewing 10 posts - 1 through 10 (of 10 total)
  • Trevor
    #246258
    This reply has been marked as private.
    Anonymous
    #246283
    This reply has been marked as private.
    Trevor
    #246466
    This reply has been marked as private.
    Anonymous
    #246506

    Hello, Trevor,

    is this field necessary?

    We would like to have all posts listed that have versionsnummer 1, which we have already defined in the settings. Then no further field is necessary for selection, is it?

    Look: https://next.touch2be.de/index.php/s/T83ELBjCQKB4Njg

    Many greetings and thank you very much for your help!

    Tobias

    Trevor
    #246791
    This reply has been marked as private.
    Anonymous
    #246833
    This reply has been marked as private.
    Trevor
    #247135
    This reply has been marked as private.
    Ross Moderator
    #247193
    This reply has been marked as private.
    Anonymous
    #247264

    Hi Ross,

    thanks for your help!

    = didn’t bring any results, so we used Like.

    To your questions:
    1) Yes, we have a backup.
    2) Yes, please as much testing as necessary. You are welcome to make changes.

    Thanks a lot!

    Tobias

    Ross Moderator
    #247363

    Hi Tobias

    Ok so I figured out the issue..

    There are two things occuring that are causing this:

    1) The post meta tab of our search form, is just an admin UI for properties you can use in a WP_Query

    2) When you use a checkbox field in ACF, the user can select multiple choices, which means the data is serialised – so for a meta field, instead of a plain value like 2, you have this array(1,2,3)

    Now the issue here is, a WordPress query can’t filter this data using a meta query, because the data is serialised (an array)

    And we don’t provide a way around this, even though we analyse the post meta to build our cache and use the serialised data correctly in our searches.

    The only way to get that to work would be to conver the field into a single value type field, like a radio (you would have to re-save your existing posts to update the post meta) – then you can use the post meta tab to do the things you need.

    Now we’ve identified this, I will add it to our v3 roadmap, so the post meta tab will in future be able ot do things like this.

    I hope that clarifies things a bit, and it’s a shame we don’t have a solution in place!

    Thanks

Viewing 10 posts - 1 through 10 (of 10 total)