Problems with the new Auto Save Feature

I have been trying to use the Auto Save feature in the latest versions of Classic and I keep running into problems.

The problem is that intermittently if I manually perform a save, Classic will put up a dialog saying that another version of the app has performed a save and if I do one I could lose my changes. Of course I DO NOT have another version of Classic running.

I did this late yesterday afternoon and after my save the page I was working on would not publish. Not sure what was going on but I could not get it to publish anything at all. I had to rebuild a fresh version of the page in order to get it working again.

Not sure what is going on with the Auto Save, so I decided to not use this feature, although it would be nice if it worked.

Hey @handshaper,

I don’t believe this is an issue caused by the new auto-save feature, I have seen this warning message in Classic before auto-save was added.

Can you do me a favor? Try turning auto-save back on. If you notice that warning again, can you look in your Dock and tell me if you see two RapidWeaver Classic icons instead of just one?

I’ll try it again. But just to be clear when this happened I did check to see if there were two instances of Classic in the dock and there was just one.

When next it happens I’ll pay closer attention and see what info I can gather.

I turned the Auto Save feature back on and after about 1/2 hour of work the following dialog popped up on the screen when I tried to perform a MANUAL save of the project.

I checked the dock and there is no other instance fo Classic running on the machine. Just to be sure I also checked the Activity Monitor and there is just the one copy of RapidWeaver running.

I opted not to continue with the save. I then kept an eye on the dirty document indicator, when it cleared I closed the project and reopened it to confirm that any changes I had made were not lost.

I was able to successfully perform a number of manual saves before this problem occurred. So I’m not sure if it was a timing issue were I was trying to do a save when RW was also doing a scheduled save.

2 Likes

I am also getting the same message after upgrading the the latest version of Classic. It does this when saving before closing and when publishing…“This document has been changed…”. I deleted older versions of RW (9.3.2 and 9.3.3) so not sure what is going on. When I first open a project from “recent”, the first page I get this message: Notice : file_get_contents(): read of 8192 bytes failed with errno=21 Is a directory in /Applications/RapidWeaver9.3.4.app/Contents/Resources/RWWebServerLaunch.php on line 178

The page has a blue dot, meaning I have changes that have not been posted (not true). I can go to the second page of the project, no problem, and then I can go back to initial page and all is good.

Thereafter, I only have the save issue as described by other post and when I publish a change in the page.

i get the same message. it often happens to me when i have different projects open

I went back to Classic 9.3.2 and no more error message, so it seems there may be some issues with the latest Classic update. Hopefully, someone can address this. Thanks.

The reason you are probably not seeing this is because the Auto Save feature was added in 9.3.3.

Yes, but Dan says no, they don’t see the issue.

Well I have run into this issue plenty of times. But it only seems to happen when I’m trying to do a save when RW is perform an auto save. It never happens any other time, only when doing a manual save, and then very randomly.

Thanks for your observations. I will continue with the older version until this is corrected, I guess. I really don’t even need auto-save, so I might download 9.3.4 again and turn off auto-save and see what happens.

I usually wait a bit when updates come along, as it seems some other issue crops up more often than not. I had just bought RW 9, so I figured I might as well keep it up to date. Oh, well.

I downloaded RW 9.3.4, set autosave to “Never” and now no issues as I open my project. Seems to me this is an Auto-save problem.

1 Like

Mmm not quite, I said I don’t think the issue is caused by the auto-save feature. I’ve seen that exact warning message long before the auto-save feature was added. It seems the auto-save feature simply caused that warning to surface more often.

We’re looking into it though and will report back when we have more information.

In the meantime, if you enable auto-save, perhaps it’s not necessary to do manual saves so often? The auto-save feature has a lot of options. If you set it to “After every change”, or even “After 5 minutes”, do you still see that warning pop up if you don’t try to manually save changes?

I just wanted to be clear. For me this message will only appear if I do a MANUAL save. I have never seen it any other time. Plus it does not do it every time I do a manual save, only periodically.

I’m to paranoid to never do a manual save. But at least I have figured out if the dialog does appear I simply cancel my save and proceed.

Yeah, I’m trying to find a way to reliably reproduce it but so far I haven’t been able to. Maybe you could send me a project file that you are seeing this on so I can try testing with it?

I thought this might be the case. :grin:

But the auto-save feature was designed so you wouldn’t need to do a manual save. Just have to take a leap of faith.

leap-of-faith-opt

For now I have adopted that approach and hope all will be well. Old habits die hard.

1 Like

I originally had it set on “after every change”, and I don’t remember if I was also doing a manual save, as I think I might have, being I do manual saves with just about everything. I am glad you do see this happening, as prior to this latest update, I have never had it occur, going all the way back to RW 6. I will try not doing any manual safe and see if that keeps things in step.

I just wanted to provide some data for you to help in solving this issue.

Thanks for getting back to me and I hope I can be of some help.

1 Like

I switched back to “After every change” and on publishing a change, the notice about the app being saved on another application came up. Now that may be true, as I previously had moved back to RW 3.3.2 and I now opened that project on RW 3.3.4. I will continue to play around with this and see if I can find some consistency for you. One thing I will try is to save the project with another name and then just open it in RW 9.3.4.

Seems sort of like going through a maze trying to find the answer. Reminds me of “Chumps at Oxford” with Laurel and Hardy as they walked and walked through a hedge maze while at Oxford….ha, ha.

No problem, thanks for the information.

If y’all want to send over any project files that you are seeing this on, I can see if I can replicate it on my end too. We have a guide here on how to share your project files and addons folder.

One more update:
I did a new save to a new folder, opened it with RW 9.3.4. Front page opened without that error message I had gotten originally. However, the front page did show that it was new and had not been published (which was done before). I then got the message about having been saved in a different app, where it asked if I wanted to save it. I first canceled the save and nothing happened, other than the beach ball. When I manually then saved it, the page would then be published.

So, I hope this is of some help, and I hope it isn’t just my human error and I am wasting your time with this.

Thanks again,

Pete

1 Like