All The Tropes Wiki Project, Part XXVII

[GethN7]

Bad news, folks... Bot runs do something bad to the database, and generate false-positive results in DPL lists.

Evidence: Both this list and this list were down to a couple-dozen pages before somebody did a bot run. Now they're so long that they overflow the DPL lists.

I propose that we not allow bot runs at all unless there's an emergency that needs to be fixed immediately (as in "the wiki has been served with a court order" immediately)... and, even then, somebody needs to go in afterwards and manually edit every page touched by the bot run so that the database is updated correctly.

Not the fault of the bot jobbing.

What we have is the templates applying the correct category on a backend level, which saves valuable processing cycles as opposed to manual place, as we bundle it in the templates for those specific pages

https://allthetropes.org/w/index.php?tit...artwarming

This puts the appropriate CSS in the background to display the page appropriately, and if you check the bottom of the template in edit view, it includes the proper category when said CSS is applied as well. I suggest looking for all pages that link to the Heartwarming Template if you want more accurate results. Same for Nightmare Fuel or any other page we use the backend template load method for.

Re-reading this...

That isn't what's happening. All I'm doing is making a miscellaneous edit to the pages in order to get the categories to actually apply to the page. I'm not defining them manually, and I don't want to define them manually - that goes against all of the automation that I've been adding to the wiki over the years.

Somehow, categories that existed are were previously being read by DPL are no longer being read by DPL. The templates were on the pages and remain on the pages. Why do I need to edit the page in order to get them to show up?

Hey, Rob, I've been looking at the stuff you've been doing this afternoon, and I think a lot of the pages you've tagged with "trope needs examples" might be better served as just noting that they're a definition page that doesn't get examples.  We have sufficient precedent for that.

This is related - all I did was add a category to an existing tag. The pages didn't show up in the category until after manual edits of the pages... which should not have been necessary.

If this is "applying the correct category on a backend level", then the backend needs to communicate with the frontend.

Then that sounds like a DPL regression, not a problem we can fix. If DPL was reading this fine, then it broke, DPL is broke.