Making Special:WantedPages update faster

[tall ice]

Is there anywhere I can request to make Special:WantedPages update faster for a bit? I really want to attempt to clean it up as much as it is possible and as quickly as possible before taking a long break. Say once a day would be great instead of once every three days.

[fathom valve]

Updating wiki's is a drain on resources. I doubt that tech want to update it faster for your wiki, because then all wikis want their special:wanted pages, and other cached pages, updated faster.

But this would basically be a question for @mental patrol who can give better answers on this one, than me. (I'm not tech savvy. )

[tall ice]

I understand that. If I were to do that I would want it only done for about a month or even a few weeks. Just long enough to put some stuff together

[mental patrol]

@tall ice the simple answer is no, not really

It also still doesn't work for most wikis fully

[devout crater]

there should still be up to 5000 pages on special:wantedpages. If you can get through all of that in just a few days there's probably a somewhat regular pattern to all of the wantedpages. Also it's not perfect but you can put this in your css

#wikiPreview :where(a, span).new {
    color: red;
    font-style: italic;
    display: block !important;
    font-size: 4em;
    visibility: visible !important;
}
``` to really obviously highlight any broken links when previewing pages. Otherwise, you could potentially use some kind of bot to go through individual pages and find links, then print off the ones that are to nonexistent pages

and if the problem is knowing which links are resolved you can use https://battlecats.miraheze.org/wiki/MediaWiki:Gadget-CacheCheck.js to help

[tall ice]

Yes it goes to 5,000 pages. And I got through it twice. Is there some way to increase the 5,000 page limit

[devout crater]

what's your wiki?

[devout crater]

okay so I'm looking at https://shinto.miraheze.org/wiki/Special:WantedPages?limit=5000&offset=0 and I've added personal css with

.mw-spcontent > ol.special > li {
    display: none;
}

.mw-spcontent > ol.special > li:has(bdi > a.new) {
    display: block;
}

there still seem to be a few pages listed there, but I don't know if that helps, I'm kinda grasping at straws here.

[tall ice]

Sorry for the lack of response. I am a bit confused as to what you actually did just there

[devout crater]

that's just looking at the whole 5000 pages and using some personal css to filter it so you only see the entries that aren't crossed off

[tall ice]

Yeah I guess that's convenient but a lot of the redlinks there are just things I really did not want to make redirects for and just removed all the links to them instead

[fathom valve]

This also creates an error:

[fathom valve]

That's mostly the way to go indeed. Remove the links from the source template

[celest temple]

that's probably because the css linter doesn't know :has()

it's a bit outdated for some reason

[fathom valve]

Try:

    display: none;
}

.mw-spcontent > ol.special > li:has bdi > a.new { 
    display: block;
}```
This doesn't give error messages.

[fathom valve]

Not sure if this is the right way though

[devout crater]

it doesn't give any error messages but it also doesn't work properly. On any modern browser :has will work
also it shouldn't be display:block, it should be ```css
.mw-spcontent > ol.special > li {
display: none;
}

.mw-spcontent > ol.special > li:has(bdi > a.new) {
display: list-item;
}

[fathom valve]

Still an error

[devout crater]

@fathom valve The CSS linter is really outdated, errors don't really mean anything. If your browser is at the latest version then this CSS should work perfectly fine

[tall ice]

Well it was nice that I managed to get the 5,000 new links