Existing website_page_error records retained after path exclusion is added #42

New issue

Closed

opened 2023-07-26 09:17:52 +02:00 by poxblossom · 1 comment

poxblossom commented

2023-07-26 09:17:52 +02:00

(Migrated from github.com)

An initial scan of the site will produce numerous false positive spelling error alerts for the German pages, for example, suggesting that "unser" be corrected to "under". Adding an exclusion rule ("/de/*) prevents the pages from being scanned again, however, any previously-logged errors are retained and shown in future reports.

Marking issues as resolved isn't a solution as the false positives are still shown in reports. I also can't mark the error as a permanent false positive in case I allow actual errors to slip through undetected ("unser" could well be a typo in English as "s" and "d" are adjacent).

Is there something in the interface I'm missing that addresses this or is my only recourse to manually edit the database each time?

My situation is this: I have a website authored in English that provides translations via an automated service which prepends the page URL with a language code, so www.mysite.com/about-us becomes www.mysite.com/de/about-us when viewed in German. An initial scan of the site will produce numerous false positive spelling error alerts for the German pages, for example, suggesting that "unser" be corrected to "under". Adding an exclusion rule ("/de/*) prevents the pages from being scanned again, however, any previously-logged errors are retained and shown in future reports. Marking issues as resolved isn't a solution as the false positives are still shown in reports. I also can't mark the error as a permanent false positive in case I allow actual errors to slip through undetected ("unser" could well be a typo in English as "s" and "d" are adjacent). Is there something in the interface I'm missing that addresses this or is my only recourse to manually edit the database each time?