Start with a SMALL site (in terms of numbers of tafs/tcfs to convert) ... 8)
The 5.5 server was prepped to ensure that your coding was really really tight. So a lot of stuff the older server versions would let you slide by with, will break the 5.5 server. Quote everything. Don't leave things implicitly stated ... E.g. <@assign this value-for-this> should be <@assign name="request$this" value="value-for-this"> Quoting is especially critical for things with embedded functions or terms like <@assign name="request$this" value="<@filter array='request$somearray' expr='#id = "<@var request$something>" '>"> or this <@if " '<@var request$this>' > '1' ">something</@if> Assign scopes to everything. And you're still going to find things that (unpleasantly) surprise you. Keep the Programmer's manual close by. If you start with a small site, you can use this to help yourself get transitioning more smoothly. I think it is WELL worth it, however. Your code will be far more reliable, and in the long run it's definitely the way to go. On Aug 10, 2010, at 3:28 PM, WebDude wrote: > > Folks... I am so excited about the latest developments, I almost peed myself. > I have been holding out for years on upgrading... pretty much because I spent > so much on the Corporate Server. But, since there seems to be new life being > pumped into the product, I am seriuosly considering buying, at the minimum, 2 > professional servers. The reason for this post is I have some concerns. I am > still using Witango 2000 and very happy with it. I have it installed on 3 > servers and never really had any issues. 2 of the servers are Win2k and one > is a 2003. We run about 70 websites, some getting about a half million visits > per month. I also have some very important corporate clients that are very > critical when it comes to uptime, speed, etc. (yeah, I know... but corporate > america can be kind of dumb when it comes to this stuff... still running such > an old version). Nothing is clustered, all servers are dedicated to specific > sites. All tie into a single database server. > > Anyway, I am going to be purchasing a few Windows Servers and would like to > load the new platform on them. I know there are some adjustments that will > need to be made. I believe that one of these is setting the default scope of > all unscoped variables to user... is that correct? What I need to know is any > other caveats that some of you may have run into. (i.e. do I actually have to > open and save each taf before they will work with a new server?) I am > thinking of porting 1 site at a time. I will have the luxury of having new > servers configured and ready to go along with the old servers. > > Any help would be greatly appreciated. I just landed some pretty hefty > contracts and would like to keep using Witango as it is my program of choice > for almost all of our development. I also would like to try to get Witango > into the mainsteam a bit more, too. Not sure how to do this, but I would > think if we could put our collective heads together, we might be able to come > up with something. I do work for some very big corporations and, though I > don't want to drop any names here, I might be able to get them to support the > product a bit. Not sure how to approach them, just thinking out loud. > Endoresements maybe? I am not sure how this stuff works. > > Thanks! > > > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
