Jump to content

Got a question on Designer [SPLIT]


Recommended Posts

Got a question on Designer. I open AD Version 2 and work in it BUT the save is in the AD version 2 BETA. I thought work in the released version would save as is and the work in Beta would save in Beta. Don't want to do to much if my work will have issues. I have NOT downloaded either of the other 2 softward Beta's as I wanted to test the Designer first. I use the EXE entenstions.  Thanks, C

System

Device name    User-PC
Processor    AMD Ryzen 5 3600 6-Core Processor                 3.60 GHz
Installed RAM    16.0 GB
Device ID    4DD0B91E-B632-4F94-B181-ED9BC6A87047
Product ID    00325-80000-00000-AAOEM
System type    64-bit operating system, x64-based processor
Pen and touch    Pen support

Edition    Windows 10 Home
Version    22H2
Installed on    ‎9/‎11/‎2020
OS build    19045.3208
Experience    Windows Feature Experience Pack 1000.19041.1000.0

 

Link to comment
Share on other sites

17 minutes ago, Sunshine Kid said:

Got a question on Designer. I open AD Version 2 and work in it BUT the save is in the AD version 2 BETA.

Please check which version of AD 2 you're really using. From your description, you have the beta version. If you click on the Account icon on the upper right, it will tell you the release you have.

There was a problem this morning, for a brief time, where the latest 2.2 beta update (2.2.0.1931) would overwrite the 2.1.1 installation, if you applied it.

So, if you start what you think is 2.1.1, but end up with 2.2.0.1931, you will need to uninstall that application and re-install 2.1.1.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

Hello,

I am here to decide between reloading the 2.1.1 program and signing up for the Beta for 2.2 because I allowed the app to update the accidental release yesterday 8/2. I feel nervous about both choices. I have a whole book that I edited and saved yesterday which will not open in 2.1.1 and I do not want to deal with any bugs/issues as I continue making my book or future books. So, I am asking for opinions on what would be my best option to keep my content and not have to deal with further issues.

Thank you,

J.T.R.

Link to comment
Share on other sites

18 hours ago, J.T.R. said:

So, I am asking for opinions on what would be my best option to keep my content and not have to deal with further issues.

  1. If you reinstall 2.1.1, you'll be able to work on other projects safely. And you'll be able to continue working on your current project from a backup you saved before you applied the unintentional 2.2 update to your 2.1.1 version.
  2. If you also participate in the 2.2 beta, you'll be able to continue working on your current project in its current state, rather than from a backup. But you are perhaps more likely to encounter problems using the beta than if you were using 2.1.1.

Another possibility, if you reinstall 2.1.1 and participate in the beta, is that you could create a new document in 2.1.1, or open a backup copy of your current project, and copy data from the 2.2 version of the project using Publisher 2.2, and paste it into the 2.1.1 version of the project using Publisher 2.1.1. That could be a lot of copying/pasting if you paste into an empty document. But if you know what changes were made since the last Save, you could work from the backup copy in 2.1.1 and only paste in the differences from 2.2.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

19 hours ago, J.T.R. said:

Hello,

I am here to decide between reloading the 2.1.1 program and signing up for the Beta for 2.2 because I allowed the app to update the accidental release yesterday 8/2. I feel nervous about both choices. I have a whole book that I edited and saved yesterday which will not open in 2.1.1 and I do not want to deal with any bugs/issues as I continue making my book or future books. So, I am asking for opinions on what would be my best option to keep my content and not have to deal with further issues.

Thank you,

J.T.R.

Funny enough, it's only the save file that is incompatible. It being a book, I'm not sure how laborious the process is to get a new file reconfigured, but we are normally are able to just copy and paste content from the beta to the 2.1.1/release version with no issues. I've seen comments in the past also of V2 data and V1 data being ported this way. That's provided there's no new features being used/under the hood changes to the structure of the content itself, then it should paste fine. I like @walt.farrell's suggestion to rely on a backup and to just paste in revisions.

Normally, we can run beta concurrent with the regular version. So if you uninstall/reinstall your release version and join/install the current beta, you will have two working copies to do the content swapping.

However, this really should not keep happening. As a beta tester, I'm gleeful when we get unanticipated secret updates (sometimes earlier iterations of what is pushed out later). But as for someone who is using an official version, this is more than a petty annoyance.

On average though, I've had good luck just using the beta. I still keep some projects right now I'm only using in production version due to the volume, but other production-related work (for example, mock-ups, photo edits) I will use in beta. It just depends for me how hard the data would be to replace. A book is fairly critical data and if content swapping does not work, then perhaps staff here can use their tools to get you back in business.

Sorry this happened to you.

Link to comment
Share on other sites

5 minutes ago, debraspicher said:

It being a book, I'm not sure how laborious the process is to get a new file reconfigured,

I've done it without too much difficulty to help someone reconstruct an approximately 30-60 page book, once, when it would Open in V2 but wouldn't Open in V1, where V2 had a bug fix that allowed use of the file.

But the workload definitely depends on the size of the book :)

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

This worked. I was able to make a PDF from the Beta version of the file and then import the PDF into the 2.1.1 version. Am concerned about future updates causing issues. Guess it would help to start file and then save and see if it shows a B to alert you that you are in the wrong version before working further. Thanks, Carol

Link to comment
Share on other sites

13 minutes ago, Sunshine Kid said:

Guess it would help to start file and then save and see if it shows a B to alert you that you are in the wrong version before working further.

If you start the beta, the icon in the upper-left of the screen will warn you. Additionally, if you Open a non-beta file in the beta you will get a warning. 

Nothing will help you if Serif releases an erroneous retail release update as they did this time, except paying attention to the forums, where retail updates are always announced. If you get a retail update without it being announced, don't install it. You can Follow this topic for that purpose: 

 

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.