Checking for CSS filter that doesn't YET exist, but SHOULD in the future? #1554
Unanswered
dumdedumda
asked this question in
Q&A
Replies: 1 comment
-
It's still running and checking even with that error. I have a few that do the same thing until the filter shows up. Once it shows up you'll receive an alert. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In (#962 (comment)) @dgtlmoon highlighted the following:
I've tried pasting a CSS filter which doesn't yet exist (e.g. '.on-sale') -- but should in the future -- in the "CSS/JSONPath/JQ/XPath Filters" box but get the following error "Warning, no filters were found, no change detection ran."
Is there a method to force CD to continue checking until the filter is found? Any tips?
Edit: Ticking "[ ] Ignore status codes (process non-2xx status codes as normal)" still results in the above error (i.e., "warning, no filters were found...".
Beta Was this translation helpful? Give feedback.
All reactions