Not signed in (Sign In)

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

    •  
      CommentAuthormadox
    • CommentTimeJul 5th 2010
     
    I saw the twitter post, dropbox had corrupted files. This i have experienced myself on a rather large U. file..i had to go back to a backup on that one. Ulysses wouldnt read it properly and alerted on this on launching.
    This is accually old news..when i got this problem i searched on it and found this post in the competing camp..
    http://www.literatureandlatte.com/forum/viewtopic.php?f=2&t=5295&start=120

    Seems like a new beta of dropbox is going to solve the way it handles these kind of files..still..risky..
    Maybe U should have way to dump the project file to a zip and export it to a preffered destination as well..
    •  
      CommentAuthormax
    • CommentTimeJul 5th 2010
     

    There is nothing to say against DropBox as long as you have backups like ours or Time Machine. Exporting as zip does not really work for us. More or less we're constantly saving your project as you write. This means that the compression would run all the time and keep your CPU quite busy. Not to speak of the dropbox folder that'd restart the upload every few seconds...

    •  
      CommentAuthorjb
    • CommentTimeJul 11th 2010
     
    Max wrote:
    "Exporting as zip does not really work for us."

    Could you elaborate?
    If exporting as zip takes place only when invoked (by a menu command), why would this keep the CPU busy?
    Probably just my limited understanding of how Ulysses works.

    My assumption is that only zipped projects are safe with Dropbox.

    It would be nice to simplify the process: rather than locating the Ulysses project in Finder, compressing it, and then dragging it to the Dropbox folder, all of this could be managed from within Ulysses. Not essential, but a nice touch, I think. (A feature of scrvnr, fwiw.)

    IOW, export as zip not as a replacement for regular save, but as an addition that would allow safe use of Dropbox.
    •  
      CommentAuthormax
    • CommentTimeJul 11th 2010
     

    Okay, now I understand you better. What we could do without any problems is to add a "compress" option to the project exporter. This would write the project as ususal but compressed. Would this be something?

    •  
      CommentAuthormadox
    • CommentTimeJul 11th 2010
     
    Yea, would be a nice touch. I do the same as you described above, save localy, zip and copy it to dropbox. Then copy it back and unzip..
    I have experienced several project corruptions using dropbox "live", working in U and the file on dropbox..
    •  
      CommentAuthorjb
    • CommentTimeJul 11th 2010
     
    Perfect ;-)
    Perhaps with a date stamp added to the project name?
    •  
      CommentAuthormax
    • CommentTimeJul 11th 2010
     

    The best is you file a feature request in our bug tracker (http://mantis.the-soulmen.com) and add the things you'd like. We'll then see what we could do ;)

    •  
      CommentAuthors2rt
    • CommentTimeJul 13th 2010
     
    Interesting, my U files live in my Dropbox repository and are synced across three computers. Haven't had a moments corruption or problem.
    •  
      CommentAuthormadox
    • CommentTimeJul 13th 2010
     
    s2rt..i had that to..but one day it was corrupted and U wouldnt open the project properly..and revisin a project on 7-8mb to see if something is missing is a ***** job..
    However, its known, just browse the dropbox forums, they have a beta out of a version that should handle it better though..still..its a gamble..
    •  
      CommentAuthormax
    • CommentTimeJul 13th 2010
     

    madox: but there is some console output that shows you what could not be loaded correctly. So that search should be a bit easier. We plan to lift this up into the interface though...

    •  
      CommentAuthorloulesko
    • CommentTimeJul 17th 2010
     
    Hey there for those of you frustrated by the inability to use drop box, I've found a work around using Panic's Transmit. Transmit as a syncing function that works fabulously well with Ulysses projects. On my laptop I created a folder names CurrentWritingProjects and then did the same on my web site. In transmit navigate to the local CurrentWritingProjects on the left panel and to the server based one in the right panel, then use the Sync function. It works flawlessly.
    •  
      CommentAuthorloulesko
    • CommentTimeJul 17th 2010
     
    The issue according to the Drop Box forum is the use of resource forks. This is apparently fixed in the next version of Drop Box.
    •  
      CommentAuthormax
    • CommentTimeJul 18th 2010
     

    Actually we don't use resource forks. There must be some other issues maybe with concurrency or so. However, DropBox works almost perfect most of the time. Whenever there is a problem, you can simply revert to a backup project...

    •  
      CommentAuthorAmberV
    • CommentTimeAug 12th 2010 edited
     
    Just to shed a little light on this, it has nothing to do with resource forks, that DropBox report that they released was erroneous in that aspect. In fact they mentioned the software I work for by name as one of the incompatible ones; we don't use resource forks either. ;) Resource forks may be a problem, but it isn't causing the issue here.

    This issue is, as Max speculates, entirely down to concurrence and the very real probability that files will "collide" and end up with versions that have been renamed to "xxx conflicted copy datestamp.etc". With normal files, you can examine both of them and figure out which you meant to keep as the latest, or manually merge the conflicts and save a new copy. With a bundle format, these conflicted files are all hidden from you by default, and if the conflicted files are project control files, it can be next to impossible to merge them or decide which is best.

    It's remarkably easy to accidentally end up with a corrupted project like this. All it takes is a laptop that is offline for a while before syncing. Any time you make edits offline, without syncing first, you run the risk of it. Some people never work that way, or always remember to sync before they head out, so they never have a problem. There are things you can do to make sure you never run into it, but it is a risk.

    But don't rely on the so-called beta coming out to fix the problem. In fact, that beta is already out and a part of Dropbox-stable these days. It's aimed at a different problem entirely. The issue here is not going to go away unless Dropbox fundamentally changes their conflict resolution. And I hope they don't, frankly. You need conflict resolution, and the only other sane way to handle it is with dialogue boxes, which I hate. I'd rather be able to examine the files at my leisure and solve the problem, and dialogue boxes won't help in unravelling the conflicts in a tightly-knit bundle format, anyway.
    •  
      CommentAuthormax
    • CommentTimeAug 13th 2010
     

    I have to add -- that after using Dropbox with Ulysses for two months now, I once had the occasion that a whole document was just gone. Not sure what the reason was, but that whole folder for the document was just gone. Luckily it was almost empty. However, everyone using Ulysses with Dropbox is at danger there...

    Where is the built-in secure syncing facility??

    ...

    ...

    <writing reminder to self>

    •  
      CommentAuthormalter
    • CommentTimeNov 15th 2010
     
    I work live on my hard drive most of the time but the backups are synced with Dropbox. To achieve a faster sync and to avoid problems due to the package the Ulysses backup creates i've written a simple AUTOMATOR function. The folder actions automatically compresses the Ulysses backup and places it into my backup Dropbox folder. This is done in no time with a single step within AUTOMATOR.

    Cheers!
    Sebastian