FronPage 2003 and file/directory names that begin with a .

C

Cory C. Albrecht

Hello all,

Anybody know how to get FrontPage 2003 to not puke when it comes to file
names or directory names that begin with a "."?

I got the FP2K3 evaluation version from Mcrosoft to check it out since a
lot of clients (and potential clients) use FP of one version or another.
However, the server for my personal home page is Linux+Apache, which
means that I have many files and directories which start while a "."
(which on un*x is essentially equivalent to the Hidden file attribute in
FAT & NTFS). if I try to synchronize the local & remote copies, or
download a file that starts with a ".", FP2K3 tells me "Server Error:
The URL: '.cpan' is invalid. It may refer to a nonexistent file or
folder, or refer to a valid file or folder that is not in the current
Web.". Now, obviously, that is a dumb thing fro FP2K3 to say because the
URL is not invalid. How the heck does FP deal with common files like
htacces, .htpasswd or .htgroups?

Also, FP2K3, in the folder list, wont even let me create a directory
called ".cpan" -- when I hit enter it just goes back to "New-Folder".
Especially dumb, because in Windows Explorer I can make a diretcory
called ".cpan", but FP2K3 never sees it on either the Folder list or the
local website view.

Because of this problem, I have to go through each diretory and
subdirect and manually transfer each and every file that has changed,
instead of just setting publish to synchronize and hitting the button.

Is it possible to get around this limitation in FP2K3?

<rant tone="quite annoyed">Who were the doofuses at MS who made the
decision to have FP act like this? Might as well go back to just using
vim and ncftp - since that would work just as good as FP2K3.</rant>
 
K

KingDavid

Cory,

I have found that synchronizing with the remote website is a losing option.

After I regretfully synchronized the website, the problems started.

The way around it was to clean up the website on my computer by eliminating
all the other "stuff" on my remote website that was downloaded to my
computer. Basically starting with the original website on my computer
before the sync.

Next, I published the website on my computger to a new directory on my
computer.

Then I published the new clean website to the remote internet site and the
problems ended. I will not sync them again. I have about 20 websites and
it seems to solve the problem.

Please note that on one occassion the problem was related to reaching the
limit of disk space on the remote server. Is seem the FP2K3 uses bigger
temp files.

JohnW
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top