Jazz Jackrabbit 2 Online

This is just a temporary list of bugs which will probably be deleted when the wiki is finished and should not be treated or considered as a wiki entry, but please observe the normal wiki rules anyway.

All the users hope their requests will be answered…

Bugs

Unresolved Bugs

• Redirects will not work if the target entry contains a ‘+’ (plus sign). ~BoggyB
• Entries containing a ‘&’ in the title can’t be edited at all. ~Fl@$h aka BlewMeUp
  Actually, the ‘&’ sign cause the following characters to be ignored (for example, Triggers & Scenery shows Triggers). ~French
• Entries containing a & char can get a messed up title after an edit.
• The sign tag (~~~) does not work in the preview. ~Fl@$h aka BlewMeUp
• HTML isn’t escaped in the summary (see my last edit for this page) ~BoggyB
  Did you use HTML in the summary or only said Fixor (with html brackets)? It seems to not have escaped the HTML but to have actually transformed the summary into html. I haven’t a clue how this would occur from the code, which just does replacements of html tag characters into special nonoffending characters. ~Fquist
  The latter. I wrote “FI > < OR TEH IMAGES” (with no spaces around the angle brackets). ~BoggyB
  I don’t know what this is but it appears to be some Textile bug… which would be beyond our control (except to maybe check for new versions). Note to self: never use Textile in future projects. ~Fquist
• Entities (I mean, for example, &) are replaced by their character in the TextBox after previewing. This can be very annoying with greater and less signs (for example, try to preview this page twice). ~French
  But on the contrary, special characters (as the arrows ← and → which I frequently use) are replaced by their numeral entity before previewing. ~French
  And please not preview this page before submitting; it would make this, especially &, work incorrectly. Please go back to the previous page if you need preview.
• Double-redirection make the original article inaccessible without hard-coding the link (in the address bar). You should prevent double-redirections, or make the original link accessible instead of the article which redirected. You could also make bots to correct double-redirections. ~French
• Having a <nowiki> would prevent from many bugs. See for example what a {{section-stub}} between at signs gives:
  
  Please correct the wiki syntax page when it’s done. ~French
• Quotes “like” ‘this’ are preceded by a backslash. Backslashes \ are themselves preceded by a backslash in preview. ~French
  It can cause big bugs in articles’ names. See this for example. ~French
• The User’s Wiki Contributions pages don’t work and show all recent changes. ~French

Resolved Bugs

• Redirect message does not always show up (example) ~Fl@$h aka BlewMeUp
• The “← Older version … Newer version →” feature on index.php does not always work together with weird characters in the title. ← should be fixed now ~Fquist
• “p-a-r-s-e-s” appears to be censored, as in “parses”. See List of Jazz Jackrabbit 2 Command Line Arguments ~BoggyB

Not a Bug

• The censor eats links; see Mercenaries (the discussion about this “bug” is on the Discussion page).
• Headers starting with ‘(’ or another character recognized by textile may get messed up. This is a textile bug, and one that will rarely come up. The only fix is probably switching to a system of our own, which takes more work than the work it takes to think of another header title than something that starts with parentheses. ~Fquist
  Rarely come up? Wouldn’t it be nice to include links in the headers? Because it’s actually impossible. ~French

Feature request/discussion

Feature requests

• Put a login box that can be used optionally on the edit page if the user is not logged in. Suggested by Aegis. → Done.
  Another suggestion by Sers: make a checkbox that makes your changes be posted anonymously even if you’re logged in. ~Fquist
• Check if the margins for blockquotes and lists can be made the same, and if that would look better. Suggested by Danyjel. ~Fquist
• An option to disable Textile parsing for an entry. Would make it easier to write articles like the Index page, as Textile parsing turns all newlines into <BR> tags (which screws up the HTML formatting). ~BoggyB
• It might be a good idea to hide changes to User pages and maybe Discussion pages too from the Recent changes… I do not think people looking for edits are interested in my addition of a DidYouKnow to my user page and when this wiki becomes more popular the whole History might get polluted by User page edits. ~Fl@$h aka BlewMeUp
  And it makes bothering guys like me to look at these pages and correct stupidly everything! ~French
• Quickjump box beneath the menu (like on Wikipedia).
• Wikipedia syntax (for talk pages?) supported (:, ::, etc.).
• Should redirects show up on the articles list?
  Yes, redirects are pages that can be bad-written. These are articles. But they could effectively be hidden sometimes.
• The title of an entry should automatically start with a Capital letter (with an option to turn it off?).
  This should be possible to make. It’s easy for admins to rename with the right markup though.
  Yes, but non-admins can’t rename! I myself made unfortunately some articles without capital letter. Using the Search TextBox, the capital is added; but using internal links, it is not! ~French
• In fact, internal links linking to non-existent pages should show the Search page instead of an empty page. ~French
• Also, the Search TextBox should never be hidden (like it is in the Version History page).
• Locking pages.
• Templates.
• Longer display for summary box.
• Some links, like links to categories at the bottom, are always written in blue, even though the article doesn’t exist. In this last case, they should use the bad-link color.
• Links should have a TITLE attribute in their tag to show the article they link to when pointed. ~French
• The differentiation page ((cur) and (last)) should show a preview at the same time. Also, there should be links to an older version and a newer version in this page. ~French
• A differentiation page to see our modifications should be accessible while editing.

In fact, it would be really good to copy Wikimedia sites for a lot of features!

Rejected Feature requests

• Force people to log in when editing or making entries?
  • No, this wiki should be free for anyone, logged in or not. There’s always IP-checking. ~Fl@$h aka BlewMeUp
  • This will be done if we run into problems with spambots/bad users. Otherwise we will not do this. ~FQuist
  • Well, put a login box there anyways for not million changes like I did. Not required, but good if you forgot to login. ~Aegis

Finished Features

None! Please hurry up!

Archived Discussion

• On Monday the 23^th of January, 2006, this page was cleaned up. The removed content can be seen here.