Jump to content

Recommended Posts

Posted

I have been having the same problem with the same error. I downloaded the publisher for Windows yesterday and I cannot tell why this error occurs, there is no way of saving the file when the error occurs.... "Save as" will only produce faulty files that cannot be opened again. But it's still possible to export to PDF. I had to start over with my broschure... Pretty upsetting.

Is it possible to download an older version of publisher where this problem (hopefully) does not exist?

Hopefully the bug will be fixed soon.

Thanks!

Posted

Hello and welcome,

Please try the beta, they fix that problem.

 

MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3476)

Affinity Suite V 2.6.1  & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

I already had a halo, but it didn't suit me!

Posted

I'm having the same problem. "Save failed due to an internal error. This should be reported to the development team."

It has happened with multiple files in the past few days.

I'm losing work time (and patience) because I have no choice but to close the file(s), lose the work I have done, and then redo what I already did again and again. And again.

It's also inconsistent/random because when I reopen the file, redo the work and save in exactly the same way, it sometimes saves ok. 

 

 

Posted

@RLi

Have you tried the beta, as advised?

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Posted

Same problem here on Windows 10. Saving a file is pretty fundamental, I really regret updating my Publisher that was working fine before! The question is should I risk instaling a potentially even more unstable version (i.e. the Beta)?

Posted
8 minutes ago, m8rtyn said:

Same problem here on Windows 10. Saving a file is pretty fundamental, I really regret updating my Publisher that was working fine before! The question is should I risk instaling a potentially even more unstable version (i.e. the Beta)?

The Beta version is a standalone.

Also wishing I hadn't updated. I didn't have a problem with the earlier version.

Posted
7 minutes ago, m8rtyn said:

The question is should I risk instaling a potentially even more unstable version (i.e. the Beta)?

Yes

The beta states

"We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below."

Consider it as an emergency beta to address serious problems some users are having that affects their ability to do any work. Changes are minimal so the normal beta concerns should not apply any more than they would to a released version.

 

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Posted

As an immediate solution to save losing work done - Open an older or similar file so the set up etc is the same. Then delete everything and copy and paste from the faulty file to the new blank one. Then it allowed me to save to a new name. Obviously depends on how much there is to copy.

Posted

Thanks for the help carl123 and RLi, I'v been using my Mac for now hoping for a maintenanace release farily soon. If no sign of one by Monday then I'll try the beta.

  • Staff
Posted

Hi all,

As it's already been mentioned here, we have fixed the saving issue in the latest beta. The only workaround would be to downgrade to 1.9 if you wish not to use the beta in preference to the 1.10.0 as suggested in the beta thread. 

1 hour ago, m8rtyn said:

If no sign of one by Monday then I'll try the beta

We don't have an ETA for a public release, but will not be releasing it before Monday for sure. 

Posted
21 minutes ago, Gabe said:

Hi all,

As it's already been mentioned here, we have fixed the saving issue in the latest beta. The only workaround would be to downgrade to 1.9 if you wish not to use the beta in preference to the 1.10.0 as suggested in the beta thread. 

We don't have an ETA for a public release, but will not be releasing it before Monday for sure. 

I've tried to downgrade, but the installer fails due to having a newer version installed. I'm not sure how to downgrade?

Posted
42 minutes ago, Gabe said:

You would have to uninstall first, then install 1.9

Thanks, now back running 1.9.2 and all's well. Thanks for your help.

Posted

Aug-13-21 Same save error, same problem as discussed above. I was just at the master page layout, so I just restarted a new one and no save error so far. just got the programs yesterday, so I hope that the version is not a glitchy one. Love the program other than the first file save error right out of the gate. I am no tech, that is for sure, so I will avoid having to delete the file and reinstall for now if possible.

Please post any updates to the same problem. Other than that I will wait for the next update.

T

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.