You need to log in before you can comment on or make changes to this bug.
from a lister: 1. After adding a server, server isn't added to the list in WMSBrowser popup until after close and re-open window, or refresh window. 2. when USEUSERSESSION=true: layers from servers added by user cannot be added to the map. There is an error saying that layer[x] does not exist in capab.dbf file or something like that. This behaviour doesn't happen when USEUSERSESSION isn't listed as a parameter in the widget (=false) 3. Now this is just annoying... the Manage Servers is the default selection, so that you have to chnage the selection and then change it back to manage the servers. Could this be made a button instead? 1 & 3 are IE specific issues. 2 is likely a bug in any browser since it is a server-side problem.
this should be addressed for the RC release
I've fixed the problem with the WMS Browser and USEUSERSESSION and changed the sample_other application to use it. Fix will be in cvs after beta release tomorrow (hopefully). Looking at the javascript errors now.
fixed problem 3, I was using a deprecated way of appending options to the select box that caused a javascript error that prevented dynamic selection of the current server. can't immediately find problem 1, in Mozilla adding a server causes the iframe in the WMS Browser popup to refresh, but I am not sure why 'cause there doesn't seem to be any code to cause it to happen ... must be bleary eyed!
Paul, is the fix for problem 3 already in CVS? I could not find it. I do have another problem with adding a new server through the Manage Servers, but this is probably a configuration issue as Liz is not experiencing this problem. I always get the "errors occurred" and the downloaded capabilities file is put in the wrong position. It is put in Chameleon root and not in the data subdirectory. After I copy the file and try a few more times it gets added, but something goes wrong with the placement which I cannot trace. Any ideas?
Paul, I already found the configuration issue, perhaps this can be put in the documentation. I used the following: WMSCACHEDIRECTORY="/ms4w_20/apps/chameleon/data" and I had to use WMSCACHEDIRECTORY="/ms4w_20/apps/chameleon/data/"
Bart, the fixes are not yet in cvs, I am anxiously awaiting the go ahead for the beta 1 release and was hoping to tag cvs, this fix will not be tested as part of the beta so I didn't commit it. I'm too lazy to try to figure out how to apply a tag in the past ;) I'll post here when the changes are committed. Hopefully they will include fixes to both the one outstanding issue above and the issue you just raised.
okay, the fixes mentioned above are in cvs. I still didn't get the last one fixed, no time today :(
I think the other issue you mention (the directory one) is a bug that should be fixed also.
Paul, any update on problem 1 by any chance?
nope, still crazy after vacation. ...
bart, issue#1 is fixed in cvs.
Bart, can you review the status of this bug, I think most of it has been addressed by now ...
Paul, it is difficult for me to test this now as we are running a partly modified Chameleon version for our project, and I have some upgrade issues with respect to the latest CVS, which I don't have time to fix now. So we will probably be running this modified and old version until 1.99 is released.
assigning to Bart since it is pending his comments.
not sure if any of this is still relevant. I'm closing this as fixed. Since this had multiple issues listed, I would appreciate new bugs being opened if any of the individual problems still exist.