Just as Firefox users were
upgrading to version 3 last week, many people started to miss their
iWeb-created galleries as they just disappeared. Well, one iWeb user has been doing extra work to fix Apple's? (erm... Mozilla's?) problem. Joshua Ochs has
posted an in-depth article on his site describing exactly what is going on -- he also provides a fix in the form of a
script to patch iWeb.
Joshua says that the problem is neither with Apple nor Mozilla, but with a JavaScript library called "Prototype" which is used by iWeb. Right now there are two ways to fix the problem (neither of which are supported by Apple): you can use the information on
Apple's Discussion Board, or you can download
Joshua's script -- both seem to work and are free.
[via
ArsTechnica]
Reader Comments (Page 1 of 1)
6-23-2008 @ 1:36PM
Joshua Ochs said...
Note that I didn't create the actual Javascript patches to Prototype that fix this, so any issues with that I can't help with. I just took the fix and made it point-and-click until Apple releases an iWeb 2.0.4 (as they surely will).
Hope this helps people!
Reply
6-23-2008 @ 1:50PM
CaptSaltyJack said...
iDisk is also broken. Not quite Firefox's fault, but Apple's. Rather than this proper syntax:
They do this:
which is incorrect. iDisk comes up as a blank web page in Firefox 3. Serious issue, as far as I'm concerned.
Reply
6-23-2008 @ 1:52PM
CaptSaltyJack said...
Woops, HTML was stripped. (replace brackets with angle brackets)
Proper syntax is [script type="text/javascript" src="file.js"][/script]
Apple does this: [script type="text/javascript" src="file.js" /]
which is incorrect.
6-23-2008 @ 1:57PM
Tony said...
Interesting - IE7 will barf on script tags like that as well (unless you're using XHTML doctypes of course, in which case it's entirely legal). Looks like apple only tested on Safari.
6-23-2008 @ 3:00PM
Jonathan Wise said...
curious...
why is [script .../] not valid, while [script][/script] is?
syntactically, they both mean the same thing, and since the script tag contains no element children (only attributes) a self-closing tag should be equally (or more) valid...
6-23-2008 @ 3:10PM
CaptSaltyJack said...
Not quite sure, Jonathan. Maybe an oversight in the XHTML spec? You could argue that tags like IMG, BR, HR can use the [TAG /] format because they never have child elements inside them. Since SCRIPT can have content inside it, it must always be closed with [/SCRIPT] even if that content is empty.
[SCRIPT /] is invalid for the same reason [TEXTAREA /] would be invalid.
6-23-2008 @ 9:44PM
James said...
A quick look at the specifications shows that it's an oversight of the developers and testers. The script element is defined as a non-empty element in the DTD, and so it requires an end tag. IE7 enforces this correctly. It looks like Firefox and Safari didn't/don't.
XHTML 1.0
4.3. For non-empty elements, end tags are required
http://www.w3.org/TR/xhtml1/#h-4.3
HTML 4
18.2.1 The SCRIPT element
http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.1
6-23-2008 @ 1:53PM
Tony said...
Reading the apple thread makes it clear that this fix does not in fact work for most people.
Reply
6-23-2008 @ 6:40PM
mark freeman said...
It does actually, its just some people don't realise you still have to make a slight change to the main gallery, like add a full stop, so the main gallery turns red. Publish it and its all back!
6-23-2008 @ 4:45PM
Arjun Saha said...
Yupp it doesn't find the HeaderControls.js file in the HeaderControls.iwdgt folder!
Reply
6-23-2008 @ 5:59PM
Jim said...
Unable to download and install patch; "error finding replacement files."
Reply
6-23-2008 @ 7:20PM
mettmann said...
same issue here - "error finding replacement files."
6-23-2008 @ 11:44PM
Joshua Ochs said...
My apologies. I pushed a new version that locates iWeb in its default location (trying to make it even simpler).... and instead I broke it. Missed a slash in a bad spot. A fixed version is due on MacUpdate as soon as they approve the submission.
6-24-2008 @ 6:03AM
Kevin Sorensen said...
I'm not sure what the hub-bub is all about. Either that, or someone snuck into my house and added this script without me knowing about it. I upgraded to Firefox 3 last week as soon as it came out. When I read this post today, I thought, well, let's check this out. I went to my galleries and wouldn't you know it: there they are, just as nice as they are in Safari 3. Sometimes, my Macs are just too amazing - they healed themselves before they even knew they were sick!
Reply
6-25-2008 @ 12:33AM
nilusworld said...
wow ... just noticed it is albums and pictures galleries not working. Any fix out there?
Reply
7-11-2008 @ 12:30PM
mac_fanatic said...
Will iWeb pages still work in Firefox 2 after the patch?
Reply