Because of this, the plugins did NOT function as expected when Ps Beta opened.
The plugin installations DID transfer and the plugins were present in their proper locations when PS Beta 26.0 opened, but the data stored in PluginsStorage did NOT transfer. This is going to be a major problem for plugin users where data for the plugin is stored on the hard drive. It will require the user to recreate it, which can be a real headache.
It is my understanding that plugin data is supposed to transfer automatically to new versions of Photoshop, but it didn’t happen today. I’m pretty sure this is a bug since the same problem occurred on both my Windows and Mac computers and did NOT occur that I can recall when Ps Beta upgraded from version 24.x to version 25.0.
I can confirm this problem in the beta version after the upgrade to 26.0. I didn’t pay attention if this worked in prior minor updates. Perhaps the transfer is handled differently in the beta than in the release version?
However, since there have been problems in the past with getting the PluginsStorage folder to the new versions, I store the data for my new plugins in a different location. Fortunately, this is now possible as getEntryWithUrl has been implemented.
Yes, Beta is different since there is only one installation. The major version update goes into the same Beta location instead of a new folder labeled 2025. The usually migration mechanisms do not apply to Beta.
We have noted this issue with UXP and Beta, and I expect we will have a fix for it. However, it is too late for this year. We will announce the change when it is ready.
Thanks for the update, Sam. It sounds like my memory of Ps Beta properly updating UXP user data when version 25.0 came out is faulty. I don’t remember there being an issue, but maybe I wasn’t using Ps Beta almost exclusively like I am now. It also sounds like there won’t be a similar issue when Ps 2025 GA is eventually released. That will be a big comfort to my customers and significantly fewer headaches for me.