270973 - Firefox crashes when trying to navigate Miva Merchant Admin

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Vera Battemarco]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

I use Miva Merchant 4.20(compiled) and OpenUi(OpenUi.org) .  It all worked great
until I upgraded to the latest version of the openui 4.953/4.982. Now, everytime
I try to navigate the admin panel for my Miva Merchant store Firefox crashes,
closes and I loose all the data as the computer freezes.  I wanted to add the
release notes but they are obviously copyrighted and too long to be included here.
If further information is needed please feel free to contact me or openui.org. 
I have also filed a HelpDesk ticket with them. 

I just want to say how happy I am with FireFox. I even added a link to you guys
from my website.  Thanks and keep up the great work! Vera Battemarco

Reproducible: Always
Steps to Reproduce:
1.Log in to merchant admin
Sorry, I am not leaving the log in info here. If you need further help please
contact me.
2. Just try to click any link on the left nav bar.
3.Firefix crashes instantly and closes.

Actual Results:  
crash and burn!

Expected Results:  
Allowed for navigation, just like it used to.

Unable to collect any further information but a crash report was automatically
sent to your site.  Computer freezes until crash is sent and it does not allow
for looking into details for the crash report.

Comment 1

[Uri Bernstein]

The incident ID is 2073361:
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=2073361

Reporter, can you please upgrade to the latest version of Firefox (1.0) and
report whether you are still seeing the problem?

Comment 2

[Michael]

I have a number of Miva customers with OpenUI installed and am having the same
issue in all Miva stores with a fresh install of the new version of OpenUI.
Stores that had the old version and were upgraded are not affected. Stores
without OpenUI are not affected. I'd be inclined to blame some poor coding
skills at OpenUI given their past history of Microsoft style
ship-n-sell-it-we'll-worry-later.

I am using Firefox 1.0.

Comment 3

[Michael]

The work around is to log into the admin screen using MSIE, go to Domain
Settings,   OpenUI Settings and check JavaScript Left Nav (turn it on). Now you
can use the Open UI menus provided you have JavaScript turned on in Firefox. (I
also have Java enabled. Not certain if you need that.)

Comment 4

[Barrett]

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0

It goes well for a few days and just when I'm getting comfortable it crashes
every dang time after the first click or two in the left nav frame.

(Camino does the same thing guys)

The advice to 
"OpenUI Settings and check JavaScript Left Nav (turn it on)"
Is WRONG.

I Thought I had been advised by Darren Ehlers to turn it off and had been
running it that way for a few weeks.
I turned it back on tonight and quickly reproduced the crash.

I highly recommend you contact [e-mail] and he may be able to
arrange a mMerchant admin login to test. He is a sharp guy and responsible for OUI. 
(PS I'd rather have my browser crash than our server crash any day <grin>)

This is on OS X 10.2.8
Merchant 4.20

Comment 5

[Michael]

Checking the option " Enable JavaScript Left-Nav Tree:" is what works here.
If unchecking it works for you, great! I guess the advice here is to change this
setting if you are having this error.

(In reply to comment #4)

> The advice to 
> "OpenUI Settings and check JavaScript Left Nav (turn it on)"
> Is WRONG.
> 

Comment 6

[Barrett]

I think there is more to it now since I made the change to ON, and got repeated
the crash a few times, came back 24 hours later, and have now been using it
without crashes.
This is the same behavior I get with it off - works really good for a while and
then for no apparent reason starts crashing again.
Very weird. 
Someone that knows what to looks for really needs to get on this.
I mentioned the right contact in previous post.
Actually I'm using Firefox today and extensively yesterday without trouble -
we'll see how long it holds with Javascript enable checked.

(In reply to comment #5)
> Checking the option " Enable JavaScript Left-Nav Tree:" is what works here.
> If unchecking it works for you, great! I guess the advice here is to change this
> setting if you are having this error.
> 
> 

Comment 7

[Barrett]

Started crashing today again.
Worked really well for apx half hour and then no matter the combination of
clicks or links in MM admin - boom boom boom everytime now.
Is there some corrupt file it caches and lets go of in 24 hours or so ???

How can I get talk back to send more info ?

Comment 8

[Howard T. Perry]

Since upgradng to Fireforx 1.0.2 two days ago, I am no longer able to browse any
Miva shopping cart or log into the Miva 4.12 admin control console.

An example of a Miva shopping cart that I cannot browse is
http://www.InterOrdnance.com/Merchant2/merchant.mv

Firefox does not crash, rather just sits with the hour glass cursor and the Stop
button is not available.  I can close the tab for this sight and continue to
browse other sites.

I hope this helps.

Howard

Comment 9

[Michael]

(In reply to comment #8)

No problem here with uncompiled Miva and version 1.0.2. I don't know if you have
OpenUI installed. My test did not. Sounds like a bad configuration on your
computer. Try uninstalling including the backup and removal of personal/default
profile information. The only important items to restore is usually bookmarks.
The rest of it is easily recreated after you install 1.0.2. Check the forums,
etc. for more details on this.

> Since upgradng to Fireforx 1.0.2 two days ago, I am no longer able to browse any
> Miva shopping cart or log into the Miva 4.12 admin control console.
> 
> An example of a Miva shopping cart that I cannot browse is
> http://www.InterOrdnance.com/Merchant2/merchant.mv
> 
> Firefox does not crash, rather just sits with the hour glass cursor and the Stop
> button is not available.  I can close the tab for this sight and continue to
> browse other sites.
> 
> I hope this helps.
> 
> Howard

Comment 10

[Ryuichi KUBUKI]

(In reply to comment #8)
> Since upgradng to Fireforx 1.0.2 two days ago, I am no longer able to browse any
> Miva shopping cart or log into the Miva 4.12 admin control console.
> 
> An example of a Miva shopping cart that I cannot browse is
> http://www.InterOrdnance.com/Merchant2/merchant.mv

The link works for me on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8b2) Gecko/20050526 Firefox/1.0+

Comment 11

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 12

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.