Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Old Bugzilla queries fail in 3.6.4 need to downgrade to 3.6.3, where are the old versions?

  • 8 svar
  • 16 har dette problem
  • 7 visninger
  • Seneste svar af Chris Ilias

more options

Our in house Bugzilla is very old. It will be some time before it is upgraded. Firefox 3.6.4 does not work with it, so we need to down grade to 3.6.3. Where are the previous version binaries?

URL of affected sites

http://

Our in house Bugzilla is very old. It will be some time before it is upgraded. Firefox 3.6.4 does not work with it, so we need to down grade to 3.6.3. Where are the previous version binaries? == URL of affected sites == http://

Valgt løsning

Hi Gary,

I had the same problem today and Bugilla stopped working (customized version based on 2.17).

I have solved the problem by patching buglist.cgi in the Bugzilla installation. Just search for the definition of $serverpush and replace it by my $serverpush = 0;

After that the intermediate page that causes trouble disappears and everything is fine again.

Best regards, Andre

Læs dette svar i sammenhæng 👍 0

Alle svar (8)

more options

See Install an older version of Firefox

But 3.6.4 also contains security fixes, so going back to old versions is strongly discouraged. If you could elaborate on "3.6.4 does not work with it", maybe we can help. (That same advice may also apply to old versions of bugzilla, but I'm not 100% sure)

more options

When you query Bugzilla 2.1.7.7 then you get a pop-up telling me that I've chosen to open bugs-2010-06-23.html". I suspect it's the errant question mark.

I'm not happy about having to down-grade, but you can't force people to upgrade everything in their systems with a new version of the browser.

more options

Also see https://bugzilla.mozilla.org/show_bug.cgi?id=560561 which turns out to be a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=560245

The resolution if this is basically "sorry". So, based on that entry I need to downgrade to 3.63 until such time as we can upgrade out Bugzilla. (And if you think that's straightforward you don't work in a stringently regulated industry.)

more options

I am also impacted in the same way, when performing a search on bugzilla 2.17.7 in Firefox 3.6.4 the new browser cannot handle the result and asks what application the html can be opened in, this is imapcting us hugely and must be fixable?

more options

I'm now getting reports of this problem too from my Bugzilla users. I'm not schedule to upgrade Bugzilla for probably another six months. What other options are there?

more options

I've asked the folks in mozilla.support.bugzilla to have a look at this thread, and see if they can help.

more options

Maybe I'm not being clear. Asking the Bugzilla folks to patch an ancient version to correct a problem that only appears in the latest version of Firefox is a bit perverse. So, I accept that the old version of Bugzilla uses some quirk of HTML that is a security problem, and I accept that I should update Bugzilla, but that doesn't change the question:

Where is a copy of the 3.6.3 binary? I need to downgrade the version of Firefox for our users who are not considering moving to Microsoft's Internet Explorer because they can use our in-house Bugzilla.

This is a very simple request. It can't be that hard to find 3.6.3 binaries for Windows and Linux and put them somewhere on the web site. It requires no programming, no testing. Just a few minutes to copy it and put test to the effect that we really should upgrade our Bugzilla so we can use the newest versions with improved security. Why doesn't anyone get this?

more options

Valgt løsning

Hi Gary,

I had the same problem today and Bugilla stopped working (customized version based on 2.17).

I have solved the problem by patching buglist.cgi in the Bugzilla installation. Just search for the definition of $serverpush and replace it by my $serverpush = 0;

After that the intermediate page that causes trouble disappears and everything is fine again.

Best regards, Andre