Minecraft Wiki
Register
Advertisement
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
This project is defunct. 
Consider looking for related projects to help. If you feel this defunct project may be worth reviving, please discuss with related projects first.

Introduction

Ever since the move to a new host, I've noticed a lot of pages either started or already had, some improperly closed html tags, such as code, div and small. This has the effect, due to the way wiki pages are designed, that the entire navigation bar at the top of each page gets messed up. Either the font changes, or it is strangely positioned overlapping the page content area. This is actually convenient behavior, because we want to fix these invalid tags, and we can spot them in one glance by just looking at the navigation bar.

Only some pages have improperly closed tags, like a <div> tag before a table to apply some extra style to it, and then forgetting to add </div> to close it again. Or sometimes an editor forgets a slash somewhere: <code>some code<code>. Sadly the only way to find these and other similarly invalid tags, is to go through all pages and manually glancing over each one.

Why?

The reason this happens is because the navigation bar (along with the wiki logo, the page footer and other stuff) actually comes after the page content in the markup of the page. So if an element in the page content is not properly closed, as its formatting continues on until it hits a proper close tag or the end of the page, the formatting of the invalid tag will also affect and mess up the navigation bar (and the rest of the page).

I think we only need to go through all pages for this project once, so no pages could promote invalid markup for new pages or editors anymore. When we're done, we simply have to guard not inadvertently repeating these issues.

Notice that helping out with this project can award you certain (secret) achievements. Consider that a small bonus for doing tedious tasks, if you'd care about that.

How to start?

To participate in this project if you're up for this, add your signature to the members list below with ~~~. I've already listed and prepared all applicable sets of pages below. When you want to start checking an unchecked set of pages, change it to {{c|In progress}} and append your name before you begin, so the line would look like this: {{c|In progress}} page set (page count) ~~~.

Note: do not start checking a set of pages someone else is already doing, as the task of going through them is very tedious and you don't want to go through pages that have already been checked as part of someone else's set. Also for the same reason only take up on one set at a time so others can work on their set without interference.

I finished a set, whats next?

If you've successfully finished checking a set of pages, thanks a lot for your effort! Change your set of pages to {{c|Done}} and move the line into the checked section at the bottom. Don't move subsets on their own however, until the whole relevant namespace is finished. You could then choose to start on the next set of pages if you still want.

To-do

  • To start checking pages in a page set (be sure you've marked it as described above), click on its link.
  • All relevant pages are listed (ignore redirects), and you can start opening and checking them all one by one.
    • I recommend to open a handful or more at once in new tabs (middle-click or CTRL-click) to reduce time clicking stuff.
  • Check the navigation bar at the top of each page to see if it shows odd formatting or odd positioning as described above.
  • If it does, edit the full page (not just the relevant section), so you can catch all issues of the page in one edit.
  • Now inspect where the issue starts (using preview), fix it and hit preview again.
  • Repeat inspection if the navigation bar is still not fixed.
  • Otherwise finish your edit with summary "fixed unclosed div-element" or similar and mark as minor.

You may need to further inspect a transcluded subpage if the issue doesn't start in the source of your page, but these may very well be in the same page set you're already checking. If for some reason you don't know how to fix one of your pages, don't hesitate to discuss it.

Note: you may prefer to use CTRL+F in your browser to highlight all occurances of a tag in the editor, if you know which tag it is.

Unchecked page sets

These pages still need to be checked for invalid tags.

  • File namespace (total 11718 pages, divided into subsets by next/previous navlinks)
  1.  Done subset 1 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  2.  Done subset 2 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  3.  Done subset 3 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  4.  Done subset 4 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  5.  Done subset 5 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  6.  Done subset 6 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  7.  Done subset 7 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  8.  Done subset 8 (345 pages, no issues) – Jack McKalling [ Jack McKalling's User page Jack McKalling's Talk page Jack McKalling's Contributions ]
  9.  Done subset 9 (345 pages, no issues) - Play logo
  10.  Done subset 10 (345 pages, no issues) - Sagessylu (discuss | edits)
  11.  Done subset 11 (345 pages, no issues) -Asarta (talk)
  12.  Done subset 12 (345 pages, no issues) -Asarta (talk)
  13.  In progress subset 13 (345 pages) Asarta (Talk)
  14.  Done subset 14 (345 pages) - Sagessylu (discuss | edits)
  15.  In progress subset 15 (345 pages) AndrewDaGuy (talk)
  16.  In progress subset 16 (345 pages) K1401986 (talk)
  17.  Done subset 17 (345 pages, 1 fix) TreeIsLife (talk)
  18.  In progress subset 18 (345 pages) Avidd (talk)
  19.  Not started subset 19 (345 pages)
  20.  Not started subset 20 (345 pages)
  21.  Not started subset 21 (345 pages)
  22.  Not started subset 22 (345 pages)
  23.  Not started subset 23 (345 pages)
  24.  Not started subset 24 (345 pages)
  25.  Not started subset 25 (345 pages)
  26.  Not started subset 26 (345 pages)
  27.  Not started subset 27 (345 pages)
  28.  Not started subset 28 (345 pages)
  29.  Not started subset 29 (345 pages)
  30.  Not started subset 30 (345 pages)
  31.  Not started subset 31 (345 pages)
  32.  Not started subset 32 (345 pages)
  33.  Not started subset 33 (345 pages)
  34.  Not started subset 34 (338 pages)

Final page set when all sets are finished:

  •  Not started New pages since this project (automatic listing)

Unsure about these?

Unsure we need to check these page sets. Please discuss on the talk page.

  •  Not started Talk namespace (1798 pages)
  •  Not started User namespace (8355 pages)
  •  Not started User talk namespace (4712 pages)

Alternative

Checking only the pages here. See the talk page for more information.

Checked page sets

These pages have all been checked and don't contain invalid tags anymore.

Members

  • Play logo 19:18, 7 May 2020 (UTC)
  • Asarta (Talk) 08:34, 26 July 2020 (UTC)
  • Avidd (talk) 05:41, 19 January 2023 (UTC)
Advertisement