Jump to content

scotsman

Level 1
  • Posts

    9
  • Joined

  • Last visited

Posts posted by scotsman

  1. Wow guys sooo many bugs still... totally aware of how software development works but this isn’t going well for me on iOS.

    - repeated crashes when selecting a shortcut notebook

    - blank screen when tapping on any note

    Can’t even test the most annoying bug before was a sudden crash when I was midway reading a pdf. It’s completely unusable for me.

     

    going to try the logout/re-sync. Which is a problem with 6k notes.

  2. OK so I think I remember what I did now. I went into the container that contains the Evernote database (named www.evernote.com ). I made an alias of it and then moved the original into my documents folder. Bingo - pdf's saved directly again. I did just try this in Big Sur though but no luck. Maybe the sandboxing system has changed? Beyond my paygrade.

  3. I recall there was a fix to this that I did before that had something to do with where the note database was stored and the new OSX file structure. I remember I created an alias of the database and then moved it to another place on my hard drive. This re-enabled the editing and direct saving of a PDF. Anyone familiar with this fix, and whether it is is even possible on Big Sur? I wish I had written it down...

  4. On 14/11/2016 at 1:22 PM, Kosterby said:

    This is a technical answer - use at own risk!!!

    Preview will no longer allow you to save documents back into documents which live in the user library folder.

    Evernote stores our documents in /Users/myuseraccount/Library/Application Support/com.evernote.Evernote/accounts/www.evernote.com - most likely a good design!

    I know my way around the terminal - so this is what you can do:

    • cd /Users/myuseraccount/Library/Application Support/com.evernote.Evernote/accounts/
    • mv www.evernote.com ~/Documents
    • ln -s ~/Documents/www.evernote.com

    Explanation:

    First line moves the terminal into the evernote database folder. Second line moves the database folder to the users document folder. Third line makes a link from the original database folder to the documents folder.

    The result is that Evernote continues to work, and Preview now thinks the files are in the Documents folder (which they are), and allow us to edit them.

    This is not really the right way to do this - But it will work until Apple and Evernote sort out their stuff.

     

    This is a genius solution! I am so happy to have found this fix. Was driving my crazy.

    • Like 1
×
×
  • Create New...