Br 12 users beware!

[BruceVI]

Tools>Photoshop has been deprecated right before your eyes.

Go to your CC app and look for an alternative version of Photoshop (23.5.5)

If you have Photoshop 2022 installed on your machines DO NOT uninstall it.  It is the only version of Ps that Bridge can access via Tools>Photoshop and has been made unavailable by Adobe

Feel free to make as much noise as possible about this.

P.S. I have a workaround.  More later

[BruceVI]

[gary_sc]

It's an interesting assumption by this community beginner to assume that this is an evil plot, but it isn't. It's the same progression that's been in place for many years: Two years of past applications are available after updating. This is the result of a legal issue (I do not know the details) that occurred a number of years ago.

If you are using Bridge 2022, you do need PS 2022, as that is a paired set. Bridge and Photoshop are (in effect) a tandem set — you need paired years. 

[BruceVI]

Your point escapes me.

[Lumigraphics]

There are multiple workarounds for this. I use Bridge 12 in production with the latest Photoshop and it all works fine.

[BruceVI]

Please confirm.  When you select an asset in Br 12 and then invoke Tools>Photoshop>Batch  that Br 12 launches the most recent release version of Ps?

[Lumigraphics]

There is a workaround which involves editing some Adobe files. I don't know that Adobe wants it posted on here but yes, it is possible. I also have a script that I wrote, which does the same thing. I use this every day in production as a working professional product photographer.

https://www.dropbox.com/sh/mg817g9a9ymbasi/AADTmXUVxmFfM58bcyYE7yiwa?dl=0

Download the Utility Script Pack and drop the entire folder into Bridge Scripts folder. This adds (among numerous other things) a Batch command to the contextual menu, that will open items in the latest version of Bridge. No hackery of Adobe files required.

Its F/OSS, Apache-licensed, so feel free to adapt it to your needs.

[BruceVI]

While I appreciate the suggestion and your scripts are interesting, it is an incomplete solution.  In the attached image you’ll see the options available in the Tools>Photoshop submenu. We use more than half of these functions on a daily basis, so while helpful in that one example of batch actions, your scripts do not fully solve the problem that I warned about at the top of this thread.

The ONLY fully functional workaround that I’ve found is to find and install a release version of Ps 2022.  I badgered Adobe until they provided me with a zipped installer version of Ps 2022 v.23.3.2  It’s not the latest version. (23.5.5) but at least it restores full functionality of Bridge 12 to Ps. They downloaded it to my machine but did not provide a link to where it could be acquired and it still does not appear in the CC app.  Why, I do not know.

Of course, this does not substitute for all the new features included in the last two years of Ps versions, but the tradeoff to acquire those would be to suffer the staggeringly mangled and poorly performing Br 14.  Br 12 does open individual files in the newest version Ps, it is the automation in the Tools>Photoshop destination that have been disabled and that is a pretty big deal that violates two of the most fundamental rules of asset management.

• Do things once, efficiently.
• Do things automatically whenever possible.

I posted this warning for all Br 12 users who may be in the market for new hardware, so that they would be prepared for Adobe’s unconscionable omission.

[Lumigraphics]

I'm well aware of how it all works. If you MUST have the menu, you can hack Adobe's files (not helping you with that) or use Bridge 14. Or just open the files you want to work with. Whining isn't going to change how the apps interoperate and no, Adobe isn't likely to go back and change that.

[BruceVI]

Lumi, 

You said:

“Whining isn't going to change how the apps interoperate….”

I hardly consider it whining when you make a statement like this:

“There are multiple workarounds for this. I use Bridge 12 in production with the latest Photoshop and it all works fine.”

This is especially true when I excitedly droped everything to set up a proper testing environment to test your scripting plug-ins only to find out that your statement isn’t true and subsequently call your attention to it.

Perhaps you should employ a bit of patience trying to understand the words that others are using and how those words describe their  experiences rather than projecting your own.

[Lumigraphics]

Both things I said are true. You can write your own scripts as well. And that's just one solution.