When you add a WMS:Lister control to the actual article template (e.g. a "News Detail" template) the lister may break.  This is because the "ItemIdentifier" attribute is repeated twice on the page!

For example: Say you have an article page that uses <!-- item --> to identify the region of the page the PatternFile refers to, if you then add an actual lister control to the page you end up with two <!-- item --> comments (see below). Once in teh new lister and once for the article!

  <ez:Lister ID="scrollingNews" runat="server" PageSize="4" 
     SortBy="Date" SortDirection="Desc" PatternFile="~/NewsPattern.txt" ItemFileExtension="*.aspx" 
     ItemDirectory="~/News" PagerStyle="None" ItemIdentifier="<!-- item -->"
     CreateCacheIndex="true" FilterKey="Section" FilterValue="">
     <HeaderTemplate><span id="news_listing"></HeaderTemplate>
     <ItemTemplate>
       <a href="<%# ((ListerItem)Container.DataItem).Link %>">
        <wg:PlainText MaxLength="80" Text='<%# ((ListerItem)Container.DataItem).GetValue("text") %>' runat="server" />...
       </a>
     </ItemTemplate>
    <FooterTemplate></span></FooterTemplate>
  </ez:Lister>

The fix is simply to leave the ItemIdentifier attribute out of any Lister control.  The default value is <!-- item -->, so you only need the attribute if you need a different value.

:)

One of these actions following yesterdays meeting [reviewing wmssamples.com] was to (in the medium rather than short term) review the site structure for Ezone and the WMS.  This has been soemthing we have talked about many times before.  I think a great example of how this works are the new Fogcreek, fogbugz sites (allthough they are on the same domain).  Joel (joels on software, owner of Fogcreek) speaks about the redesign here.

I believe that this multiple site structure was what we had been discussing previously but have never quite got implemented.

There is a WMS issue where the parentitem (and currentitem) elements of a menu element may not work when the menu has no child elements.

If this is the case you may be able to workaround it by adding an empty child element. I.E:

<childmenu type="Path">
<currentitem></currentitem><parentitem></parentitem><item></item>
</childmenu>

Barry

This would be nice to recreate for the WMS:

http://resizr.lord-lance.com

Barry