Iztok Posted April 20 Posted April 20 I make package an want to save copy of document with different name in same package folder just add letter a, can't Quote
NotMyFault Posted April 21 Posted April 21 13 hours ago, Iztok said: I make package an want to save copy of document with different name in same package folder Why? Seems a perfect recipe for getting trouble. A package is intended to have everything in one folder for ONE publisher document. Old Bruce, PaulEC and Alfred 3 Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
Iztok Posted April 22 Author Posted April 22 because I made some versions of same document, you never do this? You design in two or three direction or you need other document in different langage, so you save as same document but ext as FR as France language, that's why. I need solution not some wird conclusions. Quote
Alfred Posted April 22 Posted April 22 6 minutes ago, Iztok said: I need solution not some wird conclusions. I don’t think there’s anything weird about what @NotMyFault has suggested. If you want to keep related package folders together, put them in a parent folder instead of looking for a way to have the contents all jumbled up. PaulEC 1 Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)
NotMyFault Posted April 22 Posted April 22 44 minutes ago, Iztok said: because I made some versions of same document, you never do this? You design in two or three direction or you need other document in different langage, so you save as same document but ext as FR as France language, that's why. I need solution not some wird conclusions. A package in Publisher is a folder where Affinity stores copies of all ressources (files linked) relevant for the documents, using a specific naming convention. If you put several documents in the same folder, conflicts will occur, in worst case Affinity overwrites or deletes a file currently open, leading to the error message you observed. Your intention to have multiple versions is valid, your decision to throw multiple documents into the same folder maybe less valid. Now you can shoot the messenger, or act accordingly and keep the packages separately, or try to organize multiple language versions in other ways within one document, e.g. Books. I‘m out of this thread for good. Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
Old Bruce Posted April 22 Posted April 22 On 4/20/2025 at 12:59 PM, Iztok said: I make package an want to save copy of document with different name in same package folder just add letter a, can't For some reason the file has lost access to some placed files used in Monograf 11a.afpub. [EDIT to add the word Monograf, thanks NotMyFault] I have absolutely no problem with opening an .afpackage file and editing it, then saving it in the same folder. The saved file will have an extension of .afpub, not .afpackage. When you edited the .afpackage file; Did you change some of the images used? Did you chose to use a new font? Did you delete some of the image files from the images folder? Did you change some of the names of the folders or move the folder structure to a new location? Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
NotMyFault Posted April 22 Posted April 22 9 minutes ago, Old Bruce said: to some placed files used in 11a.afpub. Sure? You may have missed the folder name contains a space character and the popup did a line break. Old Bruce 1 Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
Iztok Posted April 24 Author Posted April 24 On 4/22/2025 at 6:38 PM, Old Bruce said: For some reason the file has lost access to some placed files used in Monograf 11a.afpub. [EDIT to add the word Monograf, thanks NotMyFault] I have absolutely no problem with opening an .afpackage file and editing it, then saving it in the same folder. The saved file will have an extension of .afpub, not .afpackage. When you edited the .afpackage file; Did you change some of the images used? Did you chose to use a new font? Did you delete some of the image files from the images folder? Did you change some of the names of the folders or move the folder structure to a new location? didn't open and save On 4/22/2025 at 6:38 PM, Old Bruce said: For some reason the file has lost access to some placed files used in Monograf 11a.afpub. [EDIT to add the word Monograf, thanks NotMyFault] I have absolutely no problem with opening an .afpackage file and editing it, then saving it in the same folder. The saved file will have an extension of .afpub, not .afpackage. When you edited the .afpackage file; Did you change some of the images used? Did you chose to use a new font? Did you delete some of the image files from the images folder? Did you change some of the names of the folders or move the folder structure to a new location? No Quote
NotMyFault Posted April 24 Posted April 24 Any chance to agree on using the package feature as intended, and use the created folders only for one Affinity document? https://affinity.help/publisher2/en-US.lproj/pages/Publishing/aboutPackaging.html Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
Staff NathanC Posted April 25 Staff Posted April 25 I would agree with the consensus to save copies to separate folders/locations rather than saving back to the packaged location, but with that aside I have attempted to duplicate this issue. In each attempt I have been able to successfully File -> Save as back to the packaged folder location as an .afpub file without the resulting error. There is likely more to this, if you're able to consistently replicate this issue please provide more information on any steps required, and if it's specific to a certain document please supply a copy of the file. It also may be worth saving to an entirely different location on your Mac (not backed up by any Cloud Storage services) just to rule this out. Quote
Recommended Posts
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.