Copy link to clipboard
Copied
(Reposted using a more accurate heading after more testing)
I've just updated the MacOS to Ventura on my 2019 iMac 27" and updated all the CC apps (illustrator, indesign, photoshop and bridge) up to 2023 versions, but am now experiencing problems.
Bridge will not open any CC file from a network volume. Photoshop and Illustrator give no indication that they are trying to open files. Indesign says "missing required parameter 'from' for method 'open'"
Network files dragged from Bridge to the desktop are also not allowed with the cursor changing to a no-entry symbol. Local files can be dragged and dropped with no issues. Local files can be dragged and dropped into Bridge but not vice versa.
All CC files can be opened from the network volume from within their respective apps, and can be copied to the desktop via Finder.
I assume this is a permissions issue but have followed whatever advice I can find including giving full disk access to Bridge in System Settings.
I have tested in Bridge 21 and have discovered that this displays the same issues.
Thoughts?
Problem solved. I'm still not entirely sure why, but the network volume appeared twice - one worked well with Bridge and one didn't. Either way, it turns out the issue wasn't Bridge after all.
Copy link to clipboard
Copied
The plot thickens...
More testing has revealed that Bridge will allow me to drag and drop from the network volume on to the desktop UNTIL I open one of the network Indesign files via Bridge. The indd opens, but when I close and reopen it (or any other) I get the missing parameter message and am unable to open any CC files via Bridge unless I restart the Mac.
At this point I am also unable to drag and drop ANY network files from Bridge onto my Mac.
Copy link to clipboard
Copied
I've now discovered that it's not just CC apps having issues via Bridge. Both Sketchup and Powerpoint network files appear to work fine until Indesign is opened, at which point they suffer the same issues as above.
I'm going to roll back to Monterey to see if that solves the problem.
Copy link to clipboard
Copied
Hi, @nawest,
I hate to tell you this, but Bridge was never designed to work on servers. It was designed to work only on local hard drives. That is the computer's hard drive and directly connected external drives. Any success you may have is more accidental than success. I can't speak of InDesign as I've never had any server use of ID. In the case of ID, were you accessing the ID files from Bridge or directly within ID?
If you really need a server within your business, please look for software that is built to work with servers. Bridge is not it, and extremely unlikely to ever be.
Copy link to clipboard
Copied
Thanks for your input Gary, and whilst I accept what you say is true, that doesn't preclude the fact that we've been using it for exactly that for about as long as Bridge has existed. And this is the first time we've come across any major issues. Maybe it is accidental but I know we're also not alone in using it succesfully in this way.
In answer to your question though, ordinarily we open the files directly from Bridge for all apps. It's pretty rare that we open them from within the apps.
I may have stumbled across the cause of the issue anyway (which apears to be server related), but I'm still testing to make sure. I'll post an update when I'm sure.
Thanks again.
Copy link to clipboard
Copied
Hi @nawest,
As I stated, Bridge was never designed to work on servers. That does not mean it can't, but even when it can, ANY change (updates to servers, software, OSs, pretty much anything can cause it to fail. And, because it was not designed to work with servers, there's not much you can expect or hope to get from Adobe to help you.
And, for the record, I am not an employee of Adobe; I just volunteer to help folks with the limited knowledge that I have from using Bridge since version 1.
Copy link to clipboard
Copied
And I, for one, appreciate that help 🙂
Copy link to clipboard
Copied
Problem solved. I'm still not entirely sure why, but the network volume appeared twice - one worked well with Bridge and one didn't. Either way, it turns out the issue wasn't Bridge after all.