You need to log in before you can comment on or make changes to this bug.
Loading samples generates JS error that stops browser from displaying map. I tried loading a few samples without success. The following samples generate the first three JS errors: sample_basic_plainbuttons.phtml, sample_basic.phtml, sample_basic_buttonizer.phtml, sample_enhanced_themelegend.phtml, sample_basic_jsapi.phtml The following samples generate the first three and the forth JS errors: sample_enhanced.phtml, sample_bilingual.phtml, sample_enhanced_jsapi.phtml, sample_ogc.phtml, sample_other.phtml The following samples generate the first three and the fifth JS errors: sample_roi.phtml Fedora Core 2 Chameleon (php_utils) cvs 20040809 Mozilla 1.6 ------------------------- JS error: Error: CWCDHTML_GetImage is not defined Source File: http://192.168.4.100/nsavard/chameleon_cvs/sample.js Line: 75 Error: MapWidgetInitVariables is not defined Source File: http://192.168.4.100/nsavard/chameleon_cvs/sample_basic_plainbuttons.phtml Line: 737 Error: MapLayerDivImgOnLoad is not defined Source File: http://192.168.4.100/nsavard/chameleon_cvs/sample_basic_plainbuttons.phtml Line: 401 Error: gMapWhspc is not defined Source File: http://192.168.4.100/nsavard/chameleon_cvs/sample_enhanced.phtml Line: 61 Error: Line is not defined Source File: http://192.168.4.100/nsavard/chameleon_cvs/sample_roi.phtml Line: 93
Changed target to 1.99 Beta 3.
cannot reproduce.
Is it better to let this bug marked as "New" instead until the reporter verify it and mark it as "Invalid"? Because this bug (if this is a bug) could be lost.
I think the bug is invalid, at least for the current cvs version ... this should then be verified during testing and either re-opened or a new bug created if you discover that I am lying :> But as far as I am concerned, the bug is no longer valid.
no js error during testing on sample application verified that this bug is invalid using beta 3 20041022 on windows
I only a JS error with these two templates: sample_basic_jsapi.phtml and sample_enhanced_jsapi.phtml. Is is related to the JSAPI bug or is it a synchronisation JS functions loading you already talk about Paul? ----------- JS error: Error: goCWCJSAPI is not defined Source File: http://server/chameleon_beta//widgets/MapDHTMLWidget/MapDHTMLWidget.js Line: 641
Paul, I think this bug is waiting for an answer to Norms question inorder for it to be closed.
Norm, do you still get these errors? I just tried this on my linux and I don't ge them. Perhaps they were fixed as part of making the JSAPI work?
I'm still having these messages. I got 20 copies of this message with the "sample_basic_jsapi.phtml" and one with "sample_enhanced_jsapi.phtml".
Who set this bug to Verified? Norms comment #9 suggests that there is still a problem. Norm will have to verify that this is still a problem.
oh, I can say that there is still no problem on windows. using beta 3 20041105
This problem still exist on Fedora Core 2. I will ask Julien to help me out with this.
Chris, in comment #9 you asked who verified this bug. If you click the link 'View Bug Activity' just under the commit button, the answer will be revealed, and it was YOU! ;) If the problem still exists for Norm after getting assistance from Julien, I suggest reopening it with a target milestone of RC1 (since it no longer affects the beta 3 release)
so that is what that link is for. :) I guess I verified it as windows fixed, while norm still had his problems on Linux.
The error described in comment #6 arises because the "cwcjsapi" widget is not loaded and the next widget ("<cwc2 type="SharedResource" name="CWCJSAPI"/>") in the sample is referring to this widget. The "cwcjsapi" is not loaded because of its maturity level "MATURITY_ALPHA".
I have changed the phtml files for those apps to lower the maturity level. Does this completely fix the issue?
I think it is an acceptable fixed. Question: (Maybe I'm pushing too far)Is there a way to send an error to the ErrorReport widget when a widget need another widget and this widget is not there?
If I understand the question correctly, I don't think there is a mechanism. I think a good fix in this case would be to remove the requirement for an explicit SharedResource named CWCJSAPI and have the CWCJSAPI widget create the sharedresource. But then again, I would like to review the whole concept of CWCJSAPI and consider changes that would make this unnecessary ... CWCJSAPI is a very unique case, there are very few other instances like it. I think we can safely ignore this problem and deal with any issues that arise on a case-by-case basis.
This is an invalid bug.
I updated from CVS Nov 11 09:34. The error is still appearing. I guess the change is not committed.
Dismiss comment #20.
