[Users] bug with layers having a WMS LAYERS value of 0

[Charlton Galvarino]

I did get around this by preventing a small block (of setText I think) from being executed in GeoExt.js, but that didn't seem like a robust fix to me.

From: users-bounces at geoext.org [mailto:users-bounces at geoext.org] On Behalf Of Charlton Galvarino
Sent: Friday, December 02, 2011 8:33 PM
To: users at geoext.org
Subject: [Users] bug with layers having a WMS LAYERS value of 0

The legend panel seems to have fatal issues when a new OpenLayers.Layer.WMS's LAYERS value is 0 as in 'zero'.

Take the stock legendpanel.html as an example.

Instead of the default Tasmania layer which looks like this:

        new OpenLayers.Layer.WMS(
            "Tasmania",
            "http://demo.opengeo.org/geoserver/wms?",
            {layers: 'topp:tasmania_state_boundaries', format: 'image/png', transparent: true},
            {singleTile: true}),

. . . simply swap out the proper LAYERS value for a '0' which ends up looking like this:

        new OpenLayers.Layer.WMS(
            "Tasmania",
            "http://demo.opengeo.org/geoserver/wms?",
            {layers: '0', format: 'image/png', transparent: true},
            {singleTile: true}),

Upon refreshing the page, you'll see an immediate GeoExt.js error.  I don't expect an image to show up since the '0' name is made up, but I don't expect the .js error.

This is an issue because my app is supporting dynamic inclusion of remote WMS-es via getcaps parsing.  In one case, lucky me, a layer is named '0'.



Charlton Galvarino
1 (803) 233-6205 : voice
1 (803) 223-9579 :   fax
charlton at 2creek.com<mailto:charlton at 2creek.com>

P.O. Box 50960
Columbia, SC 29250

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.geoext.org/pipermail/users/attachments/20111202/23c5c9bb/attachment.htm