Copy link to clipboard
Copied
My CC subscription apps are up to date. I regularly use Br & Ps & to run scripts and actions from Bridge via the Tools> Photoshop menu. Today I noticed that Photoshop no longer appears in the Tools dropdown. I checked the Bridge>Settings to be sure all the scripts are checked. I also used Time Machine to revert both Br & Ps a few days. Nothing seems to bring Ps back to the menu. What am I missing ?
Copy link to clipboard
Copied
I have the same problem. I've always processed jpegs of my tiffs using the Photoshop/Image Processor drop down in bridge. Now it is gone.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Same problem here. I've tried all kinds of thing. Reinstalled Bridge several times. Removed the beta-versions of Bridge and Photoshop. Now Photoshop no longer shows up in the Bridge Startup Scripts.
@frankg_photos Any luck with reinstalling PS?
Copy link to clipboard
Copied
Just found out what caused the problem in my case. The installation of the beta version of Photoshop messed up things.
To resolve the issue, I deinstalled Photoshop beta and the regular Photoshop. Then I reinstalled the regular Photoshop and after that opened Bridge. I was asked whether to install a couple of Startup Scripts and I did. The Tools were back as before.
After that I reinstalled Photoshop beta. After opening Bridge I was asked whether to install Photoshop 2024 Startup Scripts. DO NOT INSTALL THESE SCRIPTS! After that the Tools were still there. However, all previous Photoshop file associations in Bridge were changed into Photoshop 2024 25.0. I’m afraid you will have to change these back manually.
In my opinion this is a serious flaw in the design of the beta installation which Adobe should fix. First, there is no such thing as Photoshop 2024. The beta version is called Photoshop 2023 (beta) 25.0. Second, the file association in the explorer only displays Photoshop 2023 as an option in the list. However, this is not the regular Photoshop 2023, but Photoshop 2023 (beta) instead. I have not found a decent way to repair or circumvent this serious flaw.
Copy link to clipboard
Copied
Just a word here; that's why it's called "Beta." Sadly, ALL software is technically beta because no matter how many beta testers there are, you cannot test in all circumstances in all ways. So, things show up. However, this software is called "beta" because it hasn't been tested by a group of folks to find the obvious bugs. You found one of the bugs. You are reporting it. Future users of this software, thank you. And for reporting it here, others thank you for your warning. Hopefully, this will be resolved in the next release of beta software.
Copy link to clipboard
Copied
Hi Gary_SC, I do appreciate the fact that beta versions contain flaws and may not always be working properly. However, in this case the beta version messed up production software and it should not. Changing the file association of many file types in Windows without leaving a possibility to correct it is a serious flaw. I agree, let’s hope Adobe resolves this problem in future.
In the meantime, I have found a way to, at least temporarily, solve the problem by deinstalling and reinstalling the regular Photoshop version. This will restore all file associations, also in Bridge. I have no idea what will happen if the beta version is updated again.
Copy link to clipboard
Copied
Hi, @MeLeo,
Look, I appreciate your frustration, but as I was trying to point out, the operative word in that release is the word "beta." Beta should be respected as a big flashing sign that s#!t may happen. I've been beta testing software since 1985, and one really, really big thing you learn quickly is never to use beta software on work/important files. If you do so, I would suggest that you do it at your own risk.
There are times when released software messes up production software, which can happen when either a last-minute change was introduced into the software to resolve one issue but creates other issues. Or, the beta testers didn't have the right combination of software, hardware, or "use" pattern to create the problem. This is why, when reporting bugs, it's important to state the exact series of steps used to create the "event" and be very specific on the hardware and software used. It's common for bugs to only show up for one platform rather than the other (and even specific releases of the OS for a given platform).
When you download and use beta software, you do so at your own risk. I know some beta testers test with separate machines, but I've never done that as I do not have the money or time to maintain two systems.
If anything, I do fault Adobe for giving the impression that this public beta is fine and dandy and that you can try these new features and enjoy them. IMHO, I do think they should have had "some" warning that it is beta software.
Copy link to clipboard
Copied
Thanks Gary_SC for this addition.
Copy link to clipboard
Copied
Just a TLDR...
1. don't EVER install Beta software from ANY company on a production machine. EVER!
2. Shame on Adobe for even suggesting that their Beta's are just a "fun little pre-release playground". They are NOT!
People are lucky they didn't have to completely reinstall Windows, which happens very often. Treat Beta's like Malware, and let other people be the "experiment testers".
Copy link to clipboard
Copied
Copy link to clipboard
Copied
the 2024 versions are not working - how can I get the photoshop tool back in bridge 2024 - messing up my workflow - thanks!!!!!!!!!!
Copy link to clipboard
Copied
nevermind - it's working now!!!!!!! yay!!!!!!!!!!!!!!