Wikipedia:Bugzilla: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m me too
whitespace, simplify top
Line 97: Line 97:
--[[user:Damian Yerrick|Damian Yerrick]]
--[[user:Damian Yerrick|Damian Yerrick]]


:I agree, especially at the top it's ''very'' busy. For new users, lets just have the page title in <H1>, the Wikipedia tagline, maybe Printable and Edit, then the content. --[[user:Carey Evans|Carey Evans]]
:I agree, especially at the top it's ''very'' busy. For new users, lets just have the page title in <H1>, the Wikipedia tagline, maybe Printable and Edit, then the content. --[[user:Carey Evans|Carey Evans]]


:I agree too - people new to Wikipedia will probably be overwhelmed by all the different links and actions at the top of the page. I suggest simplifing the top to the most necessary things and putting the rest at the bottom. Are two search boxes really necessary anyway?
----
----
'''Single quotes in summary produce extra <nowiki></nowiki> characters'''
'''Single quotes in summary produce extra <nowiki></nowiki> characters'''

Revision as of 20:01, 26 January 2002

(see also Jimbo Wales Minor Issues With New System)

Please submit bugs with a bold title and date, and a specific reference.

UNCONFIRMED

Newly submitted bugs which no one has been able to duplicate yet.


"List only new changes" doesn't work

Sat Jan 26 20:31:56 2002 (Central) On special:RecentChanges, the link saying "list only new changes" consistently returns an empty list, even after waiting a while. --AxelBoldt

Right! Same here. Maybe because i'm using a +8 hours offset? --Luis Oliveira

Most wanted page listing links with trailing whitespace

Sat Jan 26: The "Most wanted" page indicates that a whole bunch of pages want a "Year in Review/Guidelines" page, but that page already exists. Upon poking around a bit more, I found that all of the pages who supposedly had a link to the non-existant page had links with a trailing space, and this was being considered different from the link without a trailing space. For example:

The "wanted" page considers the second link to point to a non-existant page.


Javascript in generated pages

Sun Jan 27 01:52:53 UTC 2002: Too much HTML is let through unchallenged. For example, try the following link not to my user page, Carey Evans. HTML 2.0 plus tables should be enough for formatting Wiki pages, though I'd prefer to be able to do everything without HTML at all. --Carey Evans


Ampersand in URLs

Sun Jan 27 01:11:52 UTC 2002: URLs containing ampersands should have them escaped as an entity reference, i.e. &amp;amp;. This seems to be the only problem stopping the pages from being technically correct HTML 4.0 transitional. --Carey Evans


Sat Jan 26

The link to the tarballs from the home page doesn't work. It gives the error "You don't have permission to access /tarballs/ on this server".

Also, there was a problem in the past when the tarballs did work: there was no date in the tarball filename or on the page with the link, so you never knew how old the tarball was.


Sat Jan 26 02:55 am PDT 2002

When entering raw unicode such as

料 理 の 鉄 人  

in the editing pane ( from the Iron Chef page ) and then clicking the preview button, the preview shows the correct characters, but the text in the preview pane is mangled to be

&amp;#26009; &amp;#29702; &amp;#12398; &amp;#37444; &amp;#20154;


previewing a second time results in

&amp;amp;#26009; &amp;amp;#29702; &amp;amp;#12398; &amp;amp;#37444; &amp;amp;#20154;

and so on -- Olof

+1, this is quite annoying. I'm not even sure what the text above was supposed to look like now. --Carey Evans
The parser seems to be overeager in converting ampersands to ampersand-a-m-p-semicolons when they're followed by the pattern for a character entity in WikiPage::subParseContents(), where I don't *think* it should be doing that. I don't have the current code in front of me though, so I'm not sure exactly what it's doing. Magnus? --Brion Vibber

Sat Jan 26 05:00:39 UTC 2002

At least on Mozilla, long URLs or wide tables like at salicylic acid or Japanese language widen the containing table cell so much the rest of the paragraphs are almost impossible to read. --Carey Evans

This would be a general problem with wide tables, images, and pre-tags... The trick is to make them a reasonable size when you write them, I guess. I've rearranged the table on the acid; the Japanese text can be squooshed down a bit; but I notice another thing there. There's a link inside a pre-tag which, being in a pre-tag, doesn't get linked but instead is treated as raw text. Is there any way to deliberately insert a link into a preformatted text chunk? Oh, and I'm also having edit conflicts with myself. Very annoying. --Brion Vibber
Given that Mozilla really hates <textarea> within tables, getting really slow, I think the best idea is for me to turn off the quick bar thingy. --Carey Evans

Less than/greater than

Sat Jan 26 04:33:32 UTC 2002: Invalid HTML like "<this>" used to be passed through escaped, like <this>. Now it effectively vanishes. It's also not very kind to talk:insertion sort, which ends up with invalid HTML. Carey Evans


Need more whitespace

January 25, 2002, at 19:40 pacific: The general layout of Wikipedia looks cluttered. It needs more whitespace to be remotely readable. --Damian Yerrick

I agree, especially at the top it's very busy. For new users, lets just have the page title in <H1>, the Wikipedia tagline, maybe Printable and Edit, then the content. --Carey Evans
I agree too - people new to Wikipedia will probably be overwhelmed by all the different links and actions at the top of the page. I suggest simplifing the top to the most necessary things and putting the rest at the bottom. Are two search boxes really necessary anyway?

Single quotes in summary produce extra characters

January 25, 2002, at 19:30 pacific: When a user edits a page, the Preview button will change a ' mark (single quote) in the summary into a ' then a \' then a \\\'. --Damian Yerrick


Double quotes in summary cause an

January 25, 2002, at 19:30 pacific: When a user edits a page, and the Summary contains a " mark (double quote), all changes to the article will be lost when the user clicks Save. --Damian Yerrick


Different user talk namespaces

Fri Jan 25 23:44:16 UTC 2002: I seem to have ended up with two slightly different user talk namespaces. Carey Evans

Me too. --Luis Oliveira
Same here. --tuxisuau
Ditto --LC

Link underlining

Fri Jan 25 23:44:16 UTC 2002: External links and different namespaces should still be underlined, or there's nothing to indicate to new users that they are actually clickable. Carey Evans


Log in doesn't set cookie path

Fri Jan 25 23:29:22 UTC 2002: The Set-Cookie header returned from the log in page doesn't include a path= variable. Most browsers default to "/"; Lynx, at least, defaults to the path of the page, so login doesn't work. Carey Evans


Definitions go in separate lists

Fri Jan 25 23:32:14 UTC 2002: Definition lists like:

Term 1
Definition 1.
Term 2
Definition 2.

each get put in separate <dl> tags, resulting in too much spacing between them. Carey Evans


Broken links coming from old-style links

January 25, 2002, at 13:41: The URL http://www.wikipedia.com/wiki/Damian_Yerrick correctly redirects to the proper article (user:Damian Yerrick), but all links from that article are broken. Shouldn't all links to wiki.phtml go to /wiki.phtml instead? --Damian Yerrick

Better I think for the old addresses to return an http 'see other', so the problem goes away. --


SEARCH function doesn't work on "History of..." pages PLUS newbie questions

1am, 1/18/2002. Go to any page, click on "view other revisions" at the bottom of the page. You go to "History of..." page (eg. http://www.wikipedia.com/wiki.cgi?action=history&id=Aardvark ). Type into the Search box at bottom and search. You are taken to the following url, http://www.wikipedia.com/wiki.cgi, and the page just reads "Invalid URL."

--Paulcz {first time on wikipedia, so it's possibly a user error, but it is consistent on different pages).

hmmm. Also, I just tried the preview button at the bottom of this Editing page and nothing happened. I'm on IE 5.5 by the way.

I've just looked on many pages trying to figure out if I should make a page for my name, such as I see for other people. If so, is that just a regular page with the title paulcz?

Also, I've tried to figure out WHERE I should ask questions such as the one I just asked, and have had no luck, so I figured I'd tag it on here. That would be a good thing to tell newbies (eg, "if you still have questions, edit page 'xxxx' to ask them" or something like that.


Problem with "diff" link?

As of 19:01, 8th January 2001, the diff link on yards/talk gives an inappropriate entry (the diff was added at around the same time, but to a different page). I assume this isn't supposed to happen --AdamW

OK so now it doesn't because I idiotically went and edited the page again. How dumb can you get? --AdamW


The first letter of usernames are automatically capitalized upon submission of the "preferences" page. 2002-1-1

If a all lowercase string is input into the "UserName" field in the preferences page, the first letter of said string is capitalized.

All page titles in Wikipedia should be capitalized. Suggest resolving INVALID. --Damian Yerrick

Konqueror 2.1.1 with KDE 2.1.2 cannot render any edit/add page. 2002-1-1

The text area for the body of the article is displayed correctly; however, the "summary" text field is rendered ""inside"" and over the article body text area. Also, nothing that would normally appear under the article body text area does not render at all.


Japanese Wikipedia marked as ISO 8859-1 2001-12-31

http://ja.wikipedia.com is illegible with IE 5.0 (Mac) because its HTTP (MIME) header includes the line

Content-Type: text/html; charset=ISO-8859-1

The charset should be changed to something appropriate (Shift_JIS or UTF8), or removed and replaced by the equivalent META tag.

On a similar note, visitors to http://www.wikipedia.com should be automatically redirected to the Wikipedia written in the language of their choice, as expressed in their browser language preferences. -- poslfit

Then how would Dutch/English bilinguals switch to the English version? en.wikipedia.com doesn't seem to have any content. --Damian Yerrick

The same problem occurs in Netscape 4.77. However, IE5 works fine. This is very similar and may be related to the problem reported at the bottom of this page. See talk:Ranma 1 for details.


CRLF line endings 2001-12-19

In David Lynch, as an example, if you inspect the resulting page, apparently, each stored line is ended with a CR-LF sequence. However, if I edit it within Lynx, the endings disappear, as they don't exist on Unix. That's all good, but all edits will then differ in all the lines (since no lines match their previous version, everything has a different ending..) See, for example: [[1]] I just fixed a typo in the first lines, and it looks as if everything has changed. Arguably, Lynx, and/or my text editor can be at fault too, but I don't think CR-LF should be stored as part of the text either.. --Chexum

Somewhere between Lynx version 2.8.2 and 2.8.4, now Lynx also submits texts with the CR-LF line-endings, so it's a bit better. I still think that they souldn't be there on the displayed entries. --Chexum
'Twas a bug in Lynx. The HTTP standard RFC 2616, section 2.2, states that everything but entity bodies should use CR-LF line endings.

Search logo I'm not sure if this is a bug: when you search for something, the old logo shows up on the search page, as in http://wikipedia.com/search.fcgi?request=happy


All's Well That Ends Well When I try to get to the page http://www.wikipedia.com/wiki/Alls_Well_That_Ends_Well--Text (Alls Well That Ends Well--Text), I get a 500: Server Error. This is the only page that's been doing this to me in recent months, and it's done it every time I've gone there. -- BD

Update: I just got into the page by typing ?action=edit etc. into the URL. Looks like a complete dump of the raw text of the play, as I had expected; the only odd thing which might have been causing wikipedia to choke was an unescaped (ie, not HTML-coded)