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.