Wikipedia:PHP script bug reports
This is a list of known bugs of the new Wikipedia PHP script. Other lists of bug are at Wikipedia bugs (some of the issues there apply to the old software however) and at Jimbo Wales Minor Issues With New System.
- The parser (to convert the source text into readable stuff) does not emulate UseModWiki 100%, but I think I got the most important 95%...
While I welcome the new features are welcome, they come at the heavy price. The system is slow. I have to wait quite a while to change page.
Prior to speeding up PHP, can it be made optional?
You mean an option on PHP or UseMod? No way. And, the reason for the system being slow is neither my code nor the PHP itself. The apache server processes keep eating memory for some unknown reason, so the system gets slow until the memory is released again after some time, or by the process dying. Right now, it is not a bit slower than the UseMod, which is probably because of the 9 hours time difference between US and Germany. --Magnus Manske
Run-of-the-mill internal Wikepedia links urgently need to be changed from the format
to (at the very least)
- http://www.wikipedia.com/wiki/English_language (which currently works)
otherwise search engines will not follow these links, and Wikipedia's Google PageRank, and hence traffic, may drop drastically.
(2002/1/28 Cosmetic) special: and wikipedia: pages have title "... - encyclopedia article from Wikipedia". They should not be indexed by search engines or should be indexed with a different page title. This is to "brand" "encyclopedia article from wikipedia" as a source of useful information -- ChaTo
- Bugfix is installed today (I hope). --Magnus Manske
(2002/1/28 Major, Mozilla-Specific?) Bug when editing with Mozilla (0.9.6/Linux). To reproduce: edit a page, write some text, then preview (everything looks ok up to here), then save. All the text is lost, a blank page is saved instead. If you don't preview, then the page is saved ok. --ChaTo
There are also many more bug over here! --Luis Oliveira
- Some of which apply to the old software, AFAIK.--Magnus Manske
- It looks like all the bugs down to "Broken links coming from old-style links" are or were with the new software, as at revision 27. Should I move them here, or delete the rest because they're no longer around? --Carey Evans
a REDIRECT to a REDIRECT doesn't work - the second REDIRECT shows up as a one-item numbered list with a link. -- RAE
- That was also the case with the old software. It prevents circles of redirects, although maybe there's a better way of doing this. --Zundark, 2002 Jan 27
- I could make this work without loops, but I know how much Wikipedians dislike every change, just because it is different ;) --Magnus Manske
Bhutan/Lhotshampa contains a redirect to Lhotshampa, but when I go there I get put into edit mode instead of being redirected.
- I had the same problem with BinomialDistribution/Revisited and Zundark/Old_Talk. It seems to be impossible to redirect a page that has a slash in its title. --Zundark, 2002 Jan 27
- In fact, if you try to redirect Foo/Bar to Quux, it actually treats it as a redirect to Quux/Bar, and seems to give an edit conflict if no such page exists (but updates the page anyway, despite the edit conflict). --Zundark, 2002 Jan 27
Timestamps for previous version links in a page's History are off by one and the first two are therefore set to the current time.
- Check the History link for this page... -- user:Derek Ross
Sun Jan 27 2002
...and probably related: RecentChanges shows (2 Changes) even if there was only one.
The Bipolar disorder page is full of extra whitespace - looking at the article reveals lots of <p> </p> and <pre> </pre> spans generated.
Also, some HTML in page comments is not being escaped out - for example, put <p> in a page comment, and see what happens. -- The Anome
The Formula One page has some problems with the section headings (with the equals sign) -- Jheijmans
There are similar problems at Surreal numbers when the string "<=" is used. -- Jan Hidders
In the Quaternions article, the first part of the article appears at the bottom of the page, as do all the QuickBar links. --Zundark, 2002 Jan 28
- This was caused by Bad Table Code in the article. There was no closing TR tag for the last row in the table, and an extra open TR tag after the end of the table. I've fixed the article... The parser could probably be made to be able to normalize these things, though (ie, remove table-ish tags not inside <TABLE>...</TABLE>) --Brion Vibber
The diffs are very hard to read, since the green and the yellow stuff is not interspersed. There was a recent change on Goedels Incompleteness Theorem, the diff showed the full article text both in green and in yellow, but after 10 minutes I could not figure out where the change was, or whether there even was any. AxelBoldt
In preview the three tilde symbols (~) are not replaced with the user name. -- Jan Hidders
The parser treats white space as significant, which is undesirable. For example, "=== Header ===" will normally produce a level three header line, but if it is followed by whitespace, it will produce a level two header line surrounded by equal signs.
Furthermore, the new parser treats equal signs as a header line even if they occur in the middle of some other text. They should only be treated as a header line if they occur on a line all by themselves.
Similarly, if a line contains only white space, the previous parser took that as a paragraph break, while the new parser treats it as a block of indented nothing, resulting in too much space between the paragraphs. AxelBoldt
At time of writing, the "most wanted" page contains a lot of Year in review pages that do actually exist. example: 12 and 17. clasqm
It's often not clear which version of the software these comments apply to. Suggestion: Write the software version number on the bottom of each page, and make this optional in the user preferences.