Edit Placed PDF Fails to Update Correctly On First Edit Document Attempt And Subsequently Can't Be Saved

[Hangman]

I'm unsure if this issue relates specifically to this reported bug fix in beta build 2.2.0.1994, Release Candidate 2...

Quote

Bugs affecting macOS

• Editing an embedded document file will cause parent file to fail to save. [AFD-6819]

But this is still not working in the latest Publisher v2 Beta...

Steps to Reproduce

1. Create a new Publisher document with the Image Placement Policy set to Prefer Embedded
2. Place a PDF file
3. Save the File
4. Select the placed PDF file in the layers panel and select Edit Document in the Context toolbar
5. Note how there is no Assigned Profile warning (when it is set to 'warn' in Preferences)
6. Make a change to the embedded file, the change is acknowledged in the title bar with an asterisk
7. Close the embedded tab and the source document shows no asterisk in the toolbar and 'Save' is greyed out in the File menu
8. Do a Save As and overwrite the file
9. Close and reopen the Publisher document - note how the change made to the embedded document hasn't been saved
10. Repeat steps 4 through 7 above and this time both the Assigned Profile warning appears in Step 5 and when the embedded document is edited and the tab closed, the source document now shows an asterisk in the title bar and 'Save' is no longer greyed out in the File menu

[Sean P]

Hi Hangman,

I can still reproduce this in 2.2.0.1999 and this is still an issue, so I will get it logged. Note I did edit your Step 10. It previously said repeat steps 1-7, however I've changed it to be steps 4-7, as demonstrated the last part of your recipe (otherwise I'll be continuously making new documents).

[Hangman]

Hi @Sean P,

Thanks for confirming, logging and editing point 10 (good spot)... Is .1999 an internal build?

[Affinity Info Bot]

The issue "Editing placed PDF fails to save changes until source file is saved and reopened" (REF: AF-31) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.