My other issues with iWeb

I am a perfect candidate for iWeb because I have no webpublishing experiance. However, I spent a couple of hours developing a site for school and the font was totally jacked. Characters popped up every where in the finished product that ruined the whole thing. This is just the type of crap I was hoping to avoid. Booo apple, boo!!

Just got iweb 1.0.1 and uploading a picture page using airport on my powerbook. The airport connection crashes as does iweb. Great!

I just built my first iWeb site for a simple family website - mainly to share pics with family and friends. I already have a hosting account for my business so I didn't want to have to purchase a seperate .Mac account.

The problem is that when I uploaded the site to my host, it screwed something up. Check out the site www.swirefamily.com - there are ? question marks and a number of other formatting problems. My host is IXWebhosting and I used Fetch to upload the files to the host.

Any ideas what the problem is?

Thanks!

Zack

I think it is odd that iWeb is generating a case sensitive URL. Is
this an aesthetic concern? iweb vs iWeb? A first release problem? A
capital "W" seems like a glitch waiting to happen. When websites are
read out during podcasts it seems overly complicated to have to read
out a capital W!
Eg:

I didn't read all the comments so this may be a repeat but, I can't even remember the last time I typed in a URL. That isn't a real issue.
There are probably real issues with iWeb - but mostly for people who are already beyond iWeb and shouldn't use a tool like this anyway. If you know how to ride a bike, why ride one with training wheels?

I think iWeb is great. I like how easy it is to use, and how simple it is to get a great looking site up in no time.

I am using a meta tag to redirect my "homepage.mac.com" site to the new iWeb site. Works like a charm.

Some complaints/enhancement-requests:

1) On a photo page, you can't make the photos links. I wanted to use one photo page as a "my albums" page, where each photo was from another album. You can't link them.

2) If you update with iPhoto an image that's already on an iWeb photo page, you have to manually delete and replace the image from iPhoto to get the updated photo on the web page. And in doing that, you lose the caption. Not a huge deal, but if you batch-update the hue and saturation for a photo album of 30 pictures, it can be a pain.

3) There seems to be an inconsistency between the blog archive page showing pictures or not. Mine used to show pictures. Now it doesn't. Why?

4) iWeb makes it easy to put all sorts of media online, including videos and such. However, it doesn't give you any indication of how big everything is. Quickly dropped in a movie and then went to update the site... The upload process started to hang, or so I thought. It was just uploading my 8 Mb movie file. The progress bar that comes up doesn't reflect the amount of data (Mbs) but the amoutn of pages, which can be very misleading. Some sort of warning popping up would be nice, telling you how big certain files are and how long the'll take to upload (for you) and download (for your visitors).

Otherwise, it rocks. See what it's doing for me:

http://homepage.mac.com/meichler

--Michael

I can't add in some custom html - I know that's half the point but I need to add in my creative commons copyright liscence which is a little piece of html.

Apple should just allow to provide a short name to a iWeb site. They can keep their long names and the short name would just be a redirect done by the server. Minimal changes necessary.

The thing I dislike most is that iWeb make a huge file in Library/application support/iweb after only a couple of pages this file was 1 GB, and the exported homepage was 10 MB.
I skipped iWeb and did the same in Dreamweaver as I dont use .mac. Double the contents gave me a site that was only 6MB and no 1GB file at all!!!
Although it required more work.
I want a better iWeb!!!

I remember that .mac was case sensitive also before the iLife 06 launch, I'm pretty shure