PixelPoetix

I managed to identify the issue. It has to do with the way Publisher brings in pages from another Publisher document when using the Add Pages from File feature. I work with a few documents that have the same Master pages with the same names (which I often do with this specific set of documents I'm currently working with). From what I can remember, it used to let me add pages from a file that uses the same Master Page names but at some point it starting duplicating the Master Pages each time I did that resulting in many copies of the same Master Page all named the same in the destination file. I can't say what version I first started noticing that behavior since I don't work with this set of files very often. It's very possible I've not worked with them since before 2.4.2. But now in 2.4.2 it just crashes if the Master Page names are the same in the origin file and the destination file. Renaming all the master pages in the origin file to include a prefix different from the destination file seems to have solved the add pages from file issue. Though it's annoying that it doesn't just apply the same named Master Page in the destination file as was used in the origin file which I seem to remember it used to do in some prior version before it started duplicating Master Pages instead. And renaming all my Master Pages in the destination file so that they're all unique (there were some duplicate Master Pages with the same name from previous Add Pages from File actions performed using some previous version of Publisher that allowed that) seems to have solved the crashing when trying to Edit Detached. Something changed in this recent version since I used to not have these crashing problems with either of these actions. I've been doing these same actions on this set of files for years. Though, like I said, it's infrequent enough (once every couple months or so) that I very well might not have done so prior to the release of 2.4.2

I'm having HORRIBLE crashing issues with Publisher 2.4.2 on an M2 Mac as well which I just posted about, so this is clearly not an OS related issue. I sure hope Serif fixes this ASAP as I literally can't even finish a simple project right now. I REALLY hope this isn't what we have to look forward to now that Affinity sold out to friggin trashy Canva.

Publisher 2.4.2 keeps crashing and it's driving me mad! I'm on an M2 Max MBP running Sonoma 14.4.1. So far, just today, it's crashed on me at least 6 times. I've even tried restarting my Mac. Still crashes. It's crashed multiple times when trying to modify content from a master page using Edit Detached. And now it's crashing when trying to insert a page from another Publisher file, even after restarting my Mac. Any chance a fix is in the works and you have a beta version I can use? This one is making it impossible for me to finish one simple project that I would have been done with by now if it weren't for all this time wasted from the crashes.

Hello Serif Friends... There's a certain behavior within Publisher that I find particularly annoying: when I hide a layer or layer group that has Text Wrap enabled for itself or for any nested layer within it, those text wrapping settings continue to affect visible text layers. I haven't been sure whether this was intended behavior or a bug and finally did a search here in the forums and discovered that it is indeed the intended behavior apparently to accommodate those who are used to the same behavior within InDesign. While I get that reasoning and I can certainly see the merit in having this behavior enabled for certain use cases, I would also LOVE the option to disable this behavior when it makes more sense for my workflow (which for me, at least, would be most of the time). To be clear, I am well aware of the option to "Ignore Text Wraps" for a visible text frame but this is NOT a suitable workaround since that visible text layer may still need to wrap around other visible layers. So currently, the only workaround is to disable text wrap for any hidden layers that I don't want affecting visible text while I work on those visible layers. But then, if I want to compare the look of one layer group to another, for example, I can't just hide one group and make the other one visible. Instead, I have to disable text wrap for each individual layer that has it in the currently visible group, hide the group, show the hidden group and then go through and re-enable text wrap for each individual layer that uses it for that now visible group. This makes comparing two overlapping layer groups a tedious experience. If I had the option of toggling a setting that prevents hidden layers with text wrap enabled from affecting visible text layers, I could then simply hide and show each layer group to compare them. Alternatively, perhaps you would consider a hybrid solution whereby individually un-checked layers with text wrap enabled continue to behave in the way the devs intended. But if they are contained in a layer group, then that group's checked or un-checked state would determine whether its child layers still affect visible text layers. I will illustrate with some example scenarios. In each of the following scenarios, all object layers have text wrap enabled. SCENARIO 1: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A, OBJECT 2A and OBJECT 2B. SCENARIO 2: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ✓ PARENT GROUP 2 ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A, OBJECT 2A and OBJECT 2B. SCENARIO 3: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ☐ OBJECT 1A ✓ PARENT GROUP 2 ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A, OBJECT 2A and OBJECT 2B. SCENARIO 4: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ☐ PARENT GROUP 2 ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A but NOT around OBJECT 2A nor OBJECT 2B. SCENARIO 5: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ☐ OBJECT 1B ☐ PARENT GROUP 2 ✓ OBJECT 2A ✓ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A and OBJECT 1B but NOT around OBJECT 2A nor OBJECT 2B. To me at least, a hybrid solution such as this would be an elegant way to please BOTH those who prefer the current behavior, i.e. those who are expecting a similar experience as they may have had with InDesign, AND those of us for whom this current behavior drives them bonkers...and all without having to choose a side AND even allowing both sides to easily adapt their workflow to make use of the alternative if and when they ever find the need to. I hope all of the above makes sense. If you've made it this far, thanks for taking the time to read through my suggestion! Let me know if I can offer any further clarification. In the meantime, keep up the AMAZING work! I've been LOVING Publisher overall and look forward to even more improvements over time. ~ Chris