Centralpoint Update 8.0.18

Date of Update: Monday, July 27, 2009

The standard file upload popup window will now verify that the upload subdirectory exists and create it if it does not.
A bug that caused the current search criteria entered into a search box to be duplicated has been repaired.
The client console has a new page that can be accessed by the URL “/Console/CpCollection.aspx?sn=ConsoleNavigationSystemName”. This page will display the XML used to generate the attributes displayed for the given console navigation item. It is assumed that the console navigation item relates to a module. This was developed for use with the new Custom Attributes module configuration, but has been designed for many other uses in the future.
Master / CMS / Modules now contains a new control validator named “XML Validator”. This allows us to validate an attributes value to determine whether it contains valid XML. It also allows us to validate the XML against a custom schema or define a collection type to validate the xml as a Centralpoint collection, or more specifically an Attribute, Configuration, or Property collection.
A bug in the code used to allow URL based navigation items to point to virtual rewritten URLs has been detected and repaired. The bug caused URLs containing query string parameters to return an error when included in the navigation.
A new module configuration called “Custom Attributes” has been added to all modules. Remember that you must be an Ancestor Admin to select the “Module Configuration” option from a standard modules “Page Options…” selector. Ancestor Admins are users logged into a web site with an account that was created in the sites Master or Uber console.

You may use this configuration to upload an XML file that will be used to customize the modules attributes. New attributes may be added and existing attributes may be renamed, textually modified, or reordered. Some changes are prohibited and will be undone during the attribute merge. Moving required attributes out of the “Attributes” group is prevented because it causes validation problems. If the original attributes are modified after custom changes have been made, the changes may not be reflected in the modules attributes because the site will still use the custom attributes.
The words “existing attributes” in the new configurations header text are linked to a new tool that allows you to view and save the modules current attributes XML.
When uploading custom attributes the uploaded file is validated to ensure that it meets the requirements of an attributes XML file. It must be a valid CpCollection XML file and the first group node must have an id of “Attributes”.
When ecommerce is enabled, custom attributes are merged before the ecommerce attributes. Custom attributes should not contain ecommerce attributes (prefixed with cpsys_Ecommerce).
New attributes added using Custom Attributes can only be used on the Site Architecture / Module Designer / Details View (#3). They do not exist in the relation, and therefore, cannot be displayed in repeated data like search results without first being added to the actual module, its relation, and implemented accordingly.
To test this feature just click the “existing attributes” link and use the save icon in the upper right hand corner of the popup to save the attributes XML as a file on your desktop. Then open the new XML file and change it, ensuring that it keeps the UTF-8 encoding. I suggest you change the name of some of the attributes and maybe copy an existing attribute and paste it in again, but be sure to change the id of the property node which must be unique within the entire file. Then upload the modified XML file using the Custom Attributes “File Upload” button and save the module configuration. The module’s attributes should now reflect the uploaded customizations.

Numerous errors were being reported when an audience/role combination had more than one home page. In this scenario only the first home page is accessible. The implementation has been modified so that when this occurs a 404 error will be displayed on the site and an error will not be report to Centralpoint.
The “Mobile Web Site Search” help file has been updated to include an onKeyPress event in the search text box. When included this event will allow the enter key to trigger a search when the users cursor is in the text box.
The script time out in the Admin / All Modules module has been increased to support sites with more data, however, in this case the script may take a long time to load.

See Full History of All Updates