© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
When importing a sample Portal project or creating a portal project using the "New Portal Project" wizard from the samples Gallery, broken link warning messages appear in the Problems view.
Portal Designer only supports displays in HTML, cHTML, and WML. If you have specified other supported markups for a page or label in an imported project, these markups are maintained but they cannot be changed. These markups will not be displayed in the Properties view.
Unless the user assigns a color palette to a page, the default color palette is used in WebSphere® Portal 6. However in Portal Designer, when the color palette is not specified, the color palette of the ancestor page is used instead of the default palette.
In the New Portal Project wizard, selecting a portal server version does not automatically update the Target Runtime. These entries must be manually synchronized, such that a WebSphere Portal v6.0 runtime is selected for a portal server version of 6.0.0.x, and a WebSphere Portal v5.1 runtime is selected for a portal server version of 5.1.0.x. If the two values are not synchronized, the portal server can become corrupted or unusable when the portal project is deployed.
In WebSphere Portal v6.0, when editing the CSS content type JSP files, such as styles.jsp or styles_theme.jspf, with a Styles dialog, JSP expressions may be displayed on the dialog. These JSP expressions cannot be modified on the dialog, you must modify them in the CSS Designer source panel.