A new hotfix package is available for version 3.0 of the TMCore SharePoint Module. This package addresses a number of bugs and provides a couple of additional enhancements for site developers. The full change list can be found below.
This bug will occur on any installation of the TMCore SharePoint Module 3.0 downloaded before 21st March 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 188.8.131.52 - if the file version shown is greater than or equal to 184.108.40.206, then you do not need to apply this hotfix.
- Download the Hotfix2 package.
- 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.
- Docs. This directory contains the updated Site Developers Guide documentation.
- Stylesheets. This directory contains the updated base stylesheets for site developers.
- NPCLEditor. This directory contains the updated NPCL Schema Editor extensions for the TMCore SharePoint Module
- 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
- After applying the solution updates it may be necessary to restart IIS.
- To install the updates to the NPCL Schema Editor extensions, simply copy the contents of the NPCLEditorExtensions directory to the local extensions directory on your development machine (typically
C:Documents and SettingsAll UsersApplication Data NetworkedPlanetNPCLEditorExtensions).
- BUGFIX: TwoHopQueryWebPart is now properly security filtering both the TargetTopic and the ViaTopic.
- BUGFIX: Modified the sample TwoHopQueryWebPart stylesheets so that they render in a meaningful way even if there is no CSS associated with their CSS class. Each grouped list now renders as a <strong> tag wrapped around the group header and a <ul> containing <li> tags for each member of the group
- BUGFIX: Fixed an error in the EnterpriseServices.SocialTagging module that caused the creation of a new tag to take a long time to complete. Creating new tags in the social tagging web parts should now be much faster.
- BUGFIX: Fixed the ItemAdded event handler to ensure proper completion when the NPItemBase feature is not activated.
- BUGFIX: Topic names for topics that represent SharePoint list items are now generated from the formatted representation of the SharePoint field configured by the Topic Type Mapping. This change ensures that calculated fields are rendered as just their formatted string value.
- BUGFIX: Fixed rendering of Source attributes in Related Topics Field links in views to render a full URL rather than a web-relative URL.
- ENHANCEMENTS: Enhancements made to the NPCL Schema Editor Extensions to ensure more consistent editing of features that are already deployed to a server. The enhancements should make it much easier to update a test deployment of features generated using the NPCL Schema Editor extensions.
- ENHANCEMENT: Modified the Associated Topic Field properties editor to allow the name of the form used by a Topic Creator to be entered in a text field rather than chosen from a drop-down list of forms. This enables the use of forms other than those contained in the list (e.g. forms from _layouts) for the creation of items.