Home»Support»Centralpoint Release History»Centralpoint Update 8.0.8
  • Printer Friendly Version
  • Decrease Text SizeIncrease Text Size

Centralpoint Update 8.0.8


Date of Update: Thursday, April 2, 2009  
  1. The cpsys_DataCurrent_Select stored procedure has been rewritten to allow NVarChar(MAX) length strings in the fields, columns, joins, where, and orderby parameters. This was implemented to solve problems caused by searches containing a large amount of criteria.
  2. The web site search has been updated to remove duplicate Structure / Modules records. Duplicate records occur when two Structure / Modules records have the same Module selected. The first record alphabetically is used based on the related Structure / Navigation record Title.
  3. The Generic module implementation has been changed to utilize 10 unique Generic modules as opposed to many Generic console navigation items relating to a single Generic module. This will cause data entered into any Generic module to appear in Generic A. If you were using any of the other Generic modules you should enable Generic A and change any generic aliases to Generic A. This change has also caused the loss of all custom Module Configuration data saved in the Generic modules. Module Configuration customizations must be recorded manually before the sync and reapplied manually after the sync.
  4. The sync process has been updated to exclude the Design folder in each web sites local folder. This will allow us to place documents in this folder related to a sites initial design and build. These files will not be overwritten by the sync and will be included in backups. Please use this folder instead of placing files or folders in the web sites local folder. A web sites local folder is the folder prefixed with “cpweb_”.
  5. A bug in the system has been repaired that caused custom module configurations to be ignored when the module was displayed in a data keyword list before the module itself was loaded.
  6. In standard modules the system is designed to ensure that console access in the main audience is always selected. This is intended to prevent a situation in which a record is inaccessible in all consoles. The Users and Roles modules utilize the standard audience selector with this feature disabled. After extensive tracing we’ve found and repaired a bug in the system that caused console access in the main audience to be added while deleted items are removed from the selector.
  7. Development / Errors modules have been repaired in Uber, Master, and Client Consoles. Previously errors containing HTML caused the display to break and/or would not display the error correctly. All message displays have been HTML encoded to display the HTML portion of the error when necessary.
  8. When an audience/role combination contains no related record in Design / Styles the web page will now display properly. The default design record, which has a disabled delete checkbox, will be used regardless of the audience, role, etc. selections. The system trace is used to record this situation if debugging is necessary.
  9. A note has been added to the client console view of a document’s historical versions to warn that the user that created a historical version is actually the user that made the changes to the document resulting in the generation of the historical version. It is not the user that created the content that was shown in the historical version. The person responsible for the content in the historical version can be found by looking up the earlier update in the audit trail.
  10. The client console navigation has been updated as follows. Please note that categories in the client console that display modules do not redirect to those modules. Instead, they are set up as a separate navigation item pointing to the same module. They are effectively another module and can be updated, managed, modified, enabled, and disabled separately. This means that if you disable Site Architecture / Navigation for a user they can still create navigation items unless you also disable Site Architecture.
    1. Structure => Site Architecture: Like Site Architecture / Navigation
    2. Admin / Administrators => Site Architecture / Administrators
    3. Site Architecture / Module => Site Architecture / Module Designer
    4. Site Architecture / Home Pages => Site Architecture / Homepages
    5. Form Manager => Forms Management: Like Forms Management / Forms
    6. Admin / Members => Members
    7. Advertising / Banner Management / Advertisers => Advertising / Advertisers
    8. Advertising / Banner Management => Advertising / Ad Tracking
    9. Advertising: Like Advertising / Advertisers
  11. A bug that caused the Attribute script to display improper data in Site Architecture / Module Designer when used with the DataInfo property has been repaired.
  12. The TaxonomyTree cp:control that is typically displayed on the module Details View (#3) is now supported by all module views. It has gotten two additional properties to support this change: WebSiteSearch and CurrentDataInfo. These controls have been documented in the client console help file titled “Modules” in the section titled “Related Taxonomy”.
  13. An attribute has been added to Structure / Modules / Home View (#1) called “Taxonomy Display Descriptions”. This attribute is only available when Taxonomy is utilized by the module and enabled using the “Taxonomy Display” attribute. This attribute can be used to hide the taxonomy descriptions. Hidden taxonomy descriptions are still searched by the module and web site search, but will not be indexed by search engines.
  14. Advertising / Sponsored Keywords has two new attributes: Url & Target. When a URL is provided the sponsored keyword will be linked to the URL using the selected target. Please remember that sponsored keywords are a client side implementation. They have little effect on the server load, but may not appear until sometime after the page has loaded depending on the client’s computer and browser. They are not intended for use as primary navigation items.
  15. Additional CpScripts have been added for use with Forms Management. The FormCaptcha CpScript was developed to add CAPTCHA validation to ensure that forms are not submitted by machines. The FormUpload CpScript was developed to allow file uploads. Visit the scripting help file for a description of all CpScripts.
  16. Design / Dynamic Feeds now allows any attribute in the selected module to be used in the 'Custom Order' attribute.


See Full History of All Updates