Publishing Problems - a Solution?

Question

For a long time I'd sympathised with all you people who'd been having publishing nightmares, even though I've been updating pretty much error free since iWeb 1.0
Then last night after updating my blogs and making a few changes, I finally got the dreaded error messages. Tried a few times, got frustrated, and decided to sleep on it.
Same this morning ... grrr ... but then I noticed that my iDisk had failed on auto-synchronisation.
I'd only mounted my iDisk recently to amend my Podcast feed, so on a hunch I unmounted iDisk, rehit the Publish button in iWeb, and holy shmoly – it worked straight off!
I reckon that publishing iWeb kicks off the iDisk auto-sync, and then you've got a conflict with iDisk and .Mac trying to outsync each other.
Anybody else found this? if this solves publishing problems for a few of you then great. If it works for a lot of you, even better. If the majority of you get sorted, then that's a revelation!
Dual 2.3 GHz PowerPC G5   Mac OS X (10.4.6)  

Answer 1

My message to Apple stated:
"My pages go through the "create" process then start
on the "publishing" process then come back with an
error message that tells me to check my internet
connection (which is fine at 2 different locations. I
spent 13 hours fighting this yesterday. It has
created a major problem for me -- and this just after
I paid an extra hundred dollars to upgrade my
broadband. Your telephone people tell me you're
working on this. Please advise when it will be fixed
so I don't waste another 13 hours today."
Regards,
Richard M.
Richard, thank you for writing this. I would like to know how this all shakes out, and I am glad that it is an Apple server problem and not mine.
Meanwhile, I want to say how helpful it is to have this iWeb forum, and also thank the very generous and thoughtful souls who take the time to help beyond what normally would be expected. Those people know who they are, but I also am grateful to everyone.
For example, I was greatly relieved to read that I was not the only person getting Network Failure messages, since it meant that probably I was not working with a defective application -- one that started out fine but somehow went south on me and would not be replaced by Apple. This may seem a trifling thing to some, but when you are in a spot that you perceive as Hot, assurance from the outside is very much appreciated.
I hope that when you all finish your websites, you post the URL so we can all see it; after all, in a sense we are all comrades in arms (because sometimes it can seem like a war, due to the Fear Factor) and our fates are somehow connected even though we are all so-called strangers.
— Lorna in Southern California