On Topic

Thanks to excellent feedback from our partners and our continued QA processes we are pleased to announce the update of the TMCore EPiServer Module to version 2.0.1.0

The following bugs have been fixed

1. Publishing a page caused all associations to be published, even if the page at the other end of the association was unpublished. Behaviour is changed to only publish associations where both ends of the association are published pages (or a topic without a page).
2. Javascript error reported if calling up topic details for a topic which did not represent an EPiServer page in the EPiServer Edit mode. This has been fixed.
3. Copying a page in EPiServer did not cause a new GUID to be assigned or a new topic to be created. This has been fixed.

Please contact Networked Planet to obtain an updated version of the module.

Asbjørn Vølstad is a senior solution architect at Making Waves, and has been working with TMCore and EPiServer on a number of projects. In this post he talks about testing and optimizing, large, dynamic solutions based on TMCore and EPiServer. The specific project he mentions is the new norwegian government portal Regjeringen.no.

When deploying production versions of TMCore EPiServer Module it is often the case that the editorial application works from the local browser but not a remote browser. This is because web applications by default do not allow Http Post operations. This is required by the Topic Map editor that is integrated with EPiServer. To fix this problem ensure the following is contain in the episerver web.config file.

<system.web>
    <webServices>
      <protocols>
        <add name="HttpPost"/>
      </protocols>
    </webServices>
  </system.web>

If using ASP.NET 2.0 you can apply this configuration change to only the path containing the web service by wrapping the above XML in a location element:

<location path="NetworkedPlanet/EPiServerModule/Service">
  <system.web>
      <webServices>
        <protocols>
          <add name="HttpPost"/>
        </protocols>
      </webServices>
    </system.web>
</location>