Not signed in (Sign In)

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorsmolk
    • CommentTimeOct 2nd 2011
     
    I received an alarming error message yesterday night:

    Error during opening
    An error occured while opening the project; (Not all) data could be read properly. A backup of the broken project has been created, choosing "Show" will reveal it in Finder.
    The opened project will be repaired. You should check the integrity of the contents!

    This with an almost completed manuscript. How do I check the integrity of the contents when the contents is > 600000 words or so?
    More than that, I just want to get on.
    •  
      CommentAuthorfehnman
    • CommentTimeOct 4th 2011
     

    Has this been resolved?

    •  
      CommentAuthordirk
    • CommentTimeOct 4th 2011
     

    Moved to email at least, hopefully also resolved :)

    •  
      CommentAuthorsmolk
    • CommentTimeOct 4th 2011
     
    Yes and no. Well, I now know I only need to check one document, and I can relatively easily find out if anything changed in it. But I'm still disturbed to find this happening to me, and not assured it won't occur again. Is it the software or an electronic blitch?

    I mean, I once had an email which as delivered wrong. Yes, it can. The last two digits of the address before @ had changed. The recipient notified me, and also stood amazed, because he saw that I had addressed it correctly.

    So if that's what happened, OK. But if it's the upgrade, I'm very worried.

    Also, I wonder how you found this document to be the victim/culprit. I can say that it had been opened recently within the project, I believe I made a little change, and then closed it again.

    Anyway, thanks for asking!
    •  
      CommentAuthormax
    • CommentTimeOct 4th 2011
     

    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.

    •  
      CommentAuthorsmolk
    • CommentTimeOct 4th 2011 edited
     
    Wow, so it's so rare, it only struck now, although it could have struck ever since 1.5 came out ? That is something. In fact, it gives me some peace of mind. Not sure how long it is since 1.5 came out, but I've been using it for at least 310 days each year since it did.... It's been 8 years now that I use Ulysses. Eight years too that I've embarked on this project, it's time to let it go and be published.
    •  
      CommentAuthormax
    • CommentTimeOct 4th 2011
     

    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. :)

    •  
      CommentAuthorsmolk
    • CommentTimeOct 4th 2011
     
    Always glad to help, even when it initially hurts...
    •  
      CommentAuthormax
    • CommentTimeOct 4th 2011
     

    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.

    •  
      CommentAuthorsmolk
    • CommentTimeOct 4th 2011
     
    archaeology is great, isn't it
    •  
      CommentAuthorzenjar
    • CommentTimeOct 5th 2011
     
    I had this same problem with 2.1. At first I tried reinstalling from the app store, but it still hung when loading preferences. Eventually I had to:

    1. drag Ulysses app to the trash
    2. delete Ulysses folder from ~/Library/Application Support (my Ulysses project files are saved in dropbox, so deleting this folder didn't delete any working projects)
    3. Reinstall Ulysses from the app store. I then reopened each Ulysses project, saved it with a new name (just in case!), then deleted the old project file (again, just in case).

    It worked for me, but your actual mileage may vary :)
    •  
      CommentAuthormax
    • CommentTimeOct 5th 2011
     

    @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 :/

    •  
      CommentAuthorzenjar
    • CommentTimeOct 5th 2011
     
    Thanks Max,

    I also deleted the preferences along with the above 3 steps - thanks for mentioning that. Since the operation hung on preferences, this was the obvious culprit. I also noticed the option to select a backup location wasn't available in 2.1.

    From my point of view, this is a good change - though it confused me at first. I still save my project files to dropbox (soon iCloud ;). I use Ulysses on an iMac and Macbook, both with TimeMachine backup, so this assures that I won't loose everything if dropbox, or one of my hard drives, give up.

    Cheers
    •  
      CommentAuthorsmolk
    • CommentTimeOct 6th 2011 edited
     
    hugely ignorant question: If I were to follow those steps (under Snow Leopard), would I lose my themes etc as well?
    I think not but just to make sure....
    •  
      CommentAuthorzenjar
    • CommentTimeOct 6th 2011
     
    Well, I'm not sure. I was able to recover my projects in 2.1.

    I made some changes to my fonts & colors and paragraph/inline styles. But not sure if I did that before or after recovery. Sorry I couldn't be of more help.
    •  
      CommentAuthormax
    • CommentTimeOct 6th 2011
     

    The steps under Snow Leopard are the same as described here except that the path is different (no sandbox):

    ~/Library/Preferences/
    

    And still deleting just this file should be enough:

     com.soulmen.ulysses2.plist
    

    Themes and backups will be preserved this way.

    •  
      CommentAuthorsmolk
    • CommentTimeOct 6th 2011
     
    I do not have the number 2 in com.soulmen.ulysses2.plist (I have a total of nine soulmen preferences, just not this one, but com.soulmen.ulysses.plist)
    I am running 2.1, though
    •  
      CommentAuthormax
    • CommentTimeOct 6th 2011 edited
     

    Ah, then you're running the non-App-Store version. It's identifier is com.soulmen.ulysses.plist Same rules apply.

    •  
      CommentAuthorsmolk
    • CommentTimeOct 10th 2011
     
    Ah, thanks. BTW, I don't even think anything *was* lost in the document I had to check. At least, compared to a backup it had no differences apart from one command I added.

    I do face the spinning wheel too often though. It will disappear, it's just slow, but painfully slow—it does miss out on characters I typed because it cannot keep up. And I'm a two-finger typist....
    •  
      CommentAuthormax
    • CommentTimeOct 10th 2011
     

    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...

    •  
      CommentAuthorsmolk
    • CommentTimeOct 13th 2011
     
    I sent an urgent email - as the project once again has problems, but now no longer opens at all. And I need to get on with it now - so it is immensely frustrating that I cannot do a single thing.
    •  
      CommentAuthordirk
    • CommentTimeOct 13th 2011
     

    We've received the email and are currently looking into this issue. We will get back to you as soon as possible.

    •  
      CommentAuthorsmolk
    • CommentTimeOct 13th 2011
     
    all well again! great great!
    •  
      CommentAuthorfthom
    • CommentTimeNov 7th 2011
     
    Hello Dirk,

    As I got the same Error during Opening 3 weeks ago I wonder if ther is a solution already and an update on the way?
    Thanks
    •  
      CommentAuthormax
    • CommentTimeNov 7th 2011
     

    º@fthom: We are working on a solution. You may want to drop a line to support@the-soulmen.com if you'd like to test a preview version when it becomes available.

    •  
      CommentAuthorsmolk
    • CommentTimeNov 7th 2011
     
    I will. Ulysses sometimes has difficulty presenting the contents of documents in either preview or tab. It's still there (I think)... so I'm going for the beta. Have my five or six-fold backup strategy in place, and seatbelts to boot
    •  
      CommentAuthorfthom
    • CommentTimeNov 7th 2011
     
    Thanks, Max. I will drop a line to support to test the preview