NetworkedPlanet Blog Insights into developing with NetworkedPlanet products

EPiServer Module 3.3.0.39 Released

TMCore EPiServer Module 3.3.0.39 has now been released. This update fixes a number of cosmetic and compatibility issues when using the Topic Map interface under non-IE web browsers. Support for both Firefox and Chrome web browsers, as well as the newly released Internet Explorer 8 has been tested.
When upgrading from a previous release, please ensure that you empty your web browser cache so that your receive the most recent Javascript and CSS files served from the web server.

EPiServer Module 3.3.0.38 Released

EPiServer Module 3.3.0.38 has now been released.
This release fixes an issue where unpublished pages when deleted from within EPiServer were not also being removed from the Topic Map. This would cause an already deleted unpublished page to show as a valid association within the Topic Map Editor interface. If you have previously encountered this issue, you must manually remove the topic for the deleted unpublished page as the consistency checker is unable to determine topics that do not have an associated page within EPiServer at this time.
Compatibility with EPiServer CMS 5 R2 SP2 RC has also been tested. We are aware of cosmetic issues with the Topic Map Editor when using Internet Explorer 8 or Firefox however.

EPiServer Module 3.3.0.37 Released

EPiServer Module 3.3.0.37 has now been released. This update addresses an issue whereby registering events with SchemaJSON were not being fired correctly. Registering events with SchemaJSON now requires that after the event is registered FlushSchema() is called so that the event is properly registered.

EPiServer Module 3.3.0.36 Released

EPiServer Module 3.3.0.36 has now been released.

• The topic map interface has been improved when dealing with topics scoped in multiple languages as well as for topics that are unscoped. Editors can now choose the language of topics they wish to see, either in a scoped language or all topics in their default unscoped view.
• Compatibility with Firefox has also been improved there may still be minor cosmetic issues however.

The upgrade requires that you install the EPiServer Module SQL extensions by running the included SQL script.

Additional information about upgrading to the TMCore EPiServer 2.0 Module

A number of projects are using a Release Candidate or Beta release of the EPiServer Module 2.0. With the final release now public here are a few additional pieces of information:

Which files are added/deleted?

There have been additions to the documentation and the AJAX topic editing client. However, deploying over the top of an existing installation will work correctly; the obsolete files will simply not be used.

Is it necessary to run the EpiServerModule.sql when I am updating?

Yes, we've updated the SQL Stored Procedures. However, this does not change any of the data in the database.

Which web.config settings should be added/removed?

No settings must be removed or changed, however you should review your existing web.config configuration with the installation guide to ensure correct operation.

Adding a new Dynamic Property 'topicidentity' to the EPiServer Project. Should there be a default value?

No value is required as default. It will get filled in automatically on each page by the EPiServer Module, either during the page create post-processing, or by the consistency checker.

The first time I run the Consistency Checker I get a lot problems reported

page name has no GUID. Will create one: urn:guid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
page name has unwanted subject identifier http://www.networkedplanet.com/2005/01/episerver/np-gen-psi/pageid
page name requires new subject identifier: urn:guid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

In TEM 2.0 we require the definition a new dynamic property to EPiServer which is a GUID, or Globally Unique IDentifier. The GUID is then used, in combination with a prefix urn:guid:, to construct the subject identifier of the topic representing the page.

The result of this is that the GUID property of the page is unchanged throughout the life of the page, and is preserved through export operations. This therefore allows EPiServer administrators to export page data, export the XTM from TMCore and then import in to new systems and the system will work as expected.

The EPiServer page ID can still be derived from the a topic via an occurrence value on the topic, typed by the Page ID occurrence type topic, by default this a topic with the subject identifier http://www.networkedplanet.com/2005/01/episerver/pageid.

The old subject identifier is no longer required and will be removed by the consistency checker.