MS FrontPage

Chapter 7 - MS FrontPage

Read This Intro First!
ALL of it!

Poor FrontPage. Nobody loves you. "Real" web designers wouldn't be caught dead using FrontPage to do client's work. Trouble is, Bill Gates has done such a good job of making it easy for the average Joe to create a reasonably acceptable website, that FrontPage websites are everywhere. As a result, if a hosting company wants to make any money, they have to offer the STUPID FrontPage extensions on the host server so the FrontPage web site will work correctly. But secretly, they hate FrontPage, and sometimes for good reasons; to be honest, FrontPage extensions are a pain in the backside to most hosting administrators. They are unstable, it takes NO effort on the part of the site owner to corrupt them, and the vast majority of people who use FrontPage not only know very little about web design, they know even less about the extensions and how to make everything come together as it should. SO, we end up having to chase after every little mistake a site owner makes, and often have to get on the phone and show site owners how to use their own software!! And this doesn't work, because NO hosting company knows the software, and only knows the extensions enough to install and re-install them. Is this what they call "The Blind Leading The Blind"? <GRRRRRRRRRRRRRRRR>

WELL! We are no different; we hate chasing after corrupted extensions too. So, we're going to make you this offer: You are in the right place. We know FrontPage, because we started in our homes using FrontPage, and cut our teeth on FrontPage 98 and 2000. We learned a lot and graduated to Dreamweaver, ColdFusion, HotMetal Pro, and other more sophisticated web design programs. Trust me when I tell you, the author has had more experience with FrontPage than any other web hosting company owner or chief executive. The author has ranted and raved at hosting companies, screamed at his computer screen and spent more time with the FrontPage help desk at Microsoft than he's willing to admit. You know what? 99% of his problems were of his own making.

If you learn nothing else in this diatribe, you must realize that CERTAIN ACTIONS ARE NOT PERMITTED on a FrontPage website. NEVER, EVER FTP ANYTHING TO A FRONTPAGE WEBSITE running Unix, or Linux operating systems that have the extensions installed. That means US! We are a Linux/Apache shop, and you simply CANNOT FTP files into a site with FrontPage extensions installed. You CAN do it on an NT machine to a limited degree, but even then you must be careful. On a Unix or Linux machine it CANNOT BE TOLERATED! SO, we will be watching! If you FTP something to your site and it has FrontPage extensions installed, we will notify the FP abuse police. :-) If it happens repeatedly, we WILL ASK YOU TO MOVE TO ANOTHER HOSTING COMPANY or, if we like you we will charge you extra for our hassle. We are serious. You must be willing to accept responsibility for your actions, and either read this manual and learn how to administer your site correctly, or please consider another hosting company. This sounds harsh, but you will end up exceedingly unhappy that your site is not working correctly, and it will not be our fault in 99% of the cases. Neither of us will benefit from the relationship. BUT, in an effort to save you endless frustration we are willing to go you one further than ANY other FrontPage hosting company. Call us if you have trouble with your SOFTWARE! That's right! We know how to make the program work, how you should best manage you files, and make you happy. We know shortcuts, we know things that Microsoft probably does not know about it's personality, limitations, and other idiosyncracies. We have resources world-wide. BUT; if we tell you how to do something, you MUST observe what we tell you about managing your site and interacting with the server extensions.

Fair enough? GREAT! Keep readin'... and PAY ATTENTION!

First and foremost, if you are still using FP98, do yourself a favor and upgrade to 2000. It is a quantum leap improvement over FP98. If you are still using FP97, you are way out of touch. We can't help you with FP97.

One recommendation we can make is that when your site is loaded onto our servers, from that point forward, do your best to do all editing live from the server, and not on your local machine and then subsequently uploading your work. One of the great things about FrontPage is the site management processes. It is so simple to open the site live on the server and do all maintenance. It's slower, but in the long run it is easier and MUCH less hassle. All you do to save your work on the server is hit "Ctrl-S" Plus, you eliminate the threat of your local machine crashing and losing all your work. And, you also eliminate the hassle of getting the PWS (Personal Web Server) to work. There are just times when PWS does not want to open, and there's very little you can do about it. I have had times that I tried to open PWS and no one could tell me why it would not open. Just eliminate the problem and work directly off the server.

MICROSOFT FRONTPAGE 98
Publishing a Web
Opening an Existing Web
Troubleshooting problems in FrontPage 98
Further Microsoft FrontPage Support

Publishing a Web

After you have built your html documents and are ready to upload them to our server:

1. Open the web you've created on your PC using FP Explorer.

2. Choose File > Publish

3. If your "Destination Web Server" doesn't appear in the Publish window (it won't the first time you publish to our server) CHOOSE "More Webs" and type the location of the web to publish to. Hit return. IMPORTANT: Use www.yourdomain.com as the Destination Web Server to publish to our server. Leave the "Destination Web Name" BLANK.

4. You will be asked for your USERNAME and PASSWORD. This is your domain's USERNAME and your FrontPage PASSWORD (which may be different than your regular telnet/ftp/POP password). If you're not sure what it is or if you aren't allowed past this point, you'll need to contact us for a new FP password.

5. You can watch the progression of the upload by looking at the bottom left corner of FP Explorer.

Back to the top

Opening an Existing Web

1. Open FP Explorer and choose File > Open Front Page Web.

2. You can now choose to open a previously created web on your PC or your web on our server.

3. Highlight the appropriate web or type in the web address (www.yourdomain.com) and click OK.

4. Enter your USERNAME and FP PASSWORD if required.

5. Make modifications and recalculate links if needed. (See FP help docs for info on when it's necessary to recalculate links.

Back to the top

Troubleshooting Common Problems with FP98

Getting error - "Root Web Busy"

FTP or telnet to your site and remove the "service.lck" file in /public_html/_vti_pvt. This usually happens when an FP session is interrupted before completion.

Server timing out when publishing large sites.

This difficulty arises when the uploading link times out in the process of copying the web to our server. The only suggestion Microsoft has offered so far is to break the main web into a group of sub webs on your PC, then upload these individually. If this problem persists for you, please contact support.

Getting Error - "Front Page Extensions not Installed"

We often see this error being reported even when the extensions have been installed. If you get this error, please contact support and we'll make sure the extensions are installed and repair them if necessary. NOTE: The extensions are easily corrupted. Please use only FP Explorer to update your web site on the server, not FTP.

I published but my web's not there!

This will happen when the "Destination Web Name" is filled in when publishing to our server.

This box should be left blank. If you put any other name in this box it will create a subdirectory off of your root web and copy all of your files into it. Your site will exist under a subdirectory instead of at the top level /public_html where it should be.

My counter, bbs, guestbook, etc isn't working.

These problems are generally due to incorrect permissions on either the directory, file(s) or cgi script(s) that are associated with them. Please don't change the permissions of your files or directories unless you have a specific reason for doing so and you know what effect it will have on your site.

My forms won't work through the Secure Server.

The call to a cgi script using the Secure Server must not be within a webbot. Use a normal cgi call in your html script for Secure Server calls.

My search bot doesn't return any results.

The /public_html directory must be world readable AND you need to recalculate links BEFORE publishing (or after editing directly on the server). If it still doesn't work: FTP to the server and go to the /public_html/_vti_txt/default.wti directory.Delete any files that begin with "ALL.". Don't delete any other files. Then using Windows Explorer, do the same thing on your PC. Recalculate links, test locally with your browser and publish.

FP starts the Web Publishing Wizard when I try to publish.

Cancel the operation and email support to have the FP extensions installed/repaired.

Why is my page renamed on the server when I publish?

The "Default Document" of your web is automatically renamed by the server to what is required by the configuration of the server. For example, if you've named the main page "index.html", it may be renamed "default.html". Just check the links to your main page to make sure they refer to it the same way.

Back to the top

Microsoft FrontPage 2000

This tutorial will guide you step-by-step through configuring Microsoft FrontPage to exchange files between your computer and your web site.

In order to follow along with us, you'll need to have Microsoft FrontPage installed, and you'll need to be connected to the internet via your Internet service provider

Create a Simple Page

Before you can publish an html file to your web site with FrontPage, you must either have a page already created, or create a page. To create a page with FrontPage, follow these simple steps:

1. With FrontPage open, choose File --> New.

2. Type in "This is a simple test"

3. From the menu bar, choose File --> Save As.

4. Name the html file.
(If this file is to be your homepage, be sure to name it index.html)

Once you have the file saved to your hard drive, you are ready to publish the file.

Publish Your Web Page.

1. From the menu bar, choose File --> Publish Web .

fp20001.gif (4071 bytes)

You'll get a dialog box like this:

fp20002.gif (2939 bytes)

2. Click on the Options button

You will see a dialog box like this:

fp20003.gif (4427 bytes)

3. In box below Specify the location to publish your site to: enter the full URL for your site.

4. If this is the first time you are publishing your site, select Publish all pages...

5. Select Include subwebs.

You should now have a dialog box that looks like this:

fp20004.gif (4546 bytes)

Obviously, you will have put your real domain name instead of 'mydomain.com'

6. Click the Publish button.

You should now see a dialog box like this one:

fp20005.gif (2944 bytes)

7. Enter your username and password.

If you have entered all the details correctly, FrontPage 2000 will then publish your site. You will see a dialog box like this one when it has finished:

fp20006.gif (2163 bytes)

8. Click Done.

Ah, if only life were that easy. However, with tempramental FrontPage, there is every possibility that you web will not transfer in it's entirety. If you get cut off, or if you try to upload your site several times and it stops in midstream (it doesn't matter what the error message says) more than likely your extensions were corrupted. This is not your fault! It's just the Microsoft way. Simply send me an e-mail and ask me to delete the extensions, and then immediately re-install your FrontPage extensions. I know this sounds round-a-bout, but if you try to re-install your extensions over corrupted extensions without first deleting the installation, you will only retain your corruption and it will not work. Don't forget; anytime you are re-installing your FrontPage extensions, and no matter who your host is, you must un-install (or delete) first! Un-install the extensions first!

1) First, ask me to uninstall the FrontPage extensions.
2) Then FTP approximately 80% of your site to the new server. Do not FTP your entire site.
3) Then, ask me to re-install your extensions. (stay with me here, I know this is wierd, but trust me...)
4) Then, go back to FrontPage, and go through the normal Publish process again. HOWEVER: Choose the "Publish changed pages only" option. This will pull in the pages you did not FTP before, and will result in a shorter upload time. When the upload is finished, FrontPage will automatically connect all your extensions, and your site will be fully functional.

Uploading your site will go a lot more smoothly if done from a DSL or cable modem connection.

Unfortunately, you will have some trouble uploading your site from one live server to another live server. I have done it, but it fails more times than it is successful. It will work a lot better if you do it from a DSL or cable connection. Try it first, and if it works, great, but otherwise you will have to backup your live site onto your local hard drive, and then upload the site from your local hard drive to the new server (us).

The Microsoft Frontpage helpdesk
number is 425-454-2030 and is available free of charge Monday - Friday, 5am until 8pm, and Saturday only 6am to 12pm, Pacific time. Have your serial number ready! You will have to give it to the gatekeeper when you make your initial call. The techies are very good. They are patient and knowledgeable.

Tom Brunt's Outfront Forums
http://www.frontpagewebmaster.com/
The best Frontpage discussion board on the web is Thomas Brunt's OutFront discussion board. The people there are great, very knowledgeable and will bend over backwards to help you with any problem you may have. I know these people intimately, so tell them you are hosting with me and you will be derided unmercifully (just kidding); actually you will be helped a great deal. In fact I can get on the phone with any of their moderators and work with them to solve your problem if I need to. Not every day, but on a sporadic basis we can go the extra mile to help or to accommodate.