Forums › Forums › Search & Filter Pro › ACF number fields values are not auto detected as min and max values

Tagged: ,

Viewing 10 posts - 1 through 10 (of 18 total)
1 2
  • Anonymous
    (Private)  November 1, 2019 at 1:47 pm #225294

    Hi,

    Just bought Search & Filter Pro and created my first search form, I face an issue I didn’t manage to solve by myself.
    I created several custom fields using ACF and I used those custom fields to build my search form.
    Two of my custom fields are set as “Number” fields in ACF, fields names are starting_year and end_year and what I would like to achieve is to get a numerical range slider from starting_year to end_year with min and max values auto-detected.
    I tried to configure my search form to do so but the range slider min and max values doesn’t match the available values in the numerical ACF fields, what I get as values are 0.

    Could you please help me on this ?

    Trevor
    (Private)  November 1, 2019 at 1:50 pm #225295

    Do the meta key names you use in the Form UI start with an _ underscore? If so, look for ones that do not.

    Anonymous
    (Private)  November 4, 2019 at 10:43 am #225364

    No they don’t

    Trevor
    (Private)  November 4, 2019 at 5:08 pm #225416
    This reply has been marked as private.
    Anonymous
    (Private)  November 4, 2019 at 8:12 pm #225427
    This reply has been marked as private.
    Trevor
    (Private)  November 4, 2019 at 9:12 pm #225442
    This reply has been marked as private.
    Anonymous
    (Private)  November 4, 2019 at 10:07 pm #225447
    This reply has been marked as private.
    Anonymous
    (Private)  November 5, 2019 at 5:51 pm #225870
    This reply has been marked as private.
    Ross Moderator
    (Private)  November 6, 2019 at 1:37 pm #225913
    This reply has been marked as private.
    Anonymous
    (Private)  December 9, 2019 at 3:42 pm #228699

    Hi Ross,

    Sorry for my late response, I was abroad and busy on something else.
    Indeed the site is already online but yet no one is browsing this for now because it’s still in development.
    Unfortunately we don’t have any staging or dev environment at disposal for this projet.
    I was wondering why you couldn’t reproduce the issue on your side first, make an appropriate patch and just update our server afterwards?
    Maybe that is what you planned to do but it was not very clear to me how you were going to work

    I would be more comfortable this way, anyway in my opinion the scope of these correctives are quite restrained therefore the risk also, innit ?

    Many thanks for your help.

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 18 total)
1 2