- Center (Above Content) and Center (Below Content) options have been added to the Advertising > Advertisers > Position attribute for use with Centralpoint’s Default Site Type.
- The web.config file of all web sites and master consoles will have the mostRecent attribute of the trace element set to false. This change will not affect sites unless tracing is enabled, but when enabled it will make it easier to utilize the trace in high traffic sites. With this feature disabled the trace will only contain the first 50 pages since the last time it was cleared, but you may change this setting back manually if you prefer it enabled.
- A new QRBarcodes CpScript has been developed to generate quick response bar codes.
The next update package, v8.1.0, will upgrade all Centralpoint sites to ASP.NET 4 (http://www.asp.net/LEARN/whitepapers/aspnet4). This update requires changes to both IIS and the web.config files which will be applied automatically to all sites during the update installation. The update containing this upgrade (v8.1.0) is scheduled for release on August 29, 2010. Before installing this update you must ensure that the .NET Framework 4 is installed on your web server and that ASP.NET 4 is Allowed via IIS’s Web Service Extensions. The .NET Framework 4 is an optional windows update and you should check for important updates after its installation. Please disable your server's auto update and sync via the Master > Content > Scheduled Tasks module if you are concerned with this upgrade or would like more time.
The current update package (v8.0.65) executes a method that will check your server’s ability to automatically upgrade and send a report via the Development > Errors module. A representative from Oxcyon will contact you to schedule a manual update if this report provides any evidence that the automatic upgrade will not succeed. Microsoft has provided a list of migration issues (http://msdn.microsoft.com/en-us/library/ee941656.aspx), and all standard Centralpoint features have been tested and updated to prevent problems. If you have produced any custom development on your server, you may want to review these issues and keep in mind that the upgrade will set all sites to controlRenderingCompatibilityVersion=”3.5” and clientIdMode=”AutoId” for backward compatibility. We expect only minor upgrade issues, if any, even within My Modules. If you have added any custom httpModules or httpHandlers in your site’s Root web.config file you will need to manually add them back after the update.
Your site’s web.config file will be automatically backed up in the Backups folder before it is modified. The upgrade will also modify IIS to place the Master site in a new app pool called cpsys_Default and all web sites and consoles in one called cpweb_Default. These new app pools will be created using the settings applied to the Application Pools folder in IIS. If you had a custom app pool configuration, you’ll have to ensure your app pools are running only ASP.NET 4 sites first, then reapply them manually after the update.
See Full History of All Updates