Control Settings available for the Query String is not working correctly

  • Resolved ruen06

    (@ruen06)


    1 year, 7 months ago

    param=value | Query parameter with a specific value.
    param=* | Query parameter with a wildcard value. (i.e. the value could be anything)
    param | Query parameter with no value. Operates the same as a wildcard value.

    I was trying to add the params (Location+1, Location+2, Location+3, Location+4, Location+5) with different values as a control such as Location+1=1/Location+1=0. But the plugin only recognises the param itself and ignores the value.

    • This topic was modified 1 year, 7 months ago by ruen06.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Nick Diego

    (@ndiego)

    Hi @ruen06,

    Thanks for reaching out. Would you be able to share the exact parameter you are entering into the text field in the Query String control? I don’t seem to be able to replicate it on my end using Location+1=1. See the screenshot below.

    The block displays when the URL ends in ?Location+1=1 and is hidden when the URL ends in ?Location+1=0. Any additional info you can provide would be helpful in diagnosing the issue.

    Thanks,
    Nick

    Thread Starter ruen06

    (@ruen06)

    Hi, kindly check this video https://www.awesomescreenshot.com/video/16774216?key=494e725a5d777927e17628ac2d96e47d

    The URL of the result page in the video is https://yoursite.com/?Location+1=1&Location+2=1&Location+3=1&Location+4=1&Location+5=1

    The message is displayed correctly when Location+1=0&Location+2=0&Location+3=0&Location+4=0&Location+5=0

    The section I used is REQUIRED QUERIES?(ALL)

    Plugin Author Nick Diego

    (@ndiego)

    Thanks for this additional info. I was able to replicate the issue and will be investigating it further.

    Best,
    Nick

    Plugin Author Nick Diego

    (@ndiego)

    Hi @ruen06,

    I have identified the bug. If you change the parameter values from 0 to another other value, everything should work correctly. Let me know if you continue experience issues after changing the value.

    A fix will be applied in the next release to address this bug, which should come out at the end of next week.

    Best,
    Nick

    Plugin Author Nick Diego

    (@ndiego)

    I apologize for the delay on this, but the newly released version 3.0.3 corrects this bug. Thanks again for reporting!

    Best,
    Nick

    Thread Starter ruen06

    (@ruen06)

    Hi, sorry to get back now. I am using version 3.1.1, but the query string control doesn’t support param value =0.

    Currently, I have used the preset and chose the “hide if this preset applies” to achieve the condition I want. Can you look into it?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Control Settings available for the Query String is not working correctly’ is closed to new replies.