RE: SPAM MESSAGE DETECTED- Webenergy Email Server: RE: Witango-Talk: Windows 7 Server
That’s awesome Robert! I just want to add that making the product better is important of course and keeping the development community happy. However, it’s equally important to attract new developers and grow the community. I’d be willing to help promote, market, and advertise with you if that’s something you are looking at doing down the road. WebLogoEmail Rick Sanders Canada: 902-431-7279 USA: 919-799-9076 www.webenergy.ca mcseSmall From: Robert Shubert [mailto:rshub...@tronics.com] Sent: Tuesday, August 10, 2010 7:52 PM To: Witango-Talk@witango.com Subject: SPAM MESSAGE DETECTED- Webenergy Email Server: RE: Witango-Talk: Windows 7 Server Here are a few points that may help you (and others) move forward… Any Witango 5.5 licenses which are purchased from now on will automatically get a v6 license when it is released. Version 5.5 is currently for sale at the same prices that v6 will sell at, and all discounts will also apply. Unfortunately we are not offering any upgrade discounts from pre-5.5 licenses, or from licenses such as the corporate which haven’t been sold for nearly a decade (or longer). Version 6 will have the same file format at version 5.5. TAFs and TCFs saved out of the 5.5 studio will run on the 6 server unchanged. Likewise files saved out of the 6 studio will run on the 5.5 server as long as you don’t use any new-in-v6 actions or tags. We are also planning the v6 studio to have a “save as 5.5” option to increase the backwards-compatibility. We want people to move freely between 5.5 and 6, at least in the near term. Upgrading from pre-5.5 to 5.5/6.0 does require a few steps. You are correct that the default scope changes from user to request (new name for local). However, you can optionally set this back to user if you prefer, perhaps just while you do your migrations. Also, the encoding types changed in 5.5, so you will need to do some find & replace with the new encoding names. There are two PDFs that you should review. One should be called “Witango Server 5 What’s New” (I don’t seem to have this document), and the other is “Witango 5.5 What’s New” (I’ll post this on the website soon). Together they explain all the changes and new features between your version of Tango 2000 and the current shipping version. I would also add that I personally believe that the 5.5.020 server is every bit as stable and capable as the Tango 2000 server. I’m not sure I would say that about 5.0 and earlier builds of 5.5, but the latest version is very good. We’ve tried to set things up now so that customers like yourself have the option to purchase new 5.5 licenses without penalty, and begin moving towards version 6. Thanks for the post and feel free to email or call me directly if you have any specific questions. Robert Witango Support From: WebDude [mailto:webd...@cipromo.com] Sent: Tuesday, August 10, 2010 3:28 PM To: Witango-Talk@witango.com Subject: Witango-Talk: Windows 7 Server 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 somethin
RE: Witango-Talk: Windows 7 Server
Here are a few points that may help you (and others) move forward… Any Witango 5.5 licenses which are purchased from now on will automatically get a v6 license when it is released. Version 5.5 is currently for sale at the same prices that v6 will sell at, and all discounts will also apply. Unfortunately we are not offering any upgrade discounts from pre-5.5 licenses, or from licenses such as the corporate which haven’t been sold for nearly a decade (or longer). Version 6 will have the same file format at version 5.5. TAFs and TCFs saved out of the 5.5 studio will run on the 6 server unchanged. Likewise files saved out of the 6 studio will run on the 5.5 server as long as you don’t use any new-in-v6 actions or tags. We are also planning the v6 studio to have a “save as 5.5” option to increase the backwards-compatibility. We want people to move freely between 5.5 and 6, at least in the near term. Upgrading from pre-5.5 to 5.5/6.0 does require a few steps. You are correct that the default scope changes from user to request (new name for local). However, you can optionally set this back to user if you prefer, perhaps just while you do your migrations. Also, the encoding types changed in 5.5, so you will need to do some find & replace with the new encoding names. There are two PDFs that you should review. One should be called “Witango Server 5 What’s New” (I don’t seem to have this document), and the other is “Witango 5.5 What’s New” (I’ll post this on the website soon). Together they explain all the changes and new features between your version of Tango 2000 and the current shipping version. I would also add that I personally believe that the 5.5.020 server is every bit as stable and capable as the Tango 2000 server. I’m not sure I would say that about 5.0 and earlier builds of 5.5, but the latest version is very good. We’ve tried to set things up now so that customers like yourself have the option to purchase new 5.5 licenses without penalty, and begin moving towards version 6. Thanks for the post and feel free to email or call me directly if you have any specific questions. Robert Witango Support From: WebDude [mailto:webd...@cipromo.com] Sent: Tuesday, August 10, 2010 3:28 PM To: Witango-Talk@witango.com Subject: Witango-Talk: Windows 7 Server 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 lists...@witango.com with "unsubscribe witango-talk" in the body. To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
Re: Witango-Talk: Windows 7 Server
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 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 lists...@witango.com > with "unsubscribe witango-talk" in the body. To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
Re: Witango-Talk: Windows 7 Server
On Aug 10, 2010, at 12:28 PM, WebDude wrote: > > > 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? It's correct that you should not make user the default scope. Best to make request the default scope. To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
Witango-Talk: Windows 7 Server
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 lists...@witango.com with "unsubscribe witango-talk" in the body.
