bug? “URL contains” targeting fails to accept comma-separated arguments

  • Resolved Joe Westcott

    (@redredweb)


    4 years, 11 months ago

    Hi, there seems to be a bug in the current version of Boxzilla, when it comes to URL-based targeting.

    If one chooses URL-based targeting with “contains” as the rule and a comma-separated list of relative URLs, then the box in question will only appear at the first URL.

    For example, if the rule is this:

    if URL > contains > /about/,/providers/

    … then the box will show up on the /about/ page but not the /providers/ page.

    I’ve recreated this problem on a stock installation of WordPress 5.3.1, running the Twenty Twelve theme and no plugins except for Boxzilla version 3.2.18.

    Here is a screenshot of the rule that fails to work as expected:

    https://www.dropbox.com/s/128xwp02sh60l0a/boxzilla-url-contain-targeting-bug-example-rule.jpg?dl=0

    Thank you for any help!

    -Joe

    • This topic was modified 4 years, 11 months ago by Joe Westcott.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey Joe,

    Please change the rules to just keep “about,providers” which are the page slug and test again.

    Thread Starter Joe Westcott

    (@redredweb)

    Hi Harish, if I switch to “Page is” and I use page slugs, those work as expected, but I have pages such as /about/us/ on this test site, and that’s why I’m trying to use “URL contains” matching instead.

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey Joe,

    In that case, can you add the PAGE id as that would work the best?

    Thread Starter Joe Westcott

    (@redredweb)

    Is there a way to target a comma-separated list of URLs, instead of manually maintaining a list of page IDs?

    It seems that this functionality exists in Boxzilla as the “if URL contains” targeting, except for this bug where only the first URL works.

    Plugin Author Danny van Kooten

    (@dvankooten)

    Hi Joe,

    That does sound like an issue. I will take a closer look at it, but please allow me a few days as my wife is currently 9 days overdue for delivering our daughter so I don’t have much time these days.

    It’s on my list though – so it won’t be forgotten!

    Thread Starter Joe Westcott

    (@redredweb)

    Best of luck, Danny!

    Plugin Author Danny van Kooten

    (@dvankooten)

    Thank you Joe, everything turned out fine, a healthy daughter was born a few hours after my last comment in this thread!

    Also I’ve just released version 3.2.19 in which the issue you reported is fixed. Great catch, thank you for bringing it to our attention!

    Thread Starter Joe Westcott

    (@redredweb)

    Congrats on your newest family member, Danny!

    And thank you for the fix! I just confirmed that comma-separated URL targets now work as expected. Thank you!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘bug? “URL contains” targeting fails to accept comma-separated arguments’ is closed to new replies.