plannergogl.blogg.se - Gnome bugzilla

GNOME BUGZILLA UPDATE
GNOME BUGZILLA PATCH

Since what Bugzilla sends out get's interpreted as ISO-8859-1 anyway, the data was always interpreted and displayed as ISO-8859-1. The Perl charset detection wasn't considered good enough.Ĭomment by MarkusBertheau: Yes. The best solution I read was ripping out the charset detection from Mozilla and using that (a comment somewhere in mozilla bug 126266).

recode html.utf-8 (this recodes the html entities browsers send when the user types a character in the textbox that's not in the page's character set)Ĭomment by OlavVitters: That assumed everything is in iso-8859-1 right? From the Mozilla bug I understood it can be any charset, and detecting that is the problem.

Pipe through iconv -f ISO-8859-1 -t UTF-8.

We need to convert our existing data to UTF-8. See my section below for some of my ideas on the matter. Maybe even put some reports under there.Įlijah: This is part of what I was doing with boogle. I want to make multiple simple search pages (each for a specific purpose). Also needs testing in 'changing multiple bugs at once'.ī.m.o already has a simple search interface.

One to change the state (change it to NEEDINFO/ NEW/ ASSIGNED/ REOPEN/ FIXED/. Separate reassignment from status changes Also needs testing in 'changing multiple bugs at once'.

GNOME BUGZILLA PATCH

I need to attached the patch there after it is finished. To reopen from NEEDINFO to UNCONFIRMED/NEWĪlso while in NEEDINFO, there should be a knob that reopen the bug only if a comment is added.Some of these might already work on b.g.o, but: I've targetted a few bugs against 2.18 and 2.20. I need to make some changes to handle that.ī.g.o is also a product in Bugzilla. Some people are behind transparant proxies. This was a change I made at Andrew's specific request (I didn't like it but he said it was needed in some cases and that cookies weren't reliable or something). We explicitly treat not logged in as being able to edit bugs. I ( OlavVitters) do not think this is a problem.Įlijah: Part of this is due to bug_ grep for "if the person hasn't logged in ($::userid = 0)". This means that we would require Cookies to be turned on. I only want to only the basic minimum possible to add a comment and to CC yourself. This makes for a very bad Bugzilla experience for persons new to Bugzilla (meaning not logged in). This to allow persons not logged in to log in afterwards. The bug for that is at: mozilla bug 224577Ĭurrently when a user is not logged in Bugzilla shows all possible option.

The patch would be for 2.20 only.Įventually it would go into main Bugzilla. Jeff Bailey is working on this and might be able to provide a patch for 2.20.

GNOME BUGZILLA UPDATE

When I'm working I usually update the page often (if you subscribe, prepare to be spammed).Īllows bug-buddy to submit bugs easily, without the message email sending. See /UpgradeStatus for current status of the upgrade. You can however add comments to the existing items. There is no guarantee that ideas listed here will be implemented.ĭon't add new items here, add them in the section Stuff wanted by others. This page is about stuff OlavVitters or one of the other bugmasters want when Bugzilla is upgraded to 2.20. Older / previous Bugzilla upgrades information