> Can we be fairly certain that sites created with this Release Candidate will not be broken when 1.0 is released?
Shouldn't be a problem, Angel. Sites created with Public Beta 7 aren't broken when the RC was released, either; you just have to be careful about retrofitting the site with new versions of the files that changed (most of them are listed in bold in the release notes, but I just spied a couple that I missed), and making sure that any customizations you've added to the Public Beta code are carried forward into the new Release Candidate code. For example, when I upgraded ProductivityEnhancement.com to the new CMS today, I just had to upload the custom tags and includes libraries, Content.cfc from the components library, and the content directory. The only thing I had to retrofit was to add the one line of code that derives Application.absoluteUrlRoot in Global.cfm and uncomment the line of code that enables ActivEdit in the content add and edit forms, then I had to re-run setup/Setup.cfm. These were the only things that were important to us right now on the production site, but I plan to retrofit the rest later. Respectfully, Adam Phillip Churvis Member of Team Macromedia http://www.ProductivityEnhancement.com Download Plum and other cool development tools, and get advanced intensive Master-level training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************
