Your best friend for file transfer.

Fetch application logoFetch

Possible workaround for iWeb mirror problem (3 posts)

  • Started 10 years ago by Joe_dEon
  • Latest reply 10 years ago from Joe_dEon
  • Joe_dEon Member

    When you publish to a folder with iWeb, it makes all the files in the folder "new" even though it doesn't need to. This means mirroring the local folder to the remote site will only result in a complete update every time.

    Here's a possible workaround:

    Publish from iWeb to a (private) .mac site and then mirror the iDisk folder where the site resides to the site you want public.

    This is not ideal since it requires having a .mac account, but it gets around the bandwitdth limits of .mac. It also lets you have the benefits of the hosting company's stats and service.

    Does anyone think this would work?

    Posted 10 years ago #

  • Scott McGuire Administrator

    Hi,

    We do not know if that would work or not; please let us know if you give it a try.

    Thanks for the suggestion,

    Scott McGuire
    Fetch Softworks

    Posted 10 years ago #

  • Joe_dEon Member

    Well, I haven't actually tried it, but I did look at my iDisk contents after a web site update from iWeb, and it did not overwrite everything. The "date modified" field showed different update times for each update from iWeb. So it seems like it could work.

    That's the good news, but then once you have the site up at .mac, you have to mirror to your remote site, and that comes with the usual web site mirroring limitations (items that have changed on your public site due to comments etc... will not be reflected on your dot mac site).

    It's just too bad dot mac is so limited (no stats, limited bandwidth, no archiving, etc...). the workflow (for a podcaster, anyways) would be ridiculously simple: create in Garageband ---> "share" to iWeb ---> add pics or whatever ---> publish!

    Posted 10 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.