Quite often I find users not knowing how to upload their web sites with FrontPage, so I was wondering if anybody knows of a guide about how to do this?

I would write one myself, but I don't have FrontPage installed (can't stand that piece of crap... Must be about the worst piece of software on the planet).

nope but the book that comes with office/frontpage when you buy it does

9 whole pages on it
=)

Straight from the horse's mouth right here. (http://www.microsoft.com/office/frontpage/support/2000.asp)

You need to go down a couple of levels - look for "How to Publish a FrontPage Web"


Lats...

Urban, how do you even know if it works on your servers if you don't have a copy of it?

Originally posted by bitserve
Urban, how do you even know if it works on your servers if you don't have a copy of it?

Because other customers are uploading just fine, and this one particular customer said he didn't know how to upload into the "public_html" directory with FrontPage (it's a CPanel server).

I also checked the extensions on the account to make sure they were installed properly.

Hmm, from the tutorial, it looks like he needs to use www.hisdomain.com/public_html as the path, right?

Originally posted by avara
Hmm, from the tutorial, it looks like he needs to use www.hisdomain.com/public_html as the path, right?

And from his ticket, he said he had used www.hostit365.com/~hisusername as the path. Is that why it didn't work?

people should really learn how to use ftp, it's not that hard...

Originally posted by 311
people should really learn how to use ftp, it's not that hard...


Very True, and it will eliminate the need for Frontpage extentsion on servers.


Jim

Originally posted by jimb



Very True, and it will eliminate the need for Frontpage extentsion on servers.


Jim

While I agree with you, let's keep this on topic please. :)

So if his domain is example.com, and the files need to go into the public_html folder, how does he publish? Would example.com/public_html be his file path?

Thanks.

sorry about that,


Anyway, there is a way in Frontpage to set the publisher to the correct directory. Its probably in the subweb section or the upload options.


Jim

Originally posted by avara
Because other customers are uploading just fine, and this one particular customer said he didn't know how to upload into the "public_html" directory with FrontPage (it's a CPanel server).

I also checked the extensions on the account to make sure they were installed properly.

So you advertise FrontPage 2002 extensions, but you've never tested them? That's really brave. Could be a PR nightmare if they don't actually work.

Anyway, maybe you should buy it just so you can support your customer? Because this is actually pretty simple. Of course you use cpanel, so it's probably not so obvious, because you don't even have to know how to install the extensions, so you probably don't know how it really works.

When you create your customer's Root Web, or they do it in the control panel, if it supports that, the Root Web is created in their document directory. They're not using FTP, and so they shouldn't be specifying a path relative to their home directory. They should be specifying the path relative to the Root Web, by simply connecting to:

http://www.theirdomain.com

That's where the Root Web will be located, and they should be able to log into it with the FrontPage client.

Using FTP does not replace using FrontPage, because using FrontPage, you can use the server side extensions (read extended functionality). If you just use FTP, you can't use the extensions.

1. I did get a friend to test the FrontPage extensions before I advertised them
2. CPanel allows FrontPage extensions to be installed from the control panel
3. I'm using *nix only (no Windows), and Microsoft hasn't made a *nix version of the FrontPage package. I just got an emulator now though, and am installing FrontPage on my computer here as I am typing this
4. I do have a support staffer who is familiar with FrontPage, but he isn't here today so that's why I'm handling the support for this myself

But anyway thanks for the advice, I guess I felt like you were attacking me. I know that probably wasn't the intention. ;)

Originally posted by avara
...But anyway thanks for the advice, I guess I felt like you were attacking me. I know that probably wasn't the intention. ;)

I really was trying to be helpful with my last post. At the beginning I thought no help was required because lats had already posted a link, and so I was just asking questions out of amazement. Thanks for humoring me with your answers. It seemed like you were going to have a hard time making sure that it wasn't a client problem. :erm:

I hadn't visited the URL that lat's link references, though. Now that I have, the docs there do seem rather confusing.

When it says to use "http://www.microsoft.com/myweb", that's the user trying to publish to the web named "/myweb". This web isn't going to be there by default on most setups, but the Root Web is, which of course would be at "/", and not "/myweb". Hence, the reason it's called the Root Web.

If you think I can help, feel free to contact me.

Hello,

I just wanted to post the resolution to this problem, in case anyone else can learn from it:

The client had not updated his DNS servers yet, and was trying to upload to hostit365.com/~username instead of hisdomain.com. Once he updated his DNS servers, it all worked. Ya learn something new every day. :)

Originally posted by avara
Hello,

I just wanted to post the resolution to this problem, in case anyone else can learn from it:

The client had not updated his DNS servers yet, and was trying to upload to hostit365.com/~username instead of hisdomain.com. Once he updated his DNS servers, it all worked. Ya learn something new every day. :)

Aha. As a frontpage host, we've learned this lesson. Instead of suggesting that they use ~username to view their site, we tell them to add the domain name and IP addresses to their hosts file.


Want to work on your web site before the DNS transfer is complete?

If so, we always just recommend adding a hosts entry on your workstation. On windows machines, you can add the domain name to your \Windows\hosts file along with the IP address, and from that workstation, it will seem like the DNS changes have already been made. This is good for publishing the site, and setting up your email accounts, before the DNS transfer has occured.

Here are the entries you would need to make:

209.217.49.126 www.yourdomain.com
209.217.49.126 pop.yourdomain.com
209.217.49.126 smtp.yourdomain.com
209.217.49.126 ftp.yourdomain.com
209.217.49.127 admin.yourdomain.com

If the hosts file doesn't exist, you may need to create it as a text file.

On a Windows NT/2000 machine, this file is in \WINNT\system32\drivers\etc


We typically don't set up an account until the DNS changes are complete, though. But we do if they request it. For a seamless transfer from another host, of course it is often requested.