Oh my word, every time I make a correction to my website it wants to upload the whole thing and NOT just the changes. What gives? I am running this under Mobile Me and it just started doing this BEFORE the update. Now that I have updated it... the thing continues to do this... Any thoughts as to why it has to publish the whole thing time and again rather then just the changes?
I posted this on my original posting, but will put it here too, FYI.
--------
OK - I just got done FIRST chatting with someone from MobileMe, and then on the phone with iWeb. Both sides had me go through many steps, none of which resolved the problem. I followed that up with MobileMe, and received this reply:
"Thanks for the update. I am going to contact a Specialist and see if we can get a case going with Engineering to figure this thing out. I will let you know as soon as I have any info for you, which will be today."
Let's all take a deep breath and hope this is resolved soon.
I have posted this problem in a super-secret place on the Apple Discussions.
I am also filing with Apple in another more super-duper secret place.
Seriously, I am.
So hold on...
Well ... this is probably not just a coincidence ...
*IMAP email notification has suddenly started working for me*. All on its own. Just in the last 3 or 4 hours.
IOW, in Mail.app, the 'new mail' sound is working when Mail arrives. This hasn't worked for me for over a year, since switching to IMAP MobileMe mail. In fact, it has never worked with my IMAP account.
It looks like Apple are hard at work on MobileMe and are working on the syncing/notifications, which may, or may not tie in with the iWeb issue.
Not sure Grant as I don't have those issues.
It does make sense that it's on "their end" as we all seem to have got this issue recently, and it started before the last update, so I don't think it's that.
I have filed with Apple in two places that get a good bit of Apple attention - let's see what happens.
Scott ... I'm not saying that the issues are directly related, but rather if Apple are working on MMe's server-side notification stuff, then perhaps it's tied in to iWeb's server-side notification/syncing stuff too.
Anyway ... Mail notification are definitely working for me. Amazing. 🙂
“ I still get the huge publishing error often about the temp files. I have no idea what this means or how to get around this one.”
I posted this on a related thread:
The Publish Error problem is an aggravating one with iWeb/MobileMe. It has nothing to do with bad files, nor does it seem to be caused by anything with your Website. Doing the usual troubleshooting remedies on a Mac does not help (deleting plists and repairing file permissions, etc etc). I've had to deal with it every time there has been a significant change to my computing environment, one that requires me to republish or refresh the entire site (I manage three large sites), like the recent iWeb 09 update. Because the sites are large, this is a serious problem for me (I outline a workaround below).
My suspicion is that the problem is caused by a communications error between iWeb (client) and the MobileMe servers, much like the communications errors that occurred in the early days of FTP and the Web. There's a lot of 'handshaking' going on when files are uploaded to a server, a back and forth between client and server to validate and confirm the integrity of the data being copied over. This communications error, at least superficially, appears to be random and also appears to affect some sites more than others. Such communications errors are often caused by dynamic timing issues (Internet traffic, speed, and bandwidth). Because so much is transpiring behind the scenes with iWeb sites, it's difficult to troubleshoot what is causing the problem.
I've spent a lot of time with Apple support (both iWeb and MobileMe) attempting to pinpoint the source of the problem, but this kind of technical problem is beyond the abilities of the front-line and second-tier support specialists. Unfortunately it's difficult to get to the highest level of support, the Apple “engineers”, so I still can only surmise what is causing this.
My workaround is to create a “dummy” second Website in iWeb, and to copy and publish the files in small groups to MobileMe. I do this by giving my original site a different name, and then to give the newly created Website the original name of the Website. This allows you to progressively republish the site to MobileMe. If you, on occasion, get another republish error, you need to go more slowly and only copy/publish a couple of files at a time.
This solution has always worked for me, but it is time-consuming and tedious. As others have said, iWeb/MobileMe is a terrific Web publishing environment, but these nagging glitches are frustrating. It's too bad Apple doesn't follow these discussions, and that they are not more attentive to user feedback to identify problems like this one.
You can publish to a local folder and upload the changed files/folders by drag and drop to Finder/Go/iDisk/My iDisk/Web/Sites.
Be aware that you loose the MobileMe specific functions like blog and photo comments, hit counter etc.
Yes. I am using a PPC G5 and started having the same problem several days a go. I have tried everything under the sun to fix it... and am glad to see (sorry to say) that that this is happening not only me. I even tried publishing the site to a non-mobileme location and the problem remains.
It started shortly after I got the recent update. This has gotta be a mobile me thing.
Not a MobileMe thing per se ... it's an iWeb publishing problem. Please call AppleCare and report your situation. Apple engineering is still collecting data on the extent of the problem, according to my phone call with them early this morning US Pacific time.
... It's too bad Apple doesn't follow these discussions, and that they are not more attentive to user feedback to identify problems like this one ...
Personally, I am glad that Apple's engineers are not here, but are accepting phone calls from us to gather details that will help solve the problem. When i talked to Apple this morning, their methodology and analysis of my meager situation was appreciated and well-received. It is by us contacting them and reporting the details THEY NEED that this problem will be cured ... not them wading through all these, "I'm down, too!" messages.
