Jump to content

dataminer

Level 1
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About dataminer

Recent Profile Visitors

1,071 profile views
  1. I am trying to export a local notebook. It all goes well but after the export procedure seems to have processed all the notes in the notebook I get the following message: "The file “content.enml” couldn’t be opened because there is no such file." I can find no way to solve or remove this problem. Eventually, after not getting anything useful from Evernote, I tried exporting the local notebooks one at a time and found that the problem was with only one notebook with a large number of notes. I went through that notebook selecting 250 notes at a time and exporting them until I got the same problem as I reported above. By gradually breaking that batch down into ever smaller batches I was able to isolate a note causing the problem. It was an empty note with the title Screenshot. When I deleted that note the batch exported without problem. So I searched through the remaining notes in the notebook for similarly titled notes and found about a dozen. Deleted them all and the problem went away. I’m not sure what produces empty notes with the Screenshot title, but I suspect it is one of the screen clipping options in the dropdown menu for the elephant symbol in the top bar. The fact that it was only notes in that one notebook (titled !_InBox) where things directed to Evernote are saved makes me think that this has arisen from a program update issue at some stage. This notebook had 800+ notes in it and I haven’t sorted them into the relevant folders for a very long time, so (given that I’ve now deleted those notes) it isn’t possible to identify the time period (and hence the Evernote version) in which they were produced. So, if you have this problem look for notes with the title Screenshot and delete them if they are empty. Dataminer
  2. I followed instructions from EN support to get back to a Time Machine version of 5.0.4 that had my notes WITH their tags, then I just followed your instructions and am back to 3.3 - with my current files and all the tags etc. intact. Thank you, and to all the others who contributed to this discussion of back-dating EN. I wish EN all success in recovering their reputation, but personally I'm moving my data out of EN to DevonThink Pro Office. Long experience has shown me that while it's complex and possibly over-featured for me, it is highly reliable while doing everything I want.
  3. Man, you must be one serious *****. ++++ For those who are wondering, the ***** text was m a s o c h i s t. Apparently the Evernote forum software considers this to be an unacceptable term. Depends on your point of view I guess. From where I stand anyone who wants to hear all of the problems with EN version 5 has to be as described in the bleeped word.
  4. Man, you must be one serious *****. Here goes: On my MacBook Pro OS 10.6.8 I am experiencing the following serious issues with 5.0.4 FIRST - Since I upgraded to 5.0.4 Evernote syncs when I open the program and shut it down, even though my preferences are set to syncing manually. Not only does this waste time (on my satellite broadband connection - I'm in a remote area) it takes around 90 seconds to sync an empty sync file on my desktop with an empty sync file on the web. My concern is not mainly the lost time - for security reasons I simply don't want any program to be "cloud syncing" unnecessarily. This behaviour, combined with the second issue below is a significant security risk. SECOND - Since I upgraded to 5.0.4 EN has been writing to and getting data from my Keychain without first getting permission. This represents a major breach of one of the key security features of the Mac OS - nothing should change files on a Mac without first getting admin user permission. This did not happen before. EN support staff confirmed today that this is a bug. THIRD - The interface sucks. FOURTH - And maybe this isn't peculiar to Ver 5.0.4 - I don't know because I've never needed to use .enex archive files to reinstate the database before, despite backing up regularly using the Export function. In attempting to overcome some issues with the note share/email function EN support said that they had found "some issues" with my datbase and recommended a procedure dealing with this. Since I currenly have a whole raft of support tickets on the go with EN (since 5.0.4 update). I carefully followed their advice on exporting all my notebooks as .enex files, getting rid of the user/library/ Application Support/Evernote/accounts/Evernote/ folder and restarting Evernote as a clean (empty) version, synching with the web version (empty because I use only non-synch notebooks) and then reimporting the .enex files. First thing I learned on importing the .enex files of the Stacks was that when you export a stack, you export only the notes from the stack, but without the underlying notebook structure. Inconvenient, but can be overcome with an hour or two of work to reconstitute the structure that I had established for the data from several projects as well as from my business and my investment/tax management. Second thing I learned was that in 5.0.4 (latestMac version) when you bring up the export screen it has the "Include tags for each note" box ticked as the default. Very reassuring. But apparently what it means, to judge from the results I achieved, is that it exports the tags to the tag list of the new datbase, but none of them is associated with any note. All notes are bare of tags. So now I have roughly 2500 notes, across 18 databases for the aforesaid projects, business, investments and tax with not a single tag. Pretty near to useless in most instances. I certainly don't have the time to got through and try to re-tag (many with multiple tags) all the notes. This is a deal breaker so far as I am concerned. I can probably/possibly recover an earlier version of the EN database from Time Machine (If I can identify all the files that need to be restored), but no way I am going to take the risk of having this (or worse) happen again with another EN update. So, what I need to do is to recover the earlier data from Time Machine, put it into a pre-Version 5 of Evernote, and then export it into a more trustworthy but more complex database Devonthink Pro Office (I know that getting data out of Evernote is not easy, but it now has to be done).
  5. I'd seriously caution anyone EN 5.0.4 about backing up EN data into its .enex archive file format. I've been happily backing up my notebooks into .enex archives since I started using EN (as well as running Time Machine). In the course of trying to solve a problem with share/emailing EN notes, EN support told me that they'd - found "some issues" with my datbase when looking at the activity logs I sent them. So I followed their advice to export all my notebooks as .enex files, getting rid of the user/library/ Application Support/Evernote/accounts/Evernote/ folder and restarting Evernote as a clean (empty) version, and then reimporting the .enex files First thing I learned on importing the .enex files of the Stacks was that when you export a stack, you export only the notes from the stack, but without the underlying notebook structure. Inconvenient, but can be overcome with an hour or more of work to reconstitute the structure that I had established for data from several projects as well as from my business and my investment/tax management. Second thing I learned was that in 5.0.4 (latest Mac version), when you bring up the export screen it has the "Include tags for each note" box ticked as the default. Very reassuring. But apparently what it means, to judge from the results I achieved, is that it exports the tags to the tag list of the new datbase, but none of them is associated with any note. All notes are bare of tags. So now I have roughly 2500 notes, across 18 databases for the aforesaid projects, business, investments and tax with not a single tag. Pretty near to useless in most instances. This is a deal breaker so far as I am concerned. I can probably/possibly recover an earlier version of the EN database from Time Machine (If I can identify all the files that need to be restored), but no way I am going to take the risk of having this (or worse) happen again with another EN update.
  6. I'd really think twice about taking any advice from EN Support. I just followed their advice on exporting all my notebooks as .enex files, getting rid of the user/library/ Application Support/Evernote/accounts/Evernote/ folder and restarting Evernote as a clean (empty) version, and then reimporting the .enex files - in order to overcome what they said were "some issues" with my datbase. First thing I learned on importing the .enex files of the Stacks was that when you export a stack, you export only the notes from the stack, but without the underlying notebook structure. Inconvenient, but can be overcome with an hour or more of work to reconstitute the structure that I had established for data from several projects as well as from my business and my investment/tax management. Second thing I learned was that in 5.0.4 (latestMac version) when you bring up the export screen it has the "Include tags for each note" box ticked as the default. Very reassuring. But apparently what it means, to judge from the results I achieved is that it exports the tags to the tag list of the new datbase, but none of them is associated with any note. All notes are bare of tags. So now I have roughly 2500 notes, across 18 databases for the aforesaid projects, business, investments and tax with not a single tag. Pretty near to useless in most instances. This is a deal breaker so far as I am concerned. I can probably/possibly recover an earlier version of the EN database from Time Machine (If I can identify all the files that need to be restored), but no way I am going to take the risk of having this (or worse) happen again with another EN update. This is on top of the fact that the 5.0.4 Mac version allows the program to access the Keychain file and insert and extract data without seeking permission. This violates one of the significant security issues in the Mac OS.
×
×
  • Create New...