Legal
The views expressed in this blog are my own and do not necessarily reflect the views of Adobe Systems Incorporated.
Search
July 01, 2008
Mac 10.5.4 update improves CS3 support
Good news: Apple has just released the 10.5.4 update to OS X Leopard, fixing some incompatibilities with Creative Suite applications:
- A problem introduced in the 10.5.3 update that could cause file corruption with files saved from Photoshop and other applications, has been fixed.
- Navigation Services issues that could cause InDesign to crash have been addressed. InDesign evangelist Tim Cole has provided more details, and the InDesign team has released their own ID 5.0.3 update today (Mac|Win; InCopy Mac|Win).
Comments
Any idea if this fixes a problem I've been having when I open new documents in Indesign and the entire Indesign interface disappears. The application is still running but I can't see it or any documents that are open no matter what I do. I'm forced to force quit Indesign when it happens.
John,
Great to see these updates. I was wondering when the video apps would be updated with Leopard? All I can find on the website says updates should be available last December. Thanks!
Drew
[Michael Coleman (After Effects PM) replies, "With the current updates, the video products are all certified for Leopard." --J.]
Roger: If you are opening new documents from Bridge, it is likely that you are running into a variation of the Cmd-H bug. Unfortunately, this was not addressed with 10.5.4. However, some folks have reported a workaround: Launch InDesign. Quit. Relaunch InDesign again. Many are are reporting that this will prevent the Cmd-H bug until you reboot your machine.
Hi John,
Interesting you mention this, as an hour ago, PS3 and bridge won't even open. Yesterday, I downloaded and installed the 10.5.4 update.
Am I the only one?
After installing 10.5.4, photoshop and bridge won't even start.
Same problem here.
Of the entire CS2 suite I can only open Acrobat Pro, post 10.5.4 update!
Solved the problem!
See http://www.experts-exchange.com/Web_Development/Software/Adobe_Creative_Suite/Q_23536455.html#a21932618
we've started discussing where CS3 is a step backwards rather than forwards...
http://paris.blog.lemonde.fr/2008/07/02/adobe-suite-cs33-et-acrobat-9-adobe-booste-encore-nos-metiers/#comment-4872
Roger:
I used to (very often) run into the problem where InDesign CS3 would disappear and couldn't see my open docs and couldn't save them.. had to force quit (then redo my work!). My fix was to assign the InDesign app to always open in the left bottom "space" and have ONLY InDesign active in that "space".. I did that 4 months ago and it hasn't happened since. Only drawback is that I need to manually click on the "space" to see the menus & toolbar..(simple tabbing to InDesign doesn't let them show). Not an ideal fix, but it works for me.
After reading of other CS apps not working after 10.5.4, I'm now worried about updating - so I guess I'll put it off even longer. :(
When I open InDesign CS3 I get an error message that the "Workgroup Client.INDesign Plugin plug-in" conflicts with "Workgroup Client UI.InDesignPlugIn" and it won't open. I've temporarily removed the plug-in and tried again and it still doesn't work. Anyone know a fix without having to reinstall (I've also run disk utility repair permissions and rebuilt the Pram).Thanks, Olivia
I'm having the same problem as Olivia. All of a sudden, after making no changes to any of my InDesignCS3 or other Creative Suite CS3 programs, I'm gettin an error message saying THE WORKDGROUP CLIENT.RPLN plug-in conflicts with WORKGROUP CLIENT ULRPLN. Try removing one of them, etc. I did remove the one that was in my InDesign plugin Workgroups folder but still have the problem. Suggestions?
Thanks - Joe
You might have better luck getting answers in the Adobe InDesign user to user forum.
I had the same problem trying to launch InDesign as Olivia.
The Workgroup Client plugin conflict message would show up.
Taking out the plugin did no good. I'm running version 5.0.3 and I solved the problem by downloading the 5.0.3 update and running it again. That fixed the problem.