Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A workaround to use advanced features in iWeb 1.1' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A workaround to use advanced features in iWeb 1.1
Authored by: fitzage on May 23, '06 08:01:54AM

Perhaps people are ignoring the warning that iWeb will continue uploading in the background and they shouldn't quit it until it tells them it's done.



[ Reply to This | # ]
A workaround to use advanced features in iWeb 1.1
Authored by: mrgrieves on May 23, '06 08:20:01AM

There is a massive problem with the iWeb 1.1 update. Just take a look at the Apple discussion forums...



[ Reply to This | # ]
A workaround to use advanced features in iWeb 1.1
Authored by: georgepratt on May 23, '06 09:16:37AM

Apple posted a fix for the commenting issue and it seems to also have fixed other things as well. Disable Arial from your User fonts. If you have a page that uses Arial, you will want to rebuild it by copying and pasting into a new blog page.

Everything works now, comments, search, etc.



[ Reply to This | # ]
A workaround to use advanced features in iWeb 1.1
Authored by: fitzage on May 23, '06 12:57:51PM

That would explain why I didn't have any trouble. I try to avoid Arial whenever possible.



[ Reply to This | # ]
Arial avoidance
Authored by: sjk on May 23, '06 05:36:56PM
Reminds me of The Scourge of Arial.

[ Reply to This | # ]
A workaround to use advanced features in iWeb 1.1
Authored by: JonathanBoyd on May 23, '06 09:46:45AM

Actually, there are plenty of errors happening in the upload. iWeb is timing out prematurely and thinking the upload has failed, when it's still going on. If you leave it running after receiving error messages, then the upload completes, but anything using Javascript (i.e. comments, searching, slideshows and possibly a few other things) doesn't work and iWeb thinks that nothing was uploaded, so you have to reupload everything next time.

The suggested workaround circumvents this problem and allows you to make incremental changes to the site, rather than continuously having to publish all.



[ Reply to This | # ]