Nothing Loads on the Filter Page about davt HOT 3 CLOSED

Let me try to respond in order:

It looks like it just might not have found any matches to show. Each time it says "no match" in the console log, it means it tested a diff and didn't find any bad words to match against. Depending on the time of day, it might just take a long time to show anything. The fact that it's showing all of those things means the script is functioning, and just not finding anything.

As for the talk/history, that's because the script actually loads on every Wikipedia page, and starts processing and displaying diffs when you're on any page where the URL contains "DAVT/Filter". You'll notice the same behavior in Lupin's tool when you go to the Filter Recent Changes page, then click View History.

There's nothing to see on the history page anyway (the page has one edit which is an HTML comment to generate a blank page). If you think it would be helpful, I can have the script put a link to the correct talk page at the top above "pause updates". Alternatively, I might be able to change the filter page to a variation of Special:BlankPage, like the RTRC gadget does, so it's clearer to users that there is no content to see on talk/history/etc.

The "errors" you pasted are actually just the script logging its actions (mostly for debugging purposes). In the JavaScript console in Chrome, you can hold control (or possibly command? dunno Macs very well) and click "Logs" at the bottom, and it will suppress the log messages and only show actual errors. It's the same key-click-combo you use to select multiple items from a list, whatever that is on a Mac.

Regarding the pause/resume function, it definitely works in the version I'm ready to release tonight or tomorrow, or at least it does in Firefox on a PC. After I update the tool to 0.1.0 tonight or tomorrow, please try the pause/resume functionality again, and let me know if it still doesn't work -- and if it doesn't, see if there are any errors showing in the JavaScript console when you click pause or resume.

The badwords list is basically the same as the one used for Lupin's tool, but I removed all of the image-specific strings (I hadn't seen Lupin's tool match on an image file name in years). It's at [[User:Darkwind/DAVT/badwords]]. The list for Lupin's tool is at [[User:Lupin/badwords]].

from davt.

Hey there, I see on the Wikipedia article that the last stable release was published today (11/11/13). However, the Anti-Vandal tool still says "This page was last modified on 29 October 2013 at 22:56." The pause button still functions as it did before (I click "Pause updates" and it shows "Resume updates", however I can't click back to "Pause updates").

On the Chrome console:

Here's the 'Logs' page:
Still latest, pulling full content index.php:183
Revision is 581216556 index.php:256
Still latest, pulling full content index.php:279
Testing for a match index.php:202
Downloading editor properties index.php:330
Editor whitelisted index.php:358
Diff queue length is: 94 index.php:364
Revision is 581216555 index.php:256
Still latest, pulling full content index.php:279
Downloading editor properties index.php:330
Editor whitelisted index.php:358
Diff queue length is: 93 index.php:364
Revision is 581216554 index.php:256
Still latest, pulling full content index.php:279
Downloading editor properties index.php:330
Testing for a match index.php:369

Here's the 'Errors' page:
Uncaught TypeError: Cannot call method 'test' of null index.php:205
Uncaught TypeError: Cannot call method 'test' of null index.php:379

I was about to write that it wasn't working but the AHAH! It started working, sick :D

Thanks :)
-busterroni

from davt.

The page [[User:Darkwind/DAVT.js]] is what gets updated when I make changes to the tool/code. The page [[User:Darkwind/DAVT/Filter]] does not get edited, like, ever, so its last update time will never change.

As for the pause/resume thing, the button is functional - if you watch the logs, when you click pause, it stops, and when you click resume, it resumes -- but the text of the button does not appear to change; that's a bug. I'll get a fix out shortly.

The uncaught typeErrors are confusing -- there's no reason codewise why that should be happening. I encountered the same errors, and when I refreshed the page, they didn't happen the next time. It may have something to do with how long it takes Wikipedia to return the page containing the bad word list. If it times out, it may cause those errors.

from davt.