Hi Bart (and list),<br>
<br>
Thanks so much for the suggestion - I don't remember placing my old
chameleon.xml file in the new version - but adding the code got rid of
the mlt_cache error.<br>
<br>
Unfortunately, it does not seem to be related to the WMS problem - which is what I really need to solve. <br>
<br>
Has something changed since the last version of Chameleon that might
cause WMS servers to lose their layer lists in the Explore WMS Layers
window? The refreshed servers are still listed as connected, but
display the same way a disconnected server displays except that a
Service Title is still shown. It is not only our WMS servers, but
*every* WMS server that is refreshed. If the server is not
refreshed, there is no problem.<br>
<br>
I made the assumption that refreshing a server grabs a new capabilities
statement. I checked for differences and found only two - one
having to do with the SYSTEM definition and one having to do with the
mapserver version being used:<br>
<br>
BEFORE:<br>
<!DOCTYPE WMT_MS_Capabilities SYSTEM "<a href="http://schemas.opengeospatial.net/wms/1.1.1/capabilities_1_1_1.dtd">http://schemas.opengeospatial.net/wms/1.1.1/capabilities_1_1_1.dtd</a>"<br>
<br>
<!-- MapServer version 4.6.1<br>
<br>
AFTER:<br>
<!DOCTYPE WMT_MS_Capabilities SYSTEM "<a href="http://schemas.opengeospatial.net/wms/1.1.1/WMS_MS_Capabilities.dtd">http://schemas.opengeospatial.net/wms/1.1.1/WMS_MS_Capabilities.dtd</a>"<br>
<br>
<!-- MapServer version 4.8.1 <br>
<br>
The tricky thing is that ONLY our files showed these differences.
Other refreshed server capability statements showed no difference
between the "before" and "after". Perhaps I am on the wrong
track? Or perhaps this could be part of the answer?<br>
<br>
I am running out of ideas with my limited understanding of exactly how
the widgets work and I truly appreciate any help that can be provided.<br>
<br>
Thank you!<br>
<br>
Jennifer Zeisloft<br>
UW Sea Grant<br>
<br><br><div><span class="gmail_quote">On 5/4/06, <b class="gmail_sendername">Eijnden, B. van den (Bart)</b> <<a href="mailto:b.vdeijnden@agi.rws.minvenw.nl">b.vdeijnden@agi.rws.minvenw.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;">
<div><span><font color="#0000ff" face="Arial" size="2">Jennifer,</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">cache_mlt is a new option in chameleon.xml. Did you just place your old
chameleon.xml in your 2.4 version? You could add an entry to your
chameleon.xml:</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">
<context-param><br>
<param-name>cache_mlt</param-name><br>
<param-value>false</param-value><br>
<description>This option controls whether or not the MLT language
translation file is cached or not. Values are "true" and
"false"</description><br>
</context-param><br></font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Don't
know if this will solve your problem though.</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div><span><font color="#0000ff" face="Arial" size="2">Best
regards,</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Bart</font></span></div>
<blockquote>
<div align="left" dir="ltr"><font face="Tahoma" size="2">-----Oorspronkelijk bericht-----<br><b>Van:</b>
<a href="mailto:chameleon-bounces@lists.maptools.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">chameleon-bounces@lists.maptools.org</a>
[mailto:<a href="mailto:chameleon-bounces@lists.maptools.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">chameleon-bounces@lists.maptools.org</a>]<b>Namens </b>Jennifer
Zeisloft<br><b>Verzonden:</b> donderdag 4 mei 2006 0:39<br><b>Aan:</b>
<a href="mailto:chameleon@lists.maptools.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">chameleon@lists.maptools.org</a><br><b>Onderwerp:</b> [Chameleon] Manage WMS
Servers widget shows "cache_mlt" errors, results in no WMS data
layers<br><br></font></div></blockquote></div><div style="direction: ltr;"><span class="e" id="q_10afe4971a5e3b76_1">Hello All,<br><br>I recently upgraded ms4w and
chameleon to the versions most current at the time: ms4w 1.4.1 and chameleon
2.4. Since that time, the Manage WMS Servers widget "inside" the Add WMS
Layers widget is returning a series of errors with the same messge:
<br><br>cache_mlt not found. Returning default value. <br><br>The biggest
problem is that any servers that are refreshed or added show only the upper
most segment of the tree in the Add WMS Layers dialog - i.e. the title
appears, but none of the layers appear and nothing can be added to a
map. I am guessing this is related to the cache_mlt error, but not
certain how.<br><br>I searched the archives and took a look at the mlt.php
file, but don't understand how this would affect WMS servers. <br><br>A
look at the Apache error log shows a couple of unusual errors that I do not
know the origins of and which also seem related to the WMS
problem:<br><br>Premature end of script headers: php.exe, referer:
http://.../chameleon//common/phpwms/manage_servers.phtml?sid=445925887dba6&callbackFunction=myUpdateServers<br><br>File
does not exist: C:/ms4w/apps/chameleon/htdocs/skins/default/css/cwc2.css,
referer:
http://.../chameleon//widgets/WMSBrowser/WMSBrowser.php?template=mapbrowser_iframe_en.html&sid=445925887dba6
(none of the icons, etc. appeared to be missing...)<br><br>If anyone should
have a suggestion as to how to get WMS layers to appear in the Add WMS Layer
dialog or how to get rid of the cache_mlt error, I would greatly appreciate
it!<br><br>Thanks in advance for your help!<br><br>Jennifer Zeisloft<br>UW Sea
Grant<br></span></div><div style="direction: ltr;"><br>
Disclaimer
************************************************************************
Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te
informeren. Wij adviseren u om bij twijfel over de juistheid of de
volledigheid van de mail contact met afzender op te nemen.
This message shall not constitute any rights or obligations.
This message is intended solely for the addressee.
If you have received this message in error, please delete it and
notify the sender immediately. When in doubt whether this message
is correct or complete, please contact the sender.
************************************************************************
<br>
</div></blockquote></div><br>