No Option To Copy Settings Etc From Release Version

[footeg]

Hi, in the exe download version of Affinity Photo 2.1.0.1732 on Windows 11, there is still a problem I reported earlier that, under settings, the option to copy settings & content from the release app is still greyed out. I was hoping it would be resolved in the latest update to the beta version.

[walt.farrell]

Works fine for me, @footeg. Of course, it worked before, too, so that may not be relevant.

I have the unsandboxed version of the V2 apps and of the beta apps on my Win 11 machine.

[MikeTO]

I believe Serif said there may be an issue copying them over if your retail and beta versions are a combination of MSIX and MSI installers.

[Patrick Connor]

4 minutes ago, MikeTO said:

I believe Serif said there may be an issue copying them over if your retail and beta versions are a combination of MSIX and MSI installers.

they did indeed  comment but it was because for unsandboxed version we have moved where the shared data is stored (from one location in 2.0.4 to a new location in 2.1 beta), to better support corporate customers. I am seeing if it was investigated and turned into a formal report

[walt.farrell]

39 minutes ago, Patrick Connor said:

but it was because for unsandboxed version we have moved where the shared data is stored (from one location in 2.0.4 to a new location in 2.1 beta), to better support corporate customers. I am seeing if it was investigated and turned into a formal report

I have unsandboxed (EXE) for both 2.0.4 and for 2.1.0.1730 & .1732.

And yes, the Retail preferences are in .Affinity while the Beta preferences are in AppData\Roaming.

But I can copy from Retail to Beta using that Preference function, so I don't think that's the issue.

[footeg]

I too have unsandboxed (EXE) for both 2.0.4 and for 2.1.0.1730 & .1732 but, for me, the option to copy is still greyed out. There is a 2.0(Beta) folder in both .Affinity & AppData/Roaming\Afifinity\Photo. I tried copying the 2.0 folder between the 2 locations but the problem remains.

[Patrick Connor]

41 minutes ago, footeg said:

I too have unsandboxed (EXE) for both 2.0.4 and for 2.1.0.1730 & .1732 but, for me, the option to copy is still greyed out.

Sorry but between 2.0.4 and 2.1.0 we have moved where the information is stored for the unsandboxed version. Rest assured that future unsandboxed (EXE) betas will pick up the information from the 2.1.0 unsandboxed release version, BUT there is no code in 2.1.0 EXE beta to look in the location Release EXE 2.0.4 is using.

HOWEVER 2.1.0 RELEASE will move the stored information from the previous 2.0.4 RELEASE location.

So unfortunately this is one function where the current Beta EXE does not match the current Beta MSIX, and for the sake of the last few weeks of the 2.1.0 beta we are unlikely to change this, due to the transient nature of the problem (it goes away when the next 2.1.x or 2.2.y beta starts). 

So thanks for your report but this is to be expected, but only for this time around the beta cycle.

[walt.farrell]

59 minutes ago, footeg said:

I too have unsandboxed (EXE) for both 2.0.4 and for 2.1.0.1730 & .1732 but, for me, the option to copy is still greyed out. There is a 2.0(Beta) folder in both .Affinity & AppData/Roaming\Afifinity\Photo. I tried copying the 2.0 folder between the 2 locations but the problem remains.

 

9 minutes ago, Patrick Connor said:

Sorry but between 2.0.4 and 2.1.0 we have moved where the information is stored for the unsandboxed version. Rest assured that future unsandboxed (EXE) betas will pick up the information from the 2.1.0 unsandboxed release version, BUT there is no code in 2.1.0 EXE beta to look in the location Release EXE 2.0.4 is using

I think I figured out the difference between @footeg's setup and mine. I previously had the MSIX installs of V2 on my Win 11 system, and I replaced them with MSI versions but I did not delete the V2 MSIX folders from .affinity so they are still there. And that is probably why I get the migration option but @footeg doesn't.

[footeg]

17 minutes ago, Patrick Connor said:

Sorry but between 2.0.4 and 2.1.0 we have moved where the information is stored for the unsandboxed version. Rest assured that future unsandboxed (EXE) betas will pick up the information from the 2.1.0 unsandboxed release version, BUT there is no code in 2.1.0 EXE beta to look in the location Release EXE 2.0.4 is using.

HOWEVER 2.1.0 RELEASE will move the stored information from the previous 2.0.4 RELEASE location.

So unfortunately this is one function where the current Beta EXE does not match the current Beta MSIX, and for the sake of the last few weeks of the 2.1.0 beta we are unlikely to change this, due to the transient nature of the problem (it goes away when the next 2.1.x or 2.2.y beta starts). 

So thanks for your report but this is to be expected, but only for this time around the beta cycle.

 

5 minutes ago, walt.farrell said:

 

I think I figured out the difference between @footeg's setup and mine. I previously had the MSIX installs of V2 on my Win 11 system, and I replaced them with MSI versions but I did not delete the V2 MSIX folders from .affinity so they are still there. And that is probably why I get the migration option but @footeg doesn't.

Thanks to you both. I will wait for the 2.1.0 release version. All looking good with the beta so far.