G'day Howard,
Not sure if this is a help to you or not, but I gave up on the deployment
wizard in Studio4.5.1 because it only works if all your folders are
already created on the host, AND if you are uploading the entire project.
It's a bug in the software, and as far as I know nothing's on the slate
for a new version yet.
It's a pity because I used to use the deployment all the time in
Studio4.0.1 and found it one of the most useful features. Nowadays I
build a local version and use my reliable CuteFTP to upload it. And
CuteFTP doesn't cost nearly A$1000 either.
I think it's an outrage, and possibly even an infringement of the Sale Of
Goods act to claim Studio v4.5.1 works on Windows95/98 and that it will
automatically deploy your project. I've had a few sympathetic calls, and
one particularly helpful individual at Allaire in the USA call me over
several days to try to fix my Studio problems, but they steadfastly
refused to go away, hundreds of other people have the same problems, yet
Allaire haven't made any sign they're about to release another version any
time soon.
I'll continue to attack them until they do. If I built web sites the way
they build Studio, I'd be sued out of business by my clients.
Cheers,
Mike Kear
AFP Web Development
Windsor, NSW, Australia
On Wed, 22 Nov 2000, Owens, Howard wrote:
>
> This isn't work and I don't understand the error message. Any help would be
> appreciated:
>
> Using the deployment wizard, I created the following script
>
> // ===================================================================
> // Project Name: BreakingFolder
> // Date/Time Generated: 11/22/2000 11:10
> //
> // ===================================================================
> // Server List:
> //
> // ftp://wwwMySite
> // ===================================================================
>
> function Main()
> {
> var app = Application;
>
>
> app.DeploymentManager.OpenProject("F:\\site\\www\\breaking\\BreakingFolder.a
> pf");
> // ===================================================================
> // Set Deployment Flags...
> // ===================================================================
> app.DeploymentManager.CreateFolder = true;
> app.DeploymentManager.UploadOnlyIfNewer = true;
> app.DeploymentManager.EncryptCFML = false;
> app.DeploymentManager.ForceLowerCase = false;
> // ===================================================================
> // Server ftp://wwwMySite Deployment
> // ===================================================================
> // >>> Folder: BreakingFolder\breaking
>
> app.DeploymentManager.UploadFile("F:\\site\\www\\breaking\\breaking.shtml","
> ftp://www.mysite.com:21/www/breaking/breaking.shtml");
>
>
> app.DeploymentManager.CloseProject();
>
> }
>
> The error is:
>
> "No Deployment Folder Path for folder: breaking"
> and
> "No Deployment Folder Path for folder: images"
>
>
>
> =========================
> Howard Owens
> Web Producer
> InsideVC.com
> mailto:[EMAIL PROTECTED]
> =========================
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Structure your ColdFusion code with Fusebox. Get the official book at
>http://www.fusionauthority.com/bkinfo.cfm
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
