• Resolved tophr

    (@tophr)


    Hello, I’ve been using the following code to filter a get_top call to the Slimstat API for some time:
    wp_slimstat_db::init('content_id does_not_match 4|2808|2782|2784|2781|2783|2780&&&limit_results equals 10');

    However, I’ve noticed Slimstat is now ignoring everything after the 4 so all the other filtered IDs are included in the list. The same thing happens when trying to use the shortcode version instead:
    [slimstat f='top' w='post_link']content_type equals page&&&content_id does_not_match 4|2808|2782|2784|2781|2783|2780&&&limit_results equals 6[/slimstat]

    • This topic was modified 6 years, 10 months ago by tophr.
Viewing 1 replies (of 1 total)
  • Plugin Author Jason Crouse

    (@coolmann)

    Hi @tophr,

    good catch. It was a regression bug introduced not so long ago. We will fix it in the next update, which is scheduled to be released in about 10 days.

    Thank you!
    Jason

Viewing 1 replies (of 1 total)
  • The topic ‘regex OR (|) no longer working with does_not_match’ is closed to new replies.