i-fix Name: PK29843

Problem Summary: Expired default content still showing on website

Detailed Problem Description:

A content doucment is still visible on the website if it was set as the default content for a sitearea. When entering the URL to the expired content document itself a 404 is returned as expected. However if the URL to the sitearea which references the expired document as the default content is entered, the expired content document is rendered. The same behaviour is seen if the sitearea is linked to through a navigator component.

Problem Analysis:

The status (draft, published, expired) of the default content doucment was not being checked when rendering the sitearea. This allowed expired content to be visible on the website by end users.


Failing Module: WCM - Web Content Management (General)

Problem Solution:

The status of the default content document is now checked when rendering a site or sitearea.

Affected Users: All Users

Requisites:
   pre-requisite Portal Component: WCM 6.0.0.0 GA build 298.0
   pre-requisite interim fixes: PK31448, PK30057

Platform Specific: No

Fix pack: This fix will be integrated into WP v6.0.0.1

Installation Steps:

NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
      The Portal Update Installer can be downloaded from the following link:
      http://www.ibm.com/software/genservers/portal/support

- Create a temporary "fix" directory to store the jar file.
- Copy jar file to this directory.
- Shutdown WebSphere Portal.
- Ensure the pre-requisite fix(es) are installed.
- Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install a fix.
  NOTE: If a pre-requisite fix is not installed, the Portal Update Installer will fail and will list the missing pre-requisite fix(es).
- Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm -DPortalAdminPwd=password
- Stop and Restart the WebSphere Portal Server.


Refer to the clustering section of the Portal Information Center (typically 'Clustering -> Performing Upgrades in a 24x7 cluster') for additional information on installing interim fixes in clustered environments while maintaining continuous availability of your Portal.

Un-Installation Steps:

NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
      DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
      YOU MAY REAPPLY ANY REMOVED FIX.

- Shutdown WebSphere Portal.
- Follow the instructions that are packaged with the Portal Update Installer on how to uninstall a fix.
- Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm -DPortalAdminPwd=password
- Stop and Restart the WebSphere Portal Server. 


Refer to the clustering section of the Portal Information Center (typically 'Clustering -> Performing Upgrades in a 24x7 cluster') for additional information on uninstalling interim fixes in clustered environments while maintaining continuous availability of your Portal.

DISCLAIMER:

This fix has received limited testing only and has not undergone IBM's complete quality assurance process. It is therefore recommended that it be tested in a testing environment before applying it to a working (authoring, production/live) system. You should always backup your data before installing a fix or fixpack.