A new hotfix package is available for version 3.0 of the TMCore SharePoint Module. This package addresses a number of bugs and performance issues. The full change list can be found below.

Systems Affected

This hotfix should be applied to any installation of the TMCore SharePoint Module 3.0 downloaded before 17th December 2008. If you downloaded your copy of the software from our site on or after this date, the hotfix is included in the package and you do not need to apply it again.

To determine if your system is affected, check the File Version property of the assembly NetworkedPlanet.SharePoint in the GAC (browse to C:WindowsASSEMBLY, locate the NetworkedPlanet.SharePoint assembly, right-click and choose Properties. The File Version can be found on the Version tab above Description and Copyright). This hotfix updates the File Version of the NetworkedPlanet.SharePoint assembly to - if the file version shown is greater than or equal to, then you do not need to apply this hotfix.

Upgrade Instructions
  1. Download the Hotfix8 package.
  2. The package is provided in a compressed ZIP file. Unzip the package on a machine in the server farm. The package contains the following files:
    • NPSharePoint.wsp. This is an updated copy of the SharePoint Solution package provided with the 3.0 release of the TMCore SharePoint Module.
    • NPOfficeServer.wsp. This is an updated copy of the SharePoint Solution package provided with the 3.0 release of the TMCore SharePoint Module.
  3. Use stsadm to upgrade the NPSharePoint.wsp and NPOfficeServer.wsp solutions on the server. The exact command-line you use will depend on how you want to schedule the upgrade, but in any case it must include the -allowgacdeployment option. A sample command line would be:
    stsadm -o upgradesolution -name NPSharePoint.wsp -filename NPSharePoint.wsp -local -allowgacdeployment
    stsadm -o upgradesolution -name NPOfficeServer.wsp -filename NPOfficeServer.wsp -local -allowgacdeployment
  4. Using SQL Server Management Studio or a command-line tool such as OSQL.EXE, execute the SQL script SQLnpsharepoint.sql against the database that holds the topic map(s) used by your SharePoint installation. This will upgrade a stored procedure used by the Search Results Topic List Web Part.
  5. After applying the solution updates it may be necessary to restart IIS.
  6. If you have installed the NPCL Editor Extensions for the TMCore SharePoint Module, copy the contents of the NPCLEditorExtensions directory to the extensions installation directory for NPCL Editor. The path to the extensions directory will depend on your installation but will typically be either: C:Documents and SettingsAll UsersApplication DataNetworkedPlanetNPCLEditorExtensions or C:Documents and Settings{User Name}Application DataNetworkedPlanetNPCLEditorExtensions
  7. This package also includes all updated documentation in the Doc directory. We recommend that you copy these files over the previously installed documentation files.
  8. Change Log
    • BUGFIX: Implemented a workaround for the problem that SharePoint does not correctly notify event handlers when the URL of a page is changed through the Page Settings. Topics representing pages should now get their content URL correctly updated if the editor changes the page URL in Page Settings.
    • BUGFIX: Fixed an error that meant that topics for items in lists that support only major version numbers and require content approval were not getting updated properly and appeared to lose related topics information.
    • BUGFIX: Fixed resource references in Classify.aspx and other pages to ensure that pages display correctly on sites that have only WSS installed.
    • BUGFIX: Fixed an issue that prevented the list of Content Type to Topic Type mappings from displaying when one of the mappings contains a reference to a non-existant SharePoint field.