You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iWeb Crashes on Publish

Hello all,

iWeb crashes when I publish. I can not publish to a folder, publish all, or publish. It seems to crash around the same place, but I can't say it always crashes when it's on the same item.

I've tried to boot into safe mode and publish, but still no luck.

It's relatively small... 60 or so blogs and about 2 dozen photo pages.

I'm travelling so I don't have access to anyone else's machine to try swapping around the domain file.

I'm cranking on an intel Macbook Core Duo 2 GHZ with a gig of ram and plenty of hard drive space.

Thanks in advance

Macbook Core Duo 2.0, Mac OS X (10.4.9), 1 GB RAM, 120GB HD

Posted on Apr 12, 2007 3:59 PM

Reply
77 replies

May 10, 2007 10:01 AM in response to ScottDirect

I'm also running 2GB of Apple factory installed RAM.

At the moment, after my purge of old blog entries (described above), I am still having no problems. In fact, it's publishing faster than I ever remember seeing it Publish.

One thing -- among the blogs I zapped was one that included an audioclip (a fairly large one at that). Could the inclusion of audioclips/podcasts inside blogs have something to do with this?

May 10, 2007 3:07 PM in response to zencat

I've got a GB of Ramjet RAM which has an awesome reputation.

I have no audioclips/podcasts in my blog. I do have a couple videos, but they are tiny - around 300k each.


I have some videos in non-blog pages that are bigger, but I put ALL of these videos in pretty early on in my iWeb usage when publishing was no problem.

How do you guys add pictures? Do you resize them first? I did for the first 3 months of usage, but for the last 4 I've been drag-dropping from iPhoto.

How big are your Domain files?

-Mark

May 10, 2007 5:00 PM in response to Mark Sansone

I just drag and drop my pics (unless they are HUGE, then I resize). One thing, I do change my photos to pngs because that prevents the annoying white line across the top that sometimes happens when when you published jpgs (another fun little iWeb bug).

Domain file is 283.5 MB. At the height of my problems (before my blog purge) it was 310 MB.

May 11, 2007 2:49 AM in response to ScottDirect

Mine's 2.45 GB.

I was thinking that domain size might have something to do with it, but if you guys are 300MB and 1.15 GB with these problems, then we're all over the gamut with sizes.

I tried to start a thread to get an idea of what everyone else's were like, but it got hijacked.

Anyone else have domain sizes? Even if you are still able to publish, I'd love to hear what domain sizes are like.

May 11, 2007 7:51 AM in response to Mark Sansone

I solved my publishing problem (for now) by taking the following steps. My file is about 180 megs.

Re-install the iWeb Application. First move the iWeb application in the Applications folder to the trash.
Then go to the root library and trash any Receipts that start with iWeb. Then install iWeb from the disk. (click on custom installation and select only iWeb.) Then get the update from the Apple website and run the update. Then do a software update from the Apple menu.

Remove any routers from your connection to the Internet. Your connection should be directly off your cable modem, etc.

Once you have reinstalled iWeb, do a restart.

Set your energy settings for 3 hours sleep for the hard disk. iWeb does not like the computer to fall asleep on the job.

Launch iWeb.

Then login to the .Mac server by going to Preferences/.Mac and select at least one other tab to login. Then quit Preferences.

Make a small change in your iWeb document so that you will be asked to save upon quitting the application.

Quit the application and click Save in the dialog that appears. After the Save click Publish in the next popup dialog. Good luck and let me know.

Cheers, Gerry

iBook G4 Mac OS X (10.4.8)

May 23, 2007 4:46 PM in response to grudy

My latest:

Still haven't had the chance to try a fresh copy of iWeb. However, I met up with a fellow traveler who had a MBP 2.16 with 2GB RAM.

Gave him my domain and sure enough it crashed.

Still no consistency of which page/file it crashes on. His machine went further than mine has in a good long while.

hrmph. Any other insights? Any other conversations with Apple?

May 23, 2007 5:13 PM in response to Mark Sansone

Important: Install a fresh copy of iWeb as per my instructions in a previous post.
Before publishing, do a save, quit and restart. Do not start or have any other application other than iWeb running when you publish and have a direct connection to the internet (no routers, etc.) Before publishing, Log-in to .Mac by opening the Preferences panel from the Apple menu at the top left of the computer screen. Click on .Mac and then choose one other tab such as synch and then quit Preferences.
You also have to force a Publish All by adding a new page (choose not to show in navigation menu from the Inspector panel). The next time you publish, delete this page and this will also force a Publish all upon quitting as per above instructions. Do not use the publish button but instead publish from the pop-up dialogs that follow a quit with unsaved changes (add a space somewhere before quitting)
It works for me. Why don't you try it as outlined? Does anyone else have any questions or comments?

Gerry

iBook G4 Mac OS X (10.4.8)

May 26, 2007 5:54 PM in response to Mark Sansone

I've fixed my problem with iWeb crashing when publishing.

I went into the package and removed any image that was larger than 1MB in size. This included JPEG, RAW, TIFF, and PSD file. These were all moved into a new folder on the desktop. From there I processed each one using a Photoshop action to save the image as a LEVEL 0, JPEG file. This produced images about 200K in size.

For all images that were JPEG before this started, I copied them back into the package. All of files that were converted to JPEG from the other formats were then imported into iPhoto.

I then re-launched iWeb and looked for all the placeholders where an image should have been but no longer existed. For each image, I took the new photo from iPhoto and placed it back into my website.

It now works. It also works much faster than before. I think that the iWeb folks are expecting people to be using 4MP cameras, saving them as cheep JPEG images. I only shoot RAW, using a Canon D10. Post processing these images (with at least 1 adjustment layer) makes them all about 16 MB in size.

iWeb just doesn't work well when it must scale images.

Good luck to all here. I've found that this seems to work for me, I hope that it works for you.

It was the discussion here that gave me the idea to reduce the size of my images, as others mentioned that the size of the website being managed was large. Mine started at about 1.6GB (really Gigabyte) because of the photoshop images. It is now 35 Meg.

I sure hope the next version of iWeb is better at handling large sites than this one. It's been a long wait.

May 27, 2007 5:09 PM in response to Mark Sansone

Thanks to all of you that have suggested fixes. I haven't done any of these things because, frankly, I started using iWeb so that I wouldn't have to go through all sorts of contortions to have fun on-line. If I wanted to suffer through the sort of things that you guys are (heroically) doing, I'd own a PC.

For now I'm publishing OK having gotten rid of an old blog that I'm no longer using. I suppose it's fine to use iWeb as a way to communicate without actually having a lasting archive of it. So disappointing though.

Again, thank you sincerely for your suggestions, folks. If I get ambitious I just may try it.

MacBook Pro Mac OS X (10.4.7)

May 29, 2007 4:38 AM in response to kdbarto

So, I made a droplet from ImageReady to downsize my images. I dupped the domain file and downsized pretty much all of them.

I then had to make an automator action to delete "-01" from the end of all the images.

Whatever, all that was not a big deal.

iWeb launched very quickly (1-2 mins?) and I tried publishing straight away. Turns out I was missing an image so I got an error.

Embarrased, I found the original in the backup domain, downsized it, and stuck it in the new domain.

iWeb crashed while opening. Hrm.

I stuck the original into the domain. iWeb crashed while opening.

I removed the image completely. iWeb crashed while opening.

I used the original domain, and I'm back to square one.


This all took me a few hours between reboots, file conversions, and iweb openings/closings/crashings. So, I'll give it another whack tomorrow I guess.

Looks like it might be promising.


ScottDirect, the only reason I started using iWeb was because I thought I wouldn't have to deal with converting files or anything technical for that matter. hrmph.

-Mark

May 29, 2007 9:50 PM in response to ScottDirect

I did bring the matter to the attention of the genius bar as well as the studio creatives and they all agreed I needed more memory and an external hard drive just in case something really bad happened.
I got the external hard drive but not the memory because I didn't feel that it was a convincing solution.
Based on other suggestions of theirs and of another iWeb blogger I did all of the following:
1. Reduced number of entries on main blog page to 10.
2. Exported photos for each blog entry, from iPhoto to a temporary desktop folder, resizing them before export to something like 400x300, then dragged them into the placeholder as well as into the body of the text. When I drag to the text I hold down ctrl and apple then click on the photo and drag to text. Text will light up blue around edges and image will plop in there, then will move with text (won't really wrap in the sense that I can't get text around the image, just above and below).
3. No cute browser background with tiled images or color.
4. No fancy fonts.
5. Before publishing exit from safari.
6. To publish (and they suggested this at the apple store) don't hit publish in the lower left corner of iWeb, nor Publish All in the menu, because these republish the WHOLE thing every time and take f o r e v e r . Instead, choose "publish to .mac". This wil publish only the new entry, any ones you have made changes to, as well as the main blog page and the archive.
7. I went back and replaced the images in some of the previous entries with resized ones. But not all because it was a pain.
This has helped a lot.
A fellow iWeb blogger said that she saves, then closes iWeb, then reopens it and publishes, and that this has helped her. She has had to start her blog over twice because of corrupted data.
Wish I had started with Typepad instead of iWeb.



imac Mac OS X (10.4.9) intelduo

imac Mac OS X (10.4.9) intelduo

imac Mac OS X (10.4.9) intelduo

iWeb Crashes on Publish

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.