Troubleshooting

The modules described in this chapter are all very polished systems, but a few interesting issues seem to be of issue more often than others. They are listed in the following sections. These modules are also all very popular, and if you need additional assistance, be certain to try the website forums set up for each module, as well as the general PostNuke forums.

Content Express Form Generates Microsoft Office Pop-Up

When first running Content Express using a Microsoft Internet Explorer browser, you might see a series of pop-up dialog boxes requesting Microsoft Office install CDs. The WYSIWYG editor uses ActiveX components from Microsoft Office, and depending on what you have installed on your machine, you might see a series of pop-up requests. You can put in your Office CD and install the missing components, or click Cancel and close the windows with no ill effects. The WYSIWYG editor works fine without installing any additional features.

Content Express Manage XML Shows _CE_USER_XSLTNOTSUPPORTED

To use the XML feature of Content Express, you must have Extensible Stylesheet Language (XSL) enabled for PHP on your server. PHP discontinued automatic support for XSL from version 4.1, but the dynamic link libraries (DLLs) needed are included in the manual install package.

You do not need XSL support to use the Content Express; it is provided for additional functionality. For complete XSL installation, go to www.php.net/xslt.

PagEd Cannot Find the PHP GD Image Extension

This error is fixed by installing the PHP graphics libraries for your server. The php_gd2.dll is included with the manual PHP installation package. Place the file in your extensions directory, and uncomment the line

 ;extension=php_gd2.dll 

to enable the support. More information on the install of GD support in PHP can be found at www.php.net/manual/en/ref.image.php.

Imported News Topic Has Broken Image

PagEd provides a very slick import feature for existing news and topics on your site, but topic images are not in the database and are still referenced from local file paths. Importing only copies database entries over. Go to the News Topics directory /images/topics/ and copy the images you need to /modules/PagEd/pictures/ to complete the import.

Unknown Window Data in PageSetter

The Unknown Window Data error is caused by a loss of session internally to PageSetter. It is caused by trying to get to a PageSetter page using browser navigation buttons or by clicking the PageSetter navigation links while in a form awaiting a Commit. With the latter cause, the error is prevented by using the Cancel button when done with a form instead of just clicking to a new navigation element.

If you are effectively locked out of PageSetter with this message, you can clear it by going to your PostNuke Administration screen. Reselect the PageSetter link from there, and your access is restored.

No Template Found in PageSetter

If PageSetter is telling you "no template has been created" for your publication type, there are two likely causes. First, did you create a template for the publication? You can use the built-in system to autogenerate appropriately named blank templates for any publication.

Second, did you reference the template correctly when you created your display block? You need only use the short, specific name of the template, such as list, full, or print. If you have entered the publication name or the full filename, such as PN-News-list.html or PN-News-full, the system does not work, returning the error message described previously.