plugin generated an error message saying the plugin failed. Another error message says the MWF failed to load, followed by "Map projection failed"

RESOLVED EXPIRED

Status

()

RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: keith_w_krieger, Assigned: peterlubczynski-bugs)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925

In the page at http://map1.kcmo-net.org/mapping/open.html, the map framework and
toolbar renders, but the map fails to open with the following error messages:
Unable to open the MWF.
Followed by: 
Map Projection failed.
After clicking through the error messages and reloading the page 3 times and
clicking through the error messages, the map finally renders.


Reproducible: Always

Steps to Reproduce:
1. Navigate to http://map1.kcmo-net.org/mapping/open.html
2. After installing the MGPlugin63.exe and restarting the browser, return to
http://map1.kcmo-net.org/mapping/open.html
3. The error messages appear as the map tries to render

Actual Results:  
Error messages from the plugin appear, followed by a partial rendering of the
toolbar for the MapGuide plugin. 

Expected Results:  
A clickable map attached to a back-end database should have appeared

configuration:
PC, 256MB RAM, cable modem connection accessed through the LAN.
Worked fine until the 1.5 betas and RC's. 
Did not cause a browser crash, although the Plugin Manager suggests that I
should restart the browser.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.