Issue

Adobe Contribute hangs when you start it on Mac OS 10.5.x.

Details

You are either using Safari version 3.2.1 or the Safari 4 Public Beta

Reason

This is due to a change in the WebKit behavior while working with Safari version 3.2.1 or the Safari 4 Public Beta

Solution

For Safari version 3.2.1:

Update your operating system to Mac OS X 10.5.7. This contains a version of WebKit which resolves the issue.

If you have the Safari 4 Beta installed, perform one of the following steps:

Note: To fix the above issue, the rendering of any active content like swf, flv, mpg, mpeg, mov etc. is blocked in the Contribute browse mode on 10.5.x with Safari 3.2.1. However the active content will render in the Contribute Edit mode.

For Contribute CS4:

Install the latest Contribute CS4 update by going to Help > Update in Contribute CS4 or Bridge CS4. This update (also available here) includes performance improvement updates for Macintosh as well.

This update also includes the Firefox 3 plug-in which allows you to use Contribute In-Browser Editor plugin in Firefox 3.

For Contribute CS4 + Safari 4 Beta installed on the machine:

  1. Install the latest Contribute CS4 update by going to Help > Update in Contribute CS4 or Bridge CS4. This update (also available here) includes performance improvement updates for Macintosh as well. [This update also includes the Firefox 3 plug-in which allows you to use Contribute In-Browser Editor plugin in Firefox 3.]
  2. Create a file "ContributeMacOptions.override" in the location Application > Adobe contribute CS4 > Configuration > plug-ins.

For Contribute CS3 and Contribute 4.0:

Go to Applications > Utilities > Terminal and run the following command:

defaults write com.adobe.Contribute WebKitPluginsEnabled -bool NO

For Contribute 3.11:

Go to Applications > Utilities > Terminal and run the following command:

defaults write com.macromedia.Contribute WebKitPluginsEnabled -bool NO

Additional Information

Although Apple have resolved the issue in the current release of Mac OS X, the problem still remains in the version of WebKit supplied with the current Safari 4 Public Beta and therefore installing this will re-introduce the problem.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy