Frontpage 2003 Question

[Orlando Gondar]

I just install and tested the Frontpage 2003 Version.

I found a dialog with the TAB "FTP"
Under this tab is a list of files that will be transfered as TEXT MODE /
TEXT FILE instead of Binary.

Is this the case when you using forntpage extensions ?

Does cgi or pl files will be transfered as TEXT FILES, not binary ?

I think this was a problem in the past with those cgi - pl scripts

Is this problem solved on Frontpage 2003 ?

Thanks

 

[Thomas A. Rowe]

Only applies to publish to a server via FTP (a server that doesn't have FP
extensions or WSS.)

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Ronx]

In older versions of FP, .pl and .cgi files were always uploaded as
binaries, which usually resulted in corruption when uploaded to a Unix
server. In practice, this makes no difference when publishing to a Windows
server.
If you add the .pl, .pm and .cgi extensions to the FTP text list, FP2003
will upload these as Text files when you publish using FTP - I believe HTTP
publishing is unchanged, but have not tested this.
In any case, when uploading to Unix you have to use an FTP client to CHMOD
..pl and .cgi files, so you may as well upload them with the FTP client
anyway.

OT - Have you noticed that .css files are treated as binaries when FTP
publishing with FP2003? .css is missing from the list of text files.

 

[Orlando Gondar]

Thanks to both, ok so as ftp they will be loaded as text, but how do I
"CHMOD" the
files with frontpage 2003 ? This new frontpage is nice I also like the dual
display
your pc on the left and the server on the right for example.
I had not tested anything yet, but I presume that now you can drag and drop
like
other programs.

Thanks again.

 

[Ronx]

You can't CHMOD the files with FP2003 - you still need the 3rd party FTP
client.

Yes you can drag and drop between local and remote websites. However, the
sites will go out of synch. and require a full publish in one direction or
other to get back in step.

 

[Orlando Gondar]

So really we still with same problems
I should use Frontpage to just create the pages, but forget about that (
Pearl, etc )

 

[Stefan B Rusynko]

The normal practice (if your host supports subwebs) is to put all your perl scripts (and any filed they write) in a subweb which is
not published using FP
- say as a folder cgi-bin (right click to convert to web)
- that way you can FTP to that folder (and chmod it's files) only w/o affecting the root web publishing w/ FP and the FP SE
integrity




| So really we still with same problems
| I should use Frontpage to just create the pages, but forget about that (
| Pearl, etc )
|
| | > You can't CHMOD the files with FP2003 - you still need the 3rd party FTP
| > client.
| >
| > Yes you can drag and drop between local and remote websites. However, the
| > sites will go out of synch. and require a full publish in one direction or
| > other to get back in step.
| >
| > --
| > Ron
| >
| > Reply only to group - all emails will be deleted unread.
| >
| >
| > | > > Thanks to both, ok so as ftp they will be loaded as text, but how do I
| > > "CHMOD" the
| > > files with frontpage 2003 ? This new frontpage is nice I also like the
| > dual
| > > display
| > > your pc on the left and the server on the right for example.
| > > I had not tested anything yet, but I presume that now you can drag and
| > drop
| > > like
| > > other programs.
| > >
| > > Thanks again.
| > >
| > > | > > > In older versions of FP, .pl and .cgi files were always uploaded as
| > > > binaries, which usually resulted in corruption when uploaded to a Unix
| > > > server. In practice, this makes no difference when publishing to a
| > > Windows
| > > > server.
| > > > If you add the .pl, .pm and .cgi extensions to the FTP text list,
| FP2003
| > > > will upload these as Text files when you publish using FTP - I believe
| > > HTTP
| > > > publishing is unchanged, but have not tested this.
| > > > In any case, when uploading to Unix you have to use an FTP client to
| > CHMOD
| > > > .pl and .cgi files, so you may as well upload them with the FTP client
| > > > anyway.
| > > >
| > > > OT - Have you noticed that .css files are treated as binaries when FTP
| > > > publishing with FP2003? .css is missing from the list of text files.
| > > >
| > > > --
| > > > Ron
| > > >
| > > > Reply only to group - all emails will be deleted unread.
| > > >
| > > >
| > > > | > > > > I just install and tested the Frontpage 2003 Version.
| > > > >
| > > > > I found a dialog with the TAB "FTP"
| > > > > Under this tab is a list of files that will be transfered as TEXT
| MODE
| > /
| > > > > TEXT FILE instead of Binary.
| > > > >
| > > > > Is this the case when you using forntpage extensions ?
| > > > >
| > > > > Does cgi or pl files will be transfered as TEXT FILES, not binary ?
| > > > >
| > > > > I think this was a problem in the past with those cgi - pl scripts
| > > > >
| > > > > Is this problem solved on Frontpage 2003 ?
| > > > >
| > > > > Thanks
| > > > >
| > > > >
| > > > >
| > > >
| > > >
| > >
| > >
| >
| >
|
|

 

[Orlando Gondar]

Humm, I see your point and the technic, like I said before, I am new to this
hosting
technics, so do be suprice if I post any stupid question.

Thanks Again.

Hey how about using FP Extensions to upload the web, then go back with the
ftp
program and upload again those files in TEXT Mode ?

That will not affect the integrity since even if the date had change, the
file still there.

The normal practice (if your host supports subwebs) is to put all your

perl scripts (and any filed they write) in a subweb which is

not published using FP
- say as a folder cgi-bin (right click to convert to web)
- that way you can FTP to that folder (and chmod it's files) only w/o

affecting the root web publishing w/ FP and the FP SE

 

[Stefan B Rusynko]

You may be able to do that, but it is not recommended
When you work with / publish w/ FP it creates meta data files for all files in the site (including time stamps) and checks them for
compatibility when you reopen / publish the site
- If you FTP, FP knows nothing about the changes and if it can't resolve the differences it can often corrupt the FP SE (since the
meta data is out of sync w/ the FTPd files)




| Humm, I see your point and the technic, like I said before, I am new to this
| hosting
| technics, so do be suprice if I post any stupid question.
|
| Thanks Again.
|
| Hey how about using FP Extensions to upload the web, then go back with the
| ftp
| program and upload again those files in TEXT Mode ?
|
| That will not affect the integrity since even if the date had change, the
| file still there.
|
| | > The normal practice (if your host supports subwebs) is to put all your
| perl scripts (and any filed they write) in a subweb which is
| > not published using FP
| > - say as a folder cgi-bin (right click to convert to web)
| > - that way you can FTP to that folder (and chmod it's files) only w/o
| affecting the root web publishing w/ FP and the FP SE
| > integrity
|
|
|

 

[Ronx]

Using FTP on a FrontPage extended web is dangerous - the extensions are
fragile!
By using subwebs for FTP, and never opening those subwebs in FP, the danger
is reduced considerably, though never completely eradicated.

Your method of uploading Perl scripts will work up to a point[1] (the web
will be out of synch and FP2003 will report conflicts with the scripts),
but, in my opinion, you are taking a huge risk If *I could not use
subwebs, I would remove the FP extensions completely from the site, and
forget about http:// publishing altogether (and forego the use of any FP
runtime components like the hit-counter, form processing, discussion web,
publish changed files only, etc).

If your scripts write to files you will definitely need a subweb to contain
these files (which may be the cgi-bin). FP extensions will not be happy
about files that are changed or created without the extensions knowing about
them. Using a subweb means the main web is safe.

[1] If you FTP the scripts, and _absolutely nothing_ else the FP
extensions may survive (no guarantees). If you FTP a complete folder - the
extensions are doomed. If you even think about FTP ing a _vti* folder, the
web is gone.