<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> users-bounces@geoext.org [mailto:users-bounces@geoext.org] <b>On Behalf Of </b>Charlton Galvarino<br><b>Sent:</b> Friday, December 02, 2011 8:33 PM<br><b>To:</b> users@geoext.org<br><b>Subject:</b> [Users] bug with layers having a WMS LAYERS value of 0<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The legend panel seems to have fatal issues when a new OpenLayers.Layer.WMS’s LAYERS value is 0 as in ‘zero’.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Take the stock legendpanel.html as an example.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Instead of the default Tasmania layer which looks like this:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> new OpenLayers.Layer.WMS(<o:p></o:p></p><p class=MsoNormal> "Tasmania",<o:p></o:p></p><p class=MsoNormal> "<a href="http://demo.opengeo.org/geoserver/wms?">http://demo.opengeo.org/geoserver/wms?</a>",<o:p></o:p></p><p class=MsoNormal> {layers: 'topp:tasmania_state_boundaries', format: 'image/png', transparent: true},<o:p></o:p></p><p class=MsoNormal> {singleTile: true}),<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>. . . simply swap out the proper LAYERS value for a ‘0’ which ends up looking like this:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> new OpenLayers.Layer.WMS(<o:p></o:p></p><p class=MsoNormal> "Tasmania",<o:p></o:p></p><p class=MsoNormal> "<a href="http://demo.opengeo.org/geoserver/wms?">http://demo.opengeo.org/geoserver/wms?</a>",<o:p></o:p></p><p class=MsoNormal> {layers: '0', format: 'image/png', transparent: true},<o:p></o:p></p><p class=MsoNormal> {singleTile: true}),<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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’.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Charlton Galvarino<o:p></o:p></p><p class=MsoNormal>1 (803) 233-6205 : voice<o:p></o:p></p><p class=MsoNormal>1 (803) 223-9579 : fax<o:p></o:p></p><p class=MsoNormal><a href="mailto:charlton@2creek.com">charlton@2creek.com</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>P.O. Box 50960<o:p></o:p></p><p class=MsoNormal>Columbia, SC 29250<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>