Centralpoint Update 8.0.34

Date of Update: Monday, April 26, 2010

The next run date is now calculated based on a combination of the last run date and the time portion of the start date as opposed to the last run date alone.
The system has been updated to support scheduled tasks executed directly from web site modules.
The scheduler now only executes one master task per web service call. This was implemented to prevent problems that are a result of one task expecting a change made in a previous task.

The Development > Errors module has been updated to hide the values of form elements containing the words “password”, “cardnumber”, or “secure”. Be sure that the id of the form element contains one of these words if you are creating a form element and do not want the value to be included in this module. This module also now displays the full date and time in the Create Date column of the grid view.
Master > Content > Web Sites > Related Backups has been repaired to accurately display the backups for the currently selected site.
It was recently discovered that web sites are utilizing the master connection string used for the activation of Centralpoint on a new server instead of the actual master connection string. While this works in most cases it may cause problems when the master connection string changes.

The activation process has been updated to change the master connection string in the development web site after it is created.
The Master > Admin > Settings module has been updated to update the web.config of all web sites when the execute connection string changes. The Web Site > Console > Admin > Settings modules no longer allows changes to the master connection string.
A sync invoked method is included in this update that will modify the master connection string of all web sites.

The shared method used to insert and update Centralpoint documents has been enhanced to handle single document relation population errors. These errors are typically caused when module configuration is used to hide a required and/or validated attribute, and causes more serious problems if changes are made to the relation in the future. The new error handling includes a more detailed error message and moves the invalid document to the related module’s Recently Deleted documents. The document can typically be restored by using module configuration to display the problem attribute and selecting a valid value before restoring the document.
The error handling around dynamic control creation (Custom Attributes and Console Triggers) has been updated to help pinpoint the cause of the problem.