shows many page URLs containing "list" which should be returned in the first call.
Is there currently another way to achieve the segmentation behavior expected when using the pageUrl segment with the =@ contains operator? Thanks.
(In ) refs #2727 =@ and !@ for pageUrl / pageTitle segments
The segmentation mechanism with callbacks was built for comparing against a single ID, which only works for == and !=. I tried to introduce dynamic SQL sub-expression with as little impact on the existing system as possible.
Btw, I changed the "action not found"-value from -1 to -100 because we were discussing to use -1 for something else. When we do, we would most likely forget to change the value. ;)
(In ) Fixes #2727
IMPLEMENTATION NOTES / limitations:
Nice update, makes it much cleaner!
What makes you think the second limitaion exists? Page title und page URL are both action-based reports/segments, so the output should be as expected. It tried it on my local box and it works.
Thanks for feedback, reopening to investigate further my claim
You're right, it WORKS! :)