Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
1 to 27 of 27
Has this been resolved?
Moved to email at least, hopefully also resolved :)
Well, this is nothing with this update. What you finally allowed us is to discover a very latent bug in the persistence layer being part of Ulysses since version 1.5 at the least. With this bug, open documents could sometimes be lost. Very rarely, but they can.
We will make sure it is fixed in Ulysses 2.1.1, which we plan to release still this october.
Well, I am not 1000% sure it was in there since 1.5. But it definitely was since 2.0 -- so that's still well over 2 years. It struck some people but we never managed to find it. Actually it was a bug in one of the 2.1 betas that caused me to look into some code that I wrote long time ago. Now with your problem and a couple of thoughts later it's quite clear what it was and how to fix it. :)
I just checked it again out of curiosity .. it's been there since like forever. The oldest date I can confirm is February 2009, that's pre-2.0 and so I guess its been there quite a bit longer.
@zenjar: may the instructions in this thread might have done the trick for you as well. Please note that as of Ulysses 2.1, backups can no longer be saved to a user-defined location. So deleting the application support or the container folder (see the other thread) is quite an invasive operation :/
The steps under Snow Leopard are the same as described here except that the path is different (no sandbox):
And still deleting just this file should be enough:
Themes and backups will be preserved this way.
Ah, then you're running the non-App-Store version. It's identifier is com.soulmen.ulysses.plist Same rules apply.
That spinning wheel is probably a side-effect of our switch to Garbage Collection. Way less crashes but decreased performance. We'll see if we can switch to ARC for Ulysses 2.1.1. Would also be very crash-savvy but will probably be faster than 2.x. Fingers crossed this does work out...
We've received the email and are currently looking into this issue. We will get back to you as soon as possible.
º@fthom: We are working on a solution. You may want to drop a line to email@example.com if you'd like to test a preview version when it becomes available.