Centralpoint Update 8.0.26
Date of Update: Monday, December 14, 2009
- The web site Page base class has a new property called MetaRobots that can be set to the contents of the robots meta tag. This new property has been utilized by various web site pages like the printer friendly version, splash pages, and email a friend form to prevent them from being spidered by search engines and causing search results with duplicate meta information.
- Attribute CpScripts entered into Site Architecture > Module Designer > Details View (#3) now support a custom parameter called ExecuteCpScriptsInResult. When set to “true” this parameter will cause CpScripts to be replaced within in the attribute contents before they are rendered to the page. You cannot add this parameter to other CpScripts or in other modules or views to get them to execute CpScripts recursively. The primary purpose of this parameter is for use with the Navigation module Content attribute when it is set up in the Module Designer with the Use Navigation Content attribute set to “No”. This new parameter has been documented in the Module Designer help file.
- The BreadCrumbTrail CpScript has been updated to use the new TaxonomyInfo property of Modules.Page which will cause it to only display on results views and to more efficiently display a deep taxonomy path.
- The Site Architecture > Taxonomy custom module has a new tab called Header Tags that works similarly to the Header Tags tab in the Site Architecture > Audiences module. This tab allows you to manage the Meta information (keywords, description, etc.) for taxonomy landing pages. A taxonomy landing page is any standard module Results View (#2) when there is only one current taxonomy item selected. The current taxonomy item may be selected using any of the supported search features like the query string, form state, the module search, etc. This change required the addition of a system taxonomy properties file which allows us to extend the properties stored within taxonomy at any time simply by changing the related file. Client sites can also have custom taxonomy properties merged with the system taxonomy properties, like custom attributes, using Admin > Properties > Taxonomy Properties File.
- Form State encoding, used with Forms Management, has been updated to only encode less than (<) and greater than (>) symbols as opposed to all HTML. These symbols must be encoded to allow the Form State XML to make it through ASP.NET Form Validation, however, when all HTML was encoded it was forcing European characters to get encoded and cause a validation exception. We are hoping that this change allows the ASP.NET Form Validation to do its job with the exception of the Form State XML. Since this change affects all Forms Management forms, some existing forms may behave differently than before this update.
- Integration Id and Order attributes have been added to the Site Architecture > Taxonomy module. The Order attribute is used to sort taxonomy items within the parent item. This attribute will default to a value of 100 for all existing records maintaining the current sort order and allowing you to insert items before or after existing items. Taxonomy items are sorted by Order, then Name within their parent item. The Integration Id attribute was added to store the original identifier of taxonomy items imported from external systems.
See Full History of All Updates