Re: Front page strikes

From: Rich Jordan (jordan_at_ccs4vms.com)
Date: 08/12/04


Date: 12 Aug 2004 09:24:18 -0700

sms@antinode.org wrote in message news:<04081013564828@antinode.org>...
> From: peter.watkinson1@ntlworld.com
>
> > 1. what's a multi-dot filename?
>
> A file name with more than one dot, like "a.b.c" (or as we'd say,
> "a^.b.c;1").
>
> Of course, the original report that they "fail" was less than fully
> informative. It'd be nice to have some details on who does what, and
> then what happens. Otherwise, it's tough to do more than guess at the
> problem(s).
>

My bad. It fails because its going to an ODS-2 disk. When the
webserver was set up, frontpage was not in the plans, and even if it
was, we didn't know that it would deliberately create unpleasantly
named files with no way to work around them. Needless to say they
simply didn't upload (ie failed). When we tested on another system
with ODS-5 disks, we had to place a set process/parse=extend in the
login.com for the FTP account, and add some DECC$ logicals to the
login.com for the webserver account to get things operational.

This system is going to be converted to ODS-5. The schedule for doing
so was based on planned installation of PHP, and possibly MySQL and
Python in a few months. The frontpage decision just blew the planned
schedule due to its unhappy filenaming conventions.

> > 2. Are you using M$ FP 2003 - with built in FTP? can't you use another
> > FTP tool and transmit in ASCII (if that makes any difference)
>
> My experience with FrontPage is nil, but I assume that it has a
> built-in FTP upload feature to send the local copies of files up to the
> Web server via FTP, and that it works with other servers, and that the
> users don't want to change their procedure to accomodate VMS. But
> that's just an assumption.
>
 
The decision on what to use was made by the customer, against our
recommendation. Why? Because they already have frontpage, and they
already have someone who knows how to use it (albeit in an all MS
environment), and they don't want pay for a better package, or take
time to learn it. Using an alternate FTP client may still be an
option if we can't work around the file attribute issue.

To be fair, this is intended for a fairly simple non-dynamic web
presence, three sites with probably no more than 5-10 pages per site,
and relatively low volume. A couple hundred page hits per day would
be surprisingly high.

Rich



Relevant Pages

  • Re: FP 2002 Wont upload since Windows SP2
    ... You are attempting to publish to a ftp ... To find the best Newsgroup for FrontPage support see: ... The web server may be temporarily out of service. ... | Windows SP2 has altered something to dampen FrontPage ...
    (microsoft.public.frontpage.client)
  • Re: MS Frontpage
    ... What errors do you get when you try to open the site in FrontPage, either directly or by using Internet Explorer? ... Do NOT use any FTP program - this will corrupt the extensions. ... Please check to make sure that the web server name is valid and your ...
    (microsoft.public.frontpage.programming)
  • Re: FrontPage API
    ... FrontPage uses the connection info / mechanism used by Internet Explorer. ... Starting an FTP Session ... The application establishes an ftp session by calling InternetConnect on a handle created by ... Enumeration of a directory on an ftp server requires the creation of a handle by FtpFindFirstFile. ...
    (microsoft.public.frontpage.programming)
  • Re: Opening web files via ftp
    ... that I was not sure about uploading a single page via FTP with FP ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... >> upload a single page to a FTP server. ... >> hosted on a Windows IIS server with the FP extensions installed, ...
    (microsoft.public.frontpage.client)
  • Re: Subsites Wont Publish Correctly
    ... get the FP extensions re-installed to ensure your use of FTP ... has not corrupted them, and republish using HTTP. ... > can suggest to them to make this work normally in FrontPage? ... >> The web site administrator is incorrect. ...
    (microsoft.public.frontpage.extensions.windowsnt)

Loading