View Full Version : How to restrict FrontPage Access to a directory.

05-23-2006, 10:22 PM
I am working with a client and they use FrontPage to create and upload thier site. They know very little about FrontPage so I am trying to figure out a way that I can keep FrontPage from affecting a directory when they use it to update thier site. The reason for this is I have installed a simple php gallery for them and I don't want FrontPage to wipe out or change the php pages I created which I uploaded via FTP. I tried Google and did not come up with much (in fact it returned to threads from here on one attempt) and even tried searching the MSN FrontPage Knowledge base.

It may be I am useing the wrong terms. "FrontPage restrict from dirctories" , "Publish with FrontPage restricted" and a few other variations. I am normally pretty good and manipulating terms but think I just don't know enough about FP to get where I want. :) Not really in the mode to find a copy of FP and install it. :o

Any ideas welcome.

06-12-2006, 02:08 PM
I promise to post more on this tonight. I have some ideas and have dealt with having to keep people stuck in one directory with frontpage as to not mess up gallery or other kind of programs.

06-02-2007, 10:58 PM
Hi Shawn,

I have been using FP since back in the 90s, and have never had it affect any of my cgi or php scripts. The only thing I have noticed it does, and it ALWAYS does it, is it puts those _vti_cnf files in every directory, including the scripts directories, but it doesn't bother the scripts.

One thing I would suggest is to not work on the site offline (on your computer) then “publish” it, work on it online (on the server), and then “save” pages as you change them. It is much faster, and it doesn't affect any other directories/scripts, except the one you are working in. If you work offline, and then "publish," it has to go through EVERY directory and file, comparing times/dates/sizes to see what has been changed, what is new, or what has been deleted. And, it puts those _vti_ files everywhere to help it next time in this process.

Again, working on the site online; http://www.yourdomain.com is just like working on your computer, and you just hit save when finished. No mucking around in the other directories and/or scripts.

The downside, you only have one copy of your site that way, and that is the one online. But, about once a week or so, I "publish" the online site over to my computer to have a backup offline.

The downside of that, if you want to see it as a downside, is that it will bring your php and cgi scripts over to your computer when it publishes to offline.

Still though, it is faster and less hassle to just do the work online. I discovered this out of necessity, my main site is over 9000 pages, all created in FP, and making one change on one page and then publish... the publish took sometimes 10 - 15 minutes for FP to do all that comparing of dates, etc., and just wasn't feasible for one simple change.