Hello Don
This is a pretty full-on discussion I see and I don't want to drag it on, but...... On 01-Jan-02, you wrote: > There is a stable version, 3.2.13, which is for regular browsing (with > JS disabled). > > Beta versions are for _testing_. Granted. However: >From memory we are kind of stuck between a rock and hard place. Here is the situation as I see it. (Speaking for myself, but I am sure that the bigger picture is true all the same.) 1) Given we have a "stable version" as you call it and we use it. A Beta is released. No one uses it because it has a timeout function, so how do you find out if there are any problems? 2) It is used by people and problems are found. Alas it times out. In the mean time though natural disc space usage, the earlier betas and coppies are deleted. The user is then unable to get the new beta/version. Possible solution for everyone who is now stuck like me. Instead of HTTP:// to the site FTP:// to the site. Ofcourse VAPOR would have to allow FTP access to the site too. I don't know if that is allowed now anyway. I am only presenting options/ideas. Regards -- The 3 stages of marriage: lust, rust and dust. Andrew Bruno [EMAIL PROTECTED] _____________________________________________________________________ Voyager Mailing List - http://v3.vapor.com/ Voyager FAQ....: http://faq.vapor.com/voyager/ Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
