Skip navigation
This discussion is archived

Publish iWeb site to ftp root website.

21973 Views 52 Replies Latest reply: Aug 20, 2009 5:45 PM by Tom Gewecke RSS
  • Ethmoid Level 6 Level 6 (9,680 points)
    Currently Being Moderated
    Aug 4, 2009 12:49 AM (in response to StevePleasants)
    Unfortunately, that is just the way that iWeb is and has done things since it first came out as iWeb 06.

    Anyway, you don't have to have sitename.com/sitename.com - the second is up to you and you can go into iWeb and re-name your site something like Site or S so your then get domain.com/Site/pagename.

    If you try uploading in iWeb 09, have you tried going into iWeb and naming your site public_html or the same as the folder your host/server requires you to upload to? Try doing this and then when you click on ftp to server leave the directory/path blank and iWeb should just upload the contents of your site as you named the folder the same.

    Try this and see if it works.
    MacBook Core 2 Duo, iPhone, Mac OS X (10.5)
  • Ethmoid Level 6 Level 6 (9,680 points)
    Currently Being Moderated
    Aug 4, 2009 12:53 AM (in response to Looter)
    Try going into iWeb and re-naming your site public_html or whatever your host/server filename is that you are required to upload to. Then when you click on ftp to server make sure that you leave the directory/path section blank and in this way iWeb may just upload the contents rather than the whole site folder as you have the same name.

    Try it and see - several people have suggest that this alternative might work instead of downloading Cyberduck and uploading just the contents.
    MacBook Core 2 Duo, iPhone, Mac OS X (10.5)
  • Tom Gewecke Level 9 Level 9 (70,815 points)
    Currently Being Moderated
    Aug 4, 2009 4:20 AM (in response to StevePleasants)
    Is that why iWeb forces a directory on the remote server, so that there can be multiple sites on the same domain?


    Yes, I think that is the basic reason for the site structure.

    I don't buy my stuff at www.amazon.com/www.amazon.com/stuff.html, that's just silly.


    Surely you understand the difference between what is in the browser address bar and the url you give to people to go to your home page? No one needs more than www.mysite.com to get to your site, do they? Look at the address bar of your browser right now -- do you care what it says there?

    On the other hand, it's clear from many posts like yours that lots of web site authors do place great importance on what the viewer of their site will see in the browser address bar if he should focus on that instead of the site content. So you might want to ask Apple to provide more options regarding what to upload in future versions of iWeb here:

    http://www.apple.com/feedback/iweb.html
    iMac Intel/2C2D, eMac G4/700, Mac OS X (10.5), 10.4, 10.3, 9.2
  • StevePleasants Level 1 Level 1 (0 points)
    Currently Being Moderated
    Aug 6, 2009 5:26 PM (in response to Tom Gewecke)
    ok, yeah, as far as changing the site name, I did change mine to "steve" so I publish to www.mysite.com/steve/ and that is what the people looking at my site see. I think the average person may not notice that a site is published to a subdirectory, but I am a systems admin and all of my friends are either admins or developers, and without fail, every single person who I have shown my site has asked me why I don't publish to the root, or who else has an account on that domain, etc.. I notice things like that, and everyone I know notices things like that. It's not the end of the world. </beatingadeadhorse>

    As far as publishing to the remote directory, unfortunately godaddy dumps you right in the root, so it makes you publish iweb to a folder. Otherwise, yes, I would name my site folder_name for the html directory and then my welcome page would have to be named index I guess. But that's not going to work.

    So yeah, I am definitely going to submit a feature request, to bring iWeb up to the same level as other quality apps such as frontpage (yes I am kidding, don't throw things at me). As for now, I am going to purchase another web app and publish stuff to www.mysite.com and then change my site in iweb to be named iWeb, so I can have a few other things in the root, and then a link to like "here check out what iWeb looks like, I made the following with iWeb, which is a part of iLife, and came with my new macbook, yadda yadda" and then I guess when I publish from iWeb I'll have to tell it not to overwrite the index.html.

    But yes, believe it or not, not being able to publish to the root of your website is actually a big deal to a lot of people, even if some people don't think twice about it.

    So, for my solution, I'm going to need something that runs on this macbook that will publish to the root, preferably something freeware, or at least very cheap. Suggestions?
    macbook, Mac OS X (10.5.7)
  • Ethmoid Level 6 Level 6 (9,680 points)
    Currently Being Moderated
    Aug 7, 2009 12:56 AM (in response to StevePleasants)
    You can get the url that you want and publish to your root folder by selecting the ftp to a folder option from iWeb 09. Download Cyberduck for free and then use Cyberduck to upload just the contents of your site folder to your public_html folder at GoDaddy or whatever folder this is. Your url will then be http://www.domain.com/pagename. This is what I do and it works well for me.

    As far as other software is concerned, you will not get anything for free - things like Freeway, Karelia and Dreamweaver all cost. You could also try Mr. Site that you can purchase and get a domain name included with it - this is also Mac compatible.

    Otherwise your options for freeware are internet based - so something like http://www.wix.com. This is free and allows you to create your own flash site on the internet - you can upgrade your account though to get rid of the Wix advertising on your site or enable you to use your site with your own domain name.
    MacBook Core 2 Duo, iPhone, Mac OS X (10.5)
  • Alain from Quebec Calculating status...
    Currently Being Moderated
    Aug 12, 2009 8:32 AM (in response to Ethmoid)
    ****, there have been about 10 people who gave that solution before you. The problem was very clear dispite what some people have said.

    I am looking at a solution too.
    G5DP, 1.8Ghz, Mac OS X (10.5.6), 4gig ram
  • Jason David Cook Calculating status...
    Currently Being Moderated
    Aug 20, 2009 1:51 PM (in response to Tom Gewecke)
    Surely you understand the difference between what is in the browser address bar and the url you give to people to go to your home page? No one needs more than www.mysite.com to get to your site, do they? Look at the address bar of your browser right now -- do you care what it says there?


    I don't think anyone here misunderstands the difference between the function of the url and what appears in the address bar. Personally, my beef with iWeb's way of doing it is url simplicity NOT for the home page, but for subdirectories. With iWeb's standard publishing method, I can't just say to someone, "go to mysite.com/resume" or "mysite.com/blog" if these pages aren't the home page. You would have to say, "mysite.com/iwebsite/blog/blog.html". It's silly to have that redundant "iwebsite" directory and it's even more redundant still to have the "blog/blog.html" (I prefer an index.html in all of my subdirectories). Sure, at best you could say, "go to mysite.com and click 'blog'."

    So why is this a problem?

    If you try to maintain multiple pages (that are in many ways unrelated to each other) off the same domain using an overarching iWeb site, you end up with all these unnecessarily long urls. If you have a personal homepage with a freelance business page, portfolio page, and maybe a resume page off-shooting from there, you don't necessarily want to give a client or employer the link to your personal blog and say, "ignore that, just click the resume". You'd rather just say, "go to mysite.com/resume" or you may even have multiple business cards with the subdirectory addresses on them (one for your freelance page, one for your portfolio, one for your resume, assuming they're all unrelated enough to warrant separate cards – and yes, I know a lot of people like that).

    This might sound like a wonky scenario that the average iWeb user would never have to worry about, and I imagine that's likely true. But for the rest of us, we know what we're doing, we understand the ramifications of the current method and it incites an extra step (the Cyberduck method) that shouldn't be necessary. For a free, bundled app, iWeb is an extremely useful tool for web site development, even for savvy web developers when it comes to throwing up a quick, temporary page that already has some polish. That gets complicated, though, when it sets up its proprietary folder structure that doesn't conform to common standards of ftp organization. We're taunted with iWeb's should-be-handy publish feature because we actually have to work around it.

    I hope that clears up any confusion as to why people care about their url.

    Message was edited by: Jason David Cook
    Mac Mini, Mac OS X (10.5.8)
  • Tom Gewecke Level 9 Level 9 (70,815 points)
    Currently Being Moderated
    Aug 20, 2009 5:45 PM (in response to Jason David Cook)
    You'd rather just say, "go to mysite.com/resume" or you may even have multiple business cards with the subdirectory addresses on them (one for your freelance page, one for your portfolio, one for your resume, assuming they're all unrelated enough to warrant separate cards ... I hope that clears up any confusion as to why people care about their url.


    Yes, I do understand that. People who routinely orally transmit urls to specific pages surely want and need something different that what iWeb produces. Presumably even having .html at the end of what you have to say is annoying. Personally I doubt that iWeb will be modified to meet that particular need, but the more people send in reasoned feedback asking for this feature, the better chance it will have.

    Many other users just don't like the way it looks, and I think it may be hard to convince Apple that this matters.
    iMac Intel/2C2D, eMac G4/700, Mac OS X (10.5), 10.4, 10.3, 9.2
1 2 3 4 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.