cool thanks michael. We doing this on our DEV systems first to catch most of the bugs but your idea of the global error handler is a good one for when we push it live.
anyone else? jonese On Fri, 11 Feb 2005 10:07:22 -0400, Michael Dinowitz <[EMAIL PROTECTED]> wrote: > I moved directly from CF 5 to CF 7. The main thing to do is > 1. run the code analyzer > 2. Set up a global error handler that'll email you on EVERY error that > happens on the site > 3. do the move over late at night and then test the site to deal with > anything missed from the analyzer. > Not really that much to worry about. There's some small issues, but they're > easily caught. > > >All, > > We are in the process of moving our CF5 sites to MX6 or MX7. We > >have a custom built CMS which talks to a SQL 2000 server. > > > > I'm looking to compile lessons learned from those who've already > >gone through this in an effort to minimize my frustration when bugs > >crop up etc. > > > >Thanks in advance > >jonese > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:194256 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
