Quirky Podcasting Problem When Ported to iWeb

It's not often that I stump the folks at the Apple store, but I certainly did that on Tuesday. Andy and I are working on a series of podcasts for Girl Scouts, and when I made a little iWeb site so that the rest of our eLearning committee could easily download the drafts, the podcast I posted didn't work.

I spent many hours trying different configurations and many more hours searching the support section on Apple's website. I then went into the Apple store at Park Meadows and worked with about six different people there. In fact, one of them said he was having the exact same problem.

My podcast uses the enhanced features — it has chapter markers and artwork (still pictures) for each chapter. It's less than 10 minutes overall. When I export it from GarageBand to iWeb using the Share to iWeb command, the darn thing won't play.

Anybody have similar problems? Got ideas?

Thanks!
Chris

Are you seeing a generic

Are you seeing a generic "Q" and "can't find plug-in" type prompt when trying to view the content in Safari?

if so then it's a known bug that occurred after upgrading fromQTime 7.1.5 to 7.1.6

read this thread

http://discussions.apple.com/thread.jspa?threadID=959309&tstart=30

problem appears to be related to QT7.1.6 which might explain some problems I'm having

My Tower is running 7.1 5 and Safari Works but Firefox is broken
My Laptop is running 7.1.6 and Safari is broken but FireFox works

I tested the following browsers on the Tower: Opera, Netescape, Mozilla. Opera worked, others broke which is consistent with Firefox being broken (mozilla essentially)

That appears consistent with the problem noted in the above thread

I'd be curious to know what versions you're running of QT

I was able to bypass the problem by replacing the QT plugin on the Laptop (QT7.1.6) which is the source of the problem as suspected. Backup the QT Plug in from 7.1.6 (HD/Library/Internet Plugins) and replace it with the 7.1.5 plugin and it might correct the problem.

There was a security update to QTime 7.1.6 that came out after all those problems but I havent' checked to see if that fixed the problem. I.e. perhaps installing QT 7.1.6 and the QT Security update will fix the problem without needing to swap the browser Plug-in back to QT 7.1.5.