IWeb 1.1 Still is TERRIBLE

Wonderful. I download iWeb 1.1 with all of the shiny new features, such as background publishing, faster pages, more reliable uploading, comments in blogs and podcasts.
All well and good. Except for the reliable publishing part. Apple, quite frankly, you s*ck. The same problem of iWeb having problems correctly calculating the disk quota for publishing to iWeb is STILL there. I haven't been able to publish my website all morning.
Unreliable, unusable, and can't recomend this. Avoid iWeb people it is terrible.

Everytime I complain about Apple's glaring lack of quality assurance and testing on a new product or release, I get all kinds of flack. Things like "It works for me, if you can't say anything constructive don't say it, what do you expect for something so cheap."
I expect something that JUST WORKS. Isn't this supposed to be the Macintosh way, and the very thing that Apple touts as being a benefit of their system over other OS or platform choices? Isn't this why we pay a premium for their all-in-one solutions, hardware and OS, rather than buying a tinker-toy Dell and cobbling together some sort of workflow?
When the Apple stuff works, I will be the first to talk up how great it is. Believe me, there is nothing better, integration-wise than the iLife package. Being able to uniformly access and manipulate media, be it music, photos, video, written word, and easily share it in the form of web pages, DVD's, photo books, greeting cards, what have you, is wonderful. It is a joy to use, and really frees my creativity.
I remember years ago when software came out, a developer would not DREAM of releasing the thing with any show-stopping bugs. The market was smaller, it was simpler times, and the consumers would not have tolerated it. NOW everyone gives companies such as Microsoft, and yes, even our beloved Apple a free pass when their xx.0 versions are simply riddled with problems that render the software either useless, or a nightmare to use. The ONLY reason software companies get away with this crap is because the consumers enable this behavior, shrugging off poor quality software with a "nice effort guys, hopefully you will fix its problems in the xx.1 release." The fact of the matter is that we early adoptors are being taken advantage of by software developers to essentially bankroll their testing efforts to shake out the final bugs, bugs which SHOULD have been eliminated prior to the software's release, by rigorous quality assurance and testing practices. Software SHOULD NOT be judged on good intentions. It should be judged on how well it does its job.
Apple has been well-aware of the publishing problems with iWeb since day one. The thing has been flakey for some users when attempting to do the "insanely great" functionality so proudly touted at MacWorld last year. I was unable to publish anything for a full ten days after purchasing the product, and I was livid.
Periodically I run into a publishing issue with the thing where it will not upload to my iDisk. I will get strange disk quota errors, or even more cryptic problems.
I work as a software developer. You can be SURE that one of the things I would have attempted to address in the point release, and one of the things that I would have placed VERY HIGH on my testing plan, would be the behavior of the software publishing functionality. If this is not 99% reliable, I would darn sight hold the product back until I was sure it worked. Apple has been told about this issue over and over again. I personally have talked to technical support AND customer relations about this issue. Is it a server thing? If that is the case, as a developer, I would be darned sure to test the software under a load, and simulate lack of server responsiveness and produce MEANINGFUL error messages to the end-user to indicate server problems.
And yes, it comes down to how this thing impacts my work. I do freelance video work, and use .mac to publish previews of my edited videos for client approval. In general, this works well, albeit terribly slow due to the quirks of .mac. Twice now in the past month I have had to call my client and apologize that I could not get my edits posted for their perusal BECAUSE iWeb crapped out on me. I ended up having to grit my teeth, and either FedEx a DVD, or use the old homepage tools to get the work posted. This is not the so-called "Macintosh Way."
I happily downloaded the new update to iWeb, with all of the great new features added to blogging, and supposedly speed-optimized graphic handling. And proceed to render my publishing efforts useless, with the same error that I had reported multiple times, that had been discussed in these forums multiple times, and still, glaringly obvious, present in the software.
This is terribly frustrating.

Similar Messages

IWeb 2.02 still crashing when updating

I tried a while ago to update to iWeb 2 and it would crash whilst updating, i had a hellish time trying to restore the old iWeb and the domain file, luckily this time i backed them up so reverting was easy, but the problem still exists that the new iWeb 2.02 gets to about 3/4 complete when updating then crashes.

Hi I just know that is not the problem, for starters this problem happened before with the original iweb 2 and i did all that stuff that time, plus i have had no problems installing, all other programmes work fine, indeed iweb 2 works fine if i i remove the domain file and act as if i am starting from scratch.
the problem is in the process of updating the domain file, maybe so incompatibility exists, even though i did not mess too much with the template pages i used.

IWeb - does it still work?

Every time I open iWeb it comes up with the error message (which is sent to apple) and asks if I want to reopen. I re open & get the same message.
Does it still work? I haven't used it for ages...
If not then how do I find the pics & videos that are embedded in iWeb?

To open your domain file in Lion, Mountain Lion or Mavericks or to switch between multiple domain files Cyclosaurus has provided us with the following script that you can make into an Applescript application with Script Editor. Open Script Editor, copy and paste the script below into Script Editor's window and save as an application.
do shell script"/usr/bin/defaults write com.apple.iWeb iWebDefaultsDocumentPath -boolean no"
delay 1
tell application "iWeb" to activate
You can download an already compiled version with this link: iWeb Switch Domain.
Just launch the application, find and select the domain file in your Home/Library/Application Support/iWeb folder that you want to open and it will open with iWeb. It modifies the iWeb preference file each time it's launched so one can switch between domain files.
WARNING: iWeb Switch Domain will overwrite an existing Domain.sites2 file if you select to create a new domain in the same folder. So rename your domain files once they've been created to something other than the default name.
For Mavericks, 10.9 , go to your Home folder and use the View ➙ Show View Options menu to bring the this window:
If using the iWeb Switch Domainapp doesn't let you open your domain file try the following:
1 - delete the iWeb preference file, com.apple.iWeb.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete iWeb's cache file, Cache.db, that is located in your
User/Home/Library/Caches/com.apple.iWeb folder (Snow Leopard and Earlier).
3 - launch iWeb and try again.

What happens if I delete a site in iweb? site still on the web? system?

B/c of my various issues i'm having since upgrading iweb, I created two test sites on iweb09. I was able to upload them to the web and to a folder.
I deleted both. Later, I created another test site with the same name (site 2). I noticed this one was acting weird.
I'm wondering what happens to the sites after they are deleted.
1. Are they available on the web?
2. Are they somewhere else on my system that I should make sure to delete?
Thx.

I'm wondering what happens to the sites after they are deleted.
1. Are they available on the web?
2. Are they somewhere else on my system that I should make sure to delete?
Deleting sites inside iweb does not have any effect on what has been published on a server or to a folder on your local drive. It just changes what is in iWeb's domain file.

Two people working on the same IWeb-page and still keep our own work saved.

Hi! I work together with a girlfriend buliding webpages in IWeb. Is it possible for us to exchange work when both of us is edithing the same webpage - and both of us have other pages one our own that we rader not share/update/change/edit/overwrite/delete,...?

Yes. Are you referring to pages in the same site or separate sites?
For separate sites the shared site would need to be it in its own domain.site2 file. Then follow the directions in this MacWorld online article: Managing an iWeb site from multiple Macs
The important caveat to this is that both of you cannot work on the site at the same time and plenty of time must pass between one of you finishing their work and the other starting up. It's just the nature of the beast. Otherwise you would have to pass the domain.sites2 file/package back and forth between your two Macs.
If your two Macs are connected together on the same LAN you could place the domain file on an external HD attached to one of the Macs so both would have access to the same file. Again, both of you could not work on the site at the same time.
The other sites would then be in a separate domain file.
If you're referring to pages in the same site it can be done by having the jointly managed pages in one site and your pages in a separate site and her pages in a separate site.
Then in the joint site add blank pages representing your pages and her pages. In each blank page put the following code in an HTML snippet:
<script type="text/javascript">
parent.window.location = "URL TO PAGE ON SITE YOU WANT TO REDIRECT TO"; </script>
Thanks to Cyclosaurus for this code
On each of your sites you would add blank pages representing the joint page and each other pages with the same redirect code.
Now you can edit and change your pages at any time, publish as she can also with her pages. For the joint pages you will have to use one of the methods I described above for separate site.
See this demo page for more about the Redirect method: Redirect.
OT

New iweb 08 update still stripping out photos

having installed the new 08 update I thought it might solve the MANY problems expereinces so far in updating 06 iweb sites
After a quick look it seemed ok but when I opened the domain file the second time most of the photos were missing.
Thought I had solved it by trying again from a previously backed up domain file, and opening each page in turn so 08 could get a good look, then saving.
It worked the first time but I opened it again to find once again most of the photos removed.
Remember this is after installing the update that came out this morning!!!!
Anybody else the same??

This is the "Previous to iWeb'08" forum -- better to post your qstn in the "iWeb'08" forum here:
http://discussions.apple.com/forum.jspa?forumID=1193

I updated to ios 5.0.1 and my battery still have terrible life

Why the ios 5.0.1 can´t fix the battery problem? I have an ipod touch 4th g.

Newsstand is an like iBooks. A place to pur suscription peridocals. Also see:
Apple - iOS 5 - 200+ new features for iPad, iPhone, and iPod touch.
Find Apples; description of iCloud here is fine.
iCloud
If you have any specific questions ask.

Still no Aperture Galleries in iWeb gallery insert menu.

Now that all my photos are created in Aperture it is really frustrating that they are not showing up on the iWeb "insert" menu. All of the iPhoto galleries show up and none of the Aperture galleries. Does anyone know when this may be fixed? They just updated iWeb today and still this problem exists. Apple PLEASE allow the insertion of galleries from Aperture - they're right there on the gallery page.
  -josh

I've run into this myself recently, and you're right, it's very annoying. On the Aperture forum there are always posters claiming "there is absolutely no reason to keep iPhoto anymore if you use Aperture." However, there are a handful of these little quirks that negate that statement (no Front Row support, none of the matte print options iPhoto has, galleries unsupported in iWeb, etc.). I've sent Apple some feedback to let them know this is an oversight.

Mavericks: Mail + Gmail = still terrible!

I have the recent Mail update installed (Version 1.0), but Mail app still works terribly with Gmail. A whole bunch of messages that are supposed to be in Inbox randomly show up only in Archive folder. If I access Gmail in browser they are displayed correctly in Inbox. What's going on? Why can't they make Maill work with Gmail?

I can't say that the discussion you referred to was very helpful for me.
One of the suggestions was to disable Show in IMAP for All Mail in Gmail Settings. Doing that actually emptied all email boxes in Mail on my Mac, after which Mail started re-syncing everything over. When it was finished, the Archive folder for Gmail was still empty leaving me with no way to access archived messages on Gmail server from Mail app.
I have enabled Show in IMAP for All Mail back. Hopefully this will bring back all archived emails in Mail... It looks like Mail is about to re-sync everything all over again. Such a waste of time...
Regardless, I'm thinking of ditching Mail app altogether. Even if there is a way to make Gmail work properly with Mail app in Mavericks, it's very far from straightforward. It's certainly does not work "out of the box".
What happen to "Apple: It just works"? Now it's more like "Apple: Sometimes it works, and sometimes it just doesn't."

IWeb and .Mac images are dark when viewed with PCs--how to fix?

I do my Photo editing in iPhoto on an iMac or an iBook, and the images look fine. Once posted to a .Mac or iWeb page, they still look fine on my Mac monitors, but when viewed on PCs and PC laptops, they are MUCH darker... The sites look terrible. The brightness on the nonMac monitors is turned up already.
Is there something special I should do to get images to appear correctly on nonMac machines?

Thanks for the responses. This has been a problem for a couple of years and this is real advice! I even had this problem with a book published through Apple. Anyway...
I didn't follow Barbara advice (OK, I'm slow, but I couldn't quite figure out where the gamma setting was), but I did use Falcon01's suggestion to use the sRGB IEC61966-2.1 profile.
I then reviewed and re-edited the relevant pictures. In this case, they are pictures of my girlfriend's condo she is trying to rent (mostly slightly off-white walls (aren't they all?) and dark, rich parquet flooring.) First, the pictures were darker, and I could adjust the exposure to much brighter, which helped a great deal. It did, however, introduce lots of color artifacts (pinkish blotchy walls). I drastically reduced the saturation which (good) made the walls look fairly normal, but (bad) made the rich wood flooring look drab and grayish. For this purpose, this will be satifactory--the pictures now at least are bright enough to not look dark and dank, and people can see what the rooms look like.
When I try this on important pictures of people and such, this approach makes me nervous. Most pictures will look awful if I boost expsoure and drain the color out. How do others handle this? Thanks in advance. BTW, here is the revised web site if interested.
http://web.mac.com/curtishaymore/iWeb/B7EC3471-1B51-467B-8C79-01CD335FC856/Libra ry%203.html

How do I get iweb to upload to different family pack accounts?

Hi. sorry if this has been covered before, but I can't find this particular problem anywhere. Also sorry this is going to take a while to explain. We feel we wasted an extra 50 bucks on our family pack for mac.com last year to have accounts we never could find out how to upload from our separate iWeb domain files. We needed 4 different "sub accounts" but we use one mac laptop using one desktop. Calling apple customer service was of no help. We have figured out the way to get iWeb to open different domain2 files was to copy and into each person's file (one for the gardener for their garden stuff, one for the budding chef and his cooking stuff, etc). But no matter what domain file is opened and worked on iWeb always uploads it to our main (original) user name thus erasing the site previously uploaded to it. We can't seem to find out how to change the settings in iWeb so when it uploads particular iWeb projects to Mac.com (or now me.com?) it goes to the sub accounts and not overwriting the main account. Our main account is for the entire household's news/photos etc and we don't link to the others from there. We thought by setting up the family pack we could easily get iweb to send up to the other sub accounts. Not so. We ended up last year just doing all our websites on the same iWeb domain file using "new website" function and adding a complete new website to the bottom of the list on our iWeb pages. All of them would be combined into one which uploaded everything to the main account. Not what we wanted but that was the only way that nothing would get erased by anyone else's updates but also not very private as those near the bottom of the list would have a mac.com address as long as my arm. Sorry so long winded here. But if we can't have two iweb domain files on a desk top upload to two separate mac.com accounts or sub accounts, then why pay the extra for them? Is a family pack only good for families with a computer in every room? Our family pack accounts expires in 10 days so would like to know if we need to waste another 50 bucks. And no, setting up separate desktops for for the sake of individual iWeb projects is not an option as all the files are kept together. We tried that once and got so much duplication in photos and stuff, our hard drive was full in no time.

so you have 45 different users on your one computer? ie: 45 different desktop users or am I still not understanding. To me a "user" you are referring to is what I would go up to the upper right of my toolbar and use the drop down menu and select another name (or in this case another alias of myself) but those additional accounts (users) would all have to be tied into my files on the main account to access them from all users, correct? All my files are on my one main user (myself) and not all of them are in iPhoto or iTunes, for instance any swf files. If I have other iWeb domain files (which I know how to create, duplicate and know about the last one used in iweb etc) then I have to create a separate user name (myself again) in my computer for as many iweb/me.com accounts or sub accounts that I have? But my problem with that is if I copy those domain files and move them into another account/user (which I tried) the link (the stuff at the bottom of the iWeb work window) still says my original Mac.com (me.com) address and will not let me change even when the new "user" has not even logged into Mac.com ever or the second computer is linked to a completely different mac.com account. I would have to start all over from scratch. I am sorry that I am not getting this. I know you are trying hard to explain it to me but it is just a bit too complicated to do a simple task of: I want to create a new iWeb/domain2 file on my own desktop with my own user name and have it go to "here" and not "here" within the me.com environment. I have actually copied and moved over 20 domain and domain2 files between our two macs to work on them, but each time the same connection indicated at the bottom is always the same and they will all upload to the master account at Mac I am referring to thus deleting anything we uploaded before no matter which computer they are located on. Once that domain file is created it is locked into that Mobileme account no matter what. So it has been easier to simply save to folders and purchase hosting from someone else than try to figure out what I am doing wrong with mac and me. (me, not myself)

5 users to contribute content from window based PC's to iWeb site

I would like to create a website in iWeb '09 which will require multiple users to contribute/publish content, but the other site collaborators do not have Macs, just Windows-based PCs.

Welcome to the discussions. Even if your five users all had Macs running the same version of iWeb, it would still be difficult for them to contribute content — because iWeb's site data is stored in a Domain file on a Mac. This Domain file would need to be exchanged around the users for updating — which is not very practical for Mac users and impossible for PC users.
Instead of using iWeb, I suggest using a web-based design app accessible from PCs and Macs. Some of these apps have specific features for sharing whilst others may be sharable by giving out the single username/password to the other users. But this could be problematic if there's only a single email address associated with the username.
This first one is specifically designed for sharing:
Backpack
Google Sites claims to make creating and sharing a group website easy:
Google Sites
This one focusses upon "social networking":
Ning
...With Ning you can add tabs and sub-tabs to specific pages and external links via the Tab Manager feature. Mouse-over the menu items at this Ning site:
http://www.openwineconsortium.org
And their tab manager:
http://blog.ning.com/2008/08/a-new-tab-manager-early-next-week.html
Other web-based design apps are:
SnapPages
Yola
Viviti
Jimdo
Weebly
Sampa
Wix
If a sharable blog format is acceptable, you could hyperlink from your iWeb site is to a free Posterous blog. Posterous has "dead simple group blogging by email" where each of your three possible blogs can now have multiple contributers — see more here.
General info about Posterous blogs is in their FAQ. ...Group members can contribute text, photos, sound and video files, etc. to a Posterous blog simply by email. Plus there is the usual commenting capability plus comment alerts for the account holder.

From old website and iWeb to new HDD and iLife '08?

I wasn't sure which category to post this in but this may seem more relevant to my issue.
I put a new HDD in my mac some time ago and also upgraded to Leopard OS. I created a site using iWeb 6 which still have saved on my original HDD which i now have for external use. I just bought iLife '08 but yet to install it as I would like to update the website I was working on rather than start from scratch. The site mainly consists of photos and videos where I used iPhoto and Quicktime Pro a lot. I have also copied my iPhoto library onto my new HDD.
What is the best way for me to copy and continue updating the site I was working whilst upgrading to iLife '08 so I can enjoy the benefits it has and use the features to help me progress with the site?
Any help much appreciated

Put the domain file in :
~/Library/Application Support/iWeb/
Open iWeb 06.
If you start using iWeb 08, it will find your domain file and updates it to iWeb 08.

IWeb quits 'unexpectedly'...how do I get it to work/

I have a website on iWeb, and I have all of a sudden had a problem opening it. I click on the icon on my dock, and it starts to bounce, but after 15-20 seconds it gives me a message saying 'the application iWeb quit unexpectedly'. I have tried relaunching it, and even did a utility check and fix to make sure there wasn't something there making it do it.
Can't get it to work...help???
Mahalo...George

George:
If you install iLife 09, that will likely fix your problem. ( unless the problem isn't really iWeb)
Do copy your domain file and move it out of the <user/library/application support/iWeb/> before you run the iWeb 09 application. Yes, this is a straight forward drag and drop operation.
<user/library.......> is a description of the location of the domain file. Here's what it means:
<user> (a little house icon in the left-hand side bar of any folder, if the side bar isn't visible, click on the oval button in the upper right hand corner of a folder to hide/ display the side bar) is usually what you've named the folder of the computer that has your personal settings for applications etc.
Double click on your user icon ( the little house) and you should see a list of folders, find the folder called <library>, double click on it, find the folder called <application support>, double click on it to reveal it's contents, find the folder called < iWeb> and you should find your domain file in that folder. Copy it (the drag and drop operation to an external drive should copy it rather than just move it. You want to copy (as opposed to <move> it so it remains in the original folder and is duplicated to a safe place on an external hard drive.
When iWeb 09 opens the domain file it will modify it and iWeb 08 will no longer be able to edit the domain file. (but with a copy of the domain file safely out of the <user/library/application support/iWeb/> iWeb 08 will still be able to edit the domain file you copied and moved.
This is a safety precaution in case something goes wrong with the update process you will still be able to edit your existing work with iWeb 08. ( you could always reinstall 08 )
To try to clarify and answer part of your question:
iWeb only edits the domain file (located on your computer), this one file is where all your editing work is stored.
When you publish to a server (or folder for that matter) the iWeb application no longer interacts with the published site. iWeb only edits your domain file. only when you hit the publish button do the changes you've made to your domain file overwrite the published site.
The domain file and the published site are two completely different things.
Hope this helps, David

How to migrate sites and blogs made with iWeb 1.1.2 into MobileMe?

How to republish or migrate sites and blogs made with iWeb 1.1.2 into MobileMe?
I can not find instructions for that, and when trying to publish into .Mac, I consistently get an error message. The sites would look better as they are, but ...

tortuga wrote:
How to republish or migrate sites and blogs made with iWeb 1.1.2 into MobileMe?
If you're referring to last year's transition from .Mac to MobileMe, your iWeb websites are still available at the same URLs and have also been given a new URL at (www.me.com). For example, (web.mac.com/emily_parker/) will work as will (web.me.com/emily_parker)
tortuga wrote:
I can not find instructions for that...
I don't think there's anything special you need to do, but anyway, this Apple doc may be of interest:
_dotMac to MobileMe transition FAQ_
tortuga wrote:
...and when trying to publish into .Mac, I consistently get an error message.
What's the exact text of the error msg? This Apple doc may help:
MobileMe: Troubleshooting iWeb publishing issues
Also, MobileMe live chat support is now 24/7 — see this announcement.
By the way, your Public Profile indicates you're running Mac OS X (10.5.4) — if that's true, you should upgrade to 10.5.8 via  menu > Software Update...

IWeb 1.1 Still is TERRIBLE

Similar Messages

Maybe you are looking for