The warrior (and some other) item set pages (like Battlegear of Wrath) specify categories in a unique and idiosyncratic method: Within the <onlyinclude> section for the tooltip is an <includeonly> section which includes a category specification.
It works, there's valid reasons to do it that way, etc. Different discussion.
More than once, people editing these pages have made some trivial change ... which for inexplicable reasons moved the category specification to the bottom of the page.
It's been different users, and it's been a highly specific change that one would not expect, particularly from a low volume/new editor. Thus, I am suspecting that this edit is being caused by the wiki "fast category" interface.
Can someone trivially determine if this is the case?
And if it is the case, what can be done to stop the unwanted and unexpected category code meddling?
--Eirik Ratcatcher (talk) 21:00, February 10, 2010 (UTC)
- I'm pretty sure it's a "feature" of CategorySelect. --k_d3 03:42, February 17, 2010 (UTC)
- We can disable it if that's the consensus, I for one have it turned off for me personally and don't think that "feature" helps at all. --Pcj (T•C) 03:54, February 17, 2010 (UTC)
- I've turned it off personally as well, for pretty much the same reason. As some people apparently use it, I'd prefer to see CategorySelect corrected, over having it removed. Simply disabling it means everything that builds on it later would have to be disabled as well. Having seen optional features become mandatory on occasion, such things cause me to twitch. This case should easily be discoverable as a context issue. (IE "within includeonly + onlyinclude" != "within onlyinclude") Alternately, some method of flagging could be created, such that the CategorySelect feature would ignore it. --Eirik Ratcatcher (talk) 20:23, February 17, 2010 (UTC)