feat: reset report for a website #46
Labels
No labels
bug
docs
duplicate
enhancement
good first issue
help wanted
question
type: js
type: ruby
unsure
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
dan/siteinspector#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
I started a scan for a website but forgot to remove spelling checks (site in French) so I stopped the scan and modified the configuration but:
Thanks for this very nice application !
Eric Collart
I would second this
version v1.2.0 (Docker)
Confusing for the user, I attempted to 'reset' a report by removing it and readding it.
I now have to 're add it' every time I want to see it!
Steps
expected:
new site, with 0 results ready to press start scan
actual:
existing items where shown, although the number of spellings were going down (I had fixed 6 that were repeated on many pages)
Further comments
When re-visiting the UI from fresh login, the above site is not visible, you have to 're add' it each time and then it shows, with the current status etc.
I think 'reset' should just be in the 'setting' section, and that would delete all entries.
I think to fix the bug I describe, when adding a site, always set public.websites.status text to 'enabled' regardless will solve the issues. manually changing this in the database has 'fixed' the problem of the site not showing unless I re-add it.
Very much want this feature as well, fairly surprised that there's no way to get rid of old entires even when they've been "marked as resolved"!
we need to periodically check the same sites over and over, as their content gets updated
Yes, I've got this problem too. Tried to remove a site and readd it as certain fixed issue didn't go away and thought there was some sort of caching happening. AdamDudley summarised it perfectly.
No way to reset report for a websiteto feat: reset report for a website