Benches Apps and software

9

Forum discrepancy: how to FTP iWeb to Godaddy o...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I've been lurking on the forum and getting all sorts of good advice. Thank you everyone who posts here!

However, I've noticed a discrepancy about FTP'ing to Godaddy with authoritative advice-givers on both sides of the issue.

Here's the issue:

When you publish to a folder in iWeb, iWeb generates two top level documents: an index.html file and a folder named Site (by default, or whatever you may have renamed it in iWeb as your "site."). The index.html file also appears to be contained inside the Site folder along with all the other docs pertaining to your website.

The question is:

Which is better, to FTP both documents to the server, the index.html file and the Site folder, OR just the contents of the Site folder (and ignore the top level index.html file)?

There are multiple recommendations in this forum for both answers.

Here's one saying FTP both:

http://discussions.apple.com/thread.jspa?messageID=7986754&#7986754

Here's one saying FTP the contents of the folder only:

http://discussions.apple.com/thread.jspa?messageID=8050644&#8050644

If I understand it correctly, a benefit of uploading both is proper RSS notification. Is this correct and how important is this? Are there any other benefits or is this the only one?

On the other hand, the benefit of uploading the content of the Site folder only is that the resulting URLs do not include the word "Site" (or whatever you've substituted for it), following your domain name, and before your page names.

In my opinion, the website looks more professional and clean without the word "site" following the domain name and before the page name, so I'd therefore rather upload the contents of the Site folder and not the Site folder + the index.html document.

So... if I continue doing it this way, is there any serious drawback, or would this be the way to get the most professional-looking results hosting an iWeb site on Godaddy?

9 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    My answer to this question is that I always advise people to upload the whole site folder, plus the separate index.html file. If you start loading individual pages from the folder, you risk messing the site structure up and your site not working at all. I tried this with my own site at one time and it would not display correctly until I uploaded the whole site folder and then it worked perfectly.

    I always say that it is not the url of a site that makes it professional or not, it is the content and the design. When I look at a site, I always look at the content and the design and then decide, I don't immediately look at the url. If you really don't like the word site, then change your site name to something more applicable to your site. I named mine the first 3 letters of the title and it looks a whole lot better than site and I am happy with it.

    Remember that old adage never judge a book by its cover, well the same applies here, never judge a web site by its url!!

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ethmoid wrote:
    My answer to this question is that I always advise people to upload the whole site folder, plus the separate index.html file. If you start loading individual pages from the folder, you risk messing the site structure up and your site not working at all. I tried this with my own site at one time and it would not display correctly until I uploaded the whole site folder and then it worked perfectly.

    Thanks for the response.

    Is there any technical reason why loading the complete contents of the folder produced by iWeb '08 would imperil the site structure, or is this advice based on your one experience? My own experience is no problems at all uploading the complete contents of the main folder to Godaddy. So... has anyone else experienced problems?

    I always say that it is not the url of a site that makes it professional or not, it is the content and the design. When I look at a site, I always look at the content and the design and then decide, I don't immediately look at the url. If you really don't like the word site, then change your site name to something more applicable to your site. I named mine the first 3 letters of the title and it looks a whole lot better than site and I am happy with it.

    Remember that old adage never judge a book by its cover, well the same applies here, never judge a web site by its url!!

    Arguably a website is the "book cover" for whatever company, organization, or person it is about. However, I don't want to derail the topic into a discussion of whether a URL matters. For those for whom it matters, it matters, and for those for whom it doesn't, it doesn't!

    For me, it matters not because I care, but because I anticipate some of my visitors will care. So if I can serve up a professional-looking URL by uploading the contents of the folder rather than the folder itself, are there any compelling reasons, aside from not pandering to the superficiality of humanity, for doing it any other way?

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    For me, it matters not because I care, but because I anticipate some of my visitors will care.

    I'm curious whether you have ever seen evidence that visitors care about what appears in the address bar when they bring up a site. Or is there an online website style manual someplace that talks about this? It's not necessarily the same as your "URL", which is what someone needs to type to get to your site, and which is normally a lot shorter.

    I think the main reason for recommending uploading the full site structure, aside from the simplicity of just uploading 2 items, is that lots of users create blogs with RSS Subscribe buttons as part of their sites and the RSS will be broken if they do not.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, I have had personal experience of uploading individual pages from the site folder and my site did not work. When I uploaded the whole site folder the site worked.

    It also takes less time to upload the whole site than individual pages and as time is of the essence for me I do it the quick way. I really don't think that any of my clients really care about the url of my site and how it comes up. They are more worried about the information that they can get from the site.

    The last comment I had about my site was not the url, but the fact that the site itself looked good.

    I have to say that I agree with Tom on this one.

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Tom Gewecke wrote:

    For me, it matters not because I care, but because I anticipate some of my visitors will care.

    I'm curious whether you have ever seen evidence that visitors care about what appears in the address bar when they bring up a site.

    I have, but I'd rather keep this site about the technical issues of creating a website with a preferred URL, rather than if URLs matter or not. Perhaps that could be another thread.

    I think the main reason for recommending uploading the full site structure, aside from the simplicity of just uploading 2 items, is that lots of users create blogs with RSS Subscribe buttons as part of their sites and the RSS will be broken if they do not.

    Thanks. That appears to be the only current drawback.

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ethmoid wrote:
    Yes, I have had personal experience of uploading individual pages from the site folder and my site did not work. When I uploaded the whole site folder the site worked.

    I'm not sure what you did (did you inadvertently fail to upload every file, was it with an earlier version of iWeb, did something else possibly mess it up?), but it appears to be working now, under the current version of iWeb uploading to Godaddy. It works for me and others have reported similar success. I don't believe I've read any other reports of problems outside of yours.

    It also takes less time to upload the whole site than individual pages and as time is of the essence for me I do it the quick way. I really don't think that any of my clients really care about the url of my site and how it comes up. They are more worried about the information that they can get from the site.

    If you select all the contents of the folder (command-A) and drag them over to the upload window (I use Fetch), it takes exactly the same amount of time as selecting the folder and index.html file. Perhaps if you were loading individual page by individual page, that might account for the problem you encountered since it would be understandable if a page might have gotten missed using that method.

    As for the argument of whether your clients care about what their URLs look like, I'd rather not get into a discussion of whether URLs matter in this thread (certainly, a number of posters in this forum have stated that it matters to them; perhaps we should start a new thread tackling the "does it even matter" issue.)

    Thanks, though, for your feedback!

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    MattiMattMatt wrote:
    I have, but I'd rather keep this site about the technical issues of creating a website with a preferred URL, rather than if URLs matter or not.

    oops. meant to say "thread" not "site."

    That's one resilient little word there, "site," refusing to go away without a fight!

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have, but I'd rather keep this site about the technical issues of creating a website with a preferred URL, rather than if URLs matter or not. Perhaps that could be another thread.

    There was another discussion recently, though there the argument was that it was easier to remember the url for a specific page if it was shorter, rather than the aesthetics of what appears in the browser address bar:

    http://discussions.apple.com/message.jspa?messageID=8121926

  9. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Tom Gewecke wrote:
    There was another discussion recently, though there the argument was that it was easier to remember the url for a specific page if it was shorter, rather than the aesthetics of what appears in the browser address bar:

    http://discussions.apple.com/message.jspa?messageID=8121926

    That's actually one of the threads I link to in my OP. I think it's all part of the same issue and with the same solution - that user also got the results he wanted by uploading the folder's contents.