Getting Strange Errors?

June 6, 2008

A couple of people have written to me recently asking about some strange errors they’re seeing at the bottom of their published iWeb pages. So far theses have all be .Mac subscribers and the error appears at the bottom of the page in a full-width bright yellow boxed area.

I do not know what this is about but it’s not related to your themes. See the screenshot which shows the error on the Apple Darkroom theme. This appears to be related to .Mac users only.

I had one individual test something for his situation – the errors for him were appearing on photo pages so I had him create a new page, drop two simple jpgs on it and publish. It worked without error. So my suspicion here is that some kind of supporting code on the .Mac side changed which either corrupted objects on your iWeb pages, or for some reason dropped support for something you dropped on the page. I’m stabbing in the dark, but it makes logical sense since the error is referring to an object.

You need to go to the Apple iWeb forums and let them know you’re seeing these errors.

iWeb pages with object errors for .Mac users.


About This Article

This entry was posted by Suzanne on Friday, June 6th, 2008 at 9:12 AM and was filed in the FYI category using the tags: , , . You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

Tuscan Characters Image Pack Released
Tabouli Update News


3 Responses to “Getting Strange Errors?”

  1. Hac Le wrote:

    It’s debugging log generated by Apple Javascript widgets, and I think it’s browser dependent also.
    I briefly looked into to this before, and it has to do javascript traversing the DOM and could not find the object (part of the widget), so it threw up the log.

  2. Suzanne wrote:

    What do you think is causing this? It seems to be related to photos – perhaps an unhandled file type.

  3. Hac Le wrote:

    Photos page widgets setup detail view by generate canvas elements, the problem must be some screwy logics or mis-init canvas elements by apple sw engineers.
    Browsers are not equal, we all know that. I saw one case that Safari did fine, but FF couldn’t find the canvas and throw an endless loop. oh well… :)