Forums › Forums › Search & Filter Pro › Bug Report: auto-detect number & Revolution Slider

Viewing 3 posts - 1 through 3 (of 3 total)
  • Trevor
    (Private)  April 20, 2017 at 9:17 am #103978

    Are you able to open the browser console and see if there are an javascript errors (in red)? This web page shows how to use many tools for diagnosis:

    https://css-tricks.com/debugging-tips-tricks/#more-253010

    I wonder whether the meta key field contains non-numeric data, as that would cause an error in the auto detect range code.

    Anonymous
    (Private)  April 20, 2017 at 3:44 pm #104045

    You are correct. For some reason, the number field I created in ACF is saving two meta keys. The one I was using “_current_price” was storing a string like “field_203530573504”. The other “current_price” (without the leading underscore) was storing the actual number input. I was using the first key and that caused the problem. Now the auto detect is working.

    Thank you for your insight 😀

    Trevor
    (Private)  April 20, 2017 at 4:00 pm #104047

    ACF always does this, so make sure not to use the one beginning with _

    I will mark this resolved.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)