PinkElephant

Each one has it's own approach - this said before saying other things. A technical issue first: The EN database is build in a way that enforces each note to be in one and only one notebook. To change this would mean to rewrite the whole thing, set up a new server structure, migrate all user databases (local and central) etc. Tags are already set up in the way you find it, with complete flexibility. So if you feel you must create a deep, treetype notebook structure and file away into this, you should probably move somewhere else. Now why this is not necessary, if you look a little bit deeper into ways to organize information: Notebooks in EN have very limited logical function. They are more like a large container than a filigreed filing structure. They are used to control things like being shared, being local, being offline etc. And you can control search easily, by first selecting a notebook and then entering a search string, or search for a tag in the selected notebook only. Tags are used to make searching easier, and to give a logical structure. This structure is not tree-type, it is a net. If you search for "2018", you will find everything tagged 2018 If you search "invoices", you will find all docs tagged invoices If you search for both, you will find all invoices from 2018. If you want to search for all invoices from 2015 to 2018 containing the ZIP-Code 12345, it is easy to do this as well (ZIP as text search) If you set up a tree structure (nested folders / notebooks), one of the 2 initial searches above is easy, the other is not. The combined search maybe is easy, for example if you file 1st "Invoices", and below this "Years". It is hard if your tree is "Invoices" - "Suppliers by Name", or other. With tags, it is always easy. And you can search for initially unrelated tags as well, the search will create the relation. Tagging is an effort if you have a lot of notebooks. First you have to think about the right notebook, then about the tags. It is no effort if you have few notebooks, and do the main filing work by tagging. Tagging is easy, because you do not have to decide about "Putting it here, putting it there" - just apply all tag wanted, and be done. And tags make it easy to avoid duplicates, because you do not need duplicates. Adding a new tag creates a duplicate by logic, while still needing just one note. Probably you do not want to make the step, because you have invested a lot into your notebook structure. I have been there some time ago as well. Then I realized that this is not the best way to set it up, it was just like that because I came from the traditional folder-tree Windows forces on us. In fact it is pretty easy to reorganize: Use one of the desktop clients (Win or Mac). First select all notes in one notebook, and mass-apply the notebook-name as a tag. Or apply 2 or more tags, that combined make up the notebook name. Then move all the notes into the new "container-type" notebook. Even with a lot of notebooks and notes, this can be done with little time spend to reorganize. You will find everything you had in the notebooks structure now in the tag list. The tags can be nested (however it will not show on the mobile clients yet, EN is working on this). This is the way I would set it up, and have done so for my data. Do what you think is right for you, but do not expect software that was designed differently to follow this. As I say - maybe switch to another tool.

For me, it is still GoodNotes 5. The notes stay in there as long as they are „work in progress“, export to EN when closed and of future use. GN5 has a strong handwriting recognition and offers a search function (if needed) in all notebooks for text. Text can be selected and converted into computer text as well, which works incredibly well with my ***** handwriting. The pdfs exported into EN are fully searchable as well (if this feature is enabled on export), the handwritten text will be found. Just takes 2 steps on my iPad , first search the note with the pdf, open it, then search for the text inside of the pdf. The handwritten match(es) found will be highlighted. One-time-purchase, good support, new features added permanently. Syncs only into iCloud, this works well over i-devices. Backups can be done to other Cloud-Services as well.

Go into the EN app. Click on account (the little man at the bottom, far right) Click on settings Activate Passcode-Lock (between Reminders and Evernote E-Mail adress, 3rd Positionen from the bottom of the list), you have to enter a passcode. When you did this, on the following screen you can select touch or Face ID. DTLow has posted this screen above. P.S. Moderators action: Moved from voting into iOS general - makes no sense to vote for something that exists.

If you are happy with Nimbus, you did the right thing for yourself. The organisation concept of EN is to build the logical structure of the notes with tags. The result is not a tree, but a net, which is way more flexible, linking notes of all types together, with multiple links. Finding information is driven by search. But a I say: If you want to create a one-way, tree type structure in which you force your information, go to another place (or create it by nested tags in EN, which is easily possible- but does not unlock the real power behind tags).

@djjason P.S. If you read through this „useless“ forum, you can easily find out that there is a EN beta program as well. The current reports about the betas show that the new EN iOS beta works with the new iOS 13 public beta. Combining an official release app like EN with a public beta like iOS 13 may lead to a crash. However, if you need your device for something relevant, you should stick with official releases on both ends. There are reports that iOS 13-beta has led to data loss on non-beta-loaded i-devices through iCloud ... (has nothing to do with the EN beta).

For engineers: This forum is user driven EN staff may read, and in rare cases will answer Direct support is restricted to paying users, non paying users may find answers here, or may try contact here https://twitter.com/evernotehelps Just an engineer as well, so we know that what the hell we know ...

Good for you. If formatting is high on your agenda, it is wise to pick a tool that is better suited for this. IMHO there is nothing like good or bad software, there is only good or bad matches between your demands / use case and the tools you pick.

Could it be that the scans that were not saved happened when you had already reached your monthly upload limit ? This can easily happen with scans, especially when saved as pictures. When I use my scanning app, it is set to create pdfs.

The EN editor is basic, and sensitive to formatting that comes with text and other stuff copied into it. My "solution": Do not try to get a nice formatting done, take it as it is, use basic formatting only. Copy as text, whenever possible. If you want a nice layout, take the information to another program. P.S. Getting the editor improved and unified over devices is a top priority of EN for this year.

Same procedure as every year, Ms Sophie ? Yes, James, same procedure as every year ! (This joke is for German readers only ...)

You are right, and I want to add something for clarity: Nesting tags is far superior to nested folders, that we all know from OSes like Windows or MacOS. A document can belong into just one folder, one folder into just one other, etc. This means that all organization must be done tree-type, and the only movement is up and down, following the branches. If a document has several uses, one starts to create help-structures or else. Nothing really works, or you end up with a lot of duplicates. One example: Some invoices may be tax deductible, other not, some invoices (but not the same as the tax stuff) will be needed when claiming warranty, others not etc. With folders, you have to decide whether you build a "tax" tree, or a "warranty tree", but no matter how, the other aspect will be missing. With tags, you can create both structures side by side. If you need to find all tax related stuff for 2018, you just search for "tax" AND "2018", and it will find among others all the relevant invoices. Same with searching for warranty, here maybe by direct search for the device plus the tag "warranty" or "invoice" (to exclude all the other notes with user manual etc.). There is always just one note somewhere in its notebook, but with tags, the approach is more like a net, not a tree. Access is possible from many entry points. This is why IMHO nesting tags is important, and nesting notebooks is not. If the tag nesting feature would be available on all clients, I would probably change my tagging strategy from a 2-level-nesting to a multi-level nesting. Because it means re-tagging, this can be done step by step, never loosing the searchability of all notes. You can apply the new tags side by side to the existing ones, and when you are completely done, you just delete the old tags. This step-by-step method is another pro for tags - when you change a folder structure, you have to do it in one go, for not to create a complete chaos.

Thanks for posting. Relevant for me, due to the German ä/ö/ü.

I agree that it is not good practice to overwrite local data. When I read your posting correctly, it was not done as long as the system was running unchanged. Just when updating, things went wrong. This is why I assume that during update, something happened to the data base, being synced or not. One reason can be that the update did not only include program code, but maybe a change of the data structure as well. Then the database must be updated, because the new program will not run on an old database. This is just wild guessing, but could explain why the database was set back to the server version during updating. In general and away from this issue: Think about creating regular, frequent backups. There are many things that can go wrong, and data that exists only on one device is easily wiped out by desaster or accident or malfunction. There is inexpensive or even free software to do the job, or you go to a cloud based service that needs an internet connection, but will not need an external drive. From what I know, currently Backblaze is probably the best service in a price-Performance ratio, because they sell a full, permanent backup of 1 computer (no Storage size limit !) to cloud server for 5$ a month. This includes versioning, so you can even go back in time if the last version created won’t do. 1st rule you learn in any IT-course: No backup, no mercy.

1st yes, this may be a reason, and if it is back to work now, it likely was the reason. 2nd if not, you should be clearer on which OS and client you try to do this. Like it is described here, many relevant details are missing.

Not very likely to have a bug not fixed, but no new posting between 2017 and today. How were the pictures created, how were they stored, how were they loaded into EN locally, did the sync go through without an error message ? If they are not visible on the server via web client, they are simply not there. The question is: Why ? Because maybe the activity log must be analyzed to find out, you should think about issuing a support ticket.

Looks like .... It is unlikely somebody from EN will drive by and read this, because this is a user forum, and Skitch is currently not in the focus of anybody.

Please do not mix handwriting and markup. These are two completely different capabilities. Both are requested, but for different use cases. For handwriting, there is Penultimate (which is not what I would propose). For markup editing, there is no internal solution, just external editors.

No experience with this special issue. Just had other problems with the client installed from the App Store. Uninstalled (completely, using AppCleaner !) and reinstalled the direct install app, Same version like from the App Store. My issues were fixed. I then learned that the App Store software runs in a sandbox, which can cause problems. The same software, direct install is not restricted.

Not fixed, not fixed, annoyed, angry etc. I am missing one thing in all of the postings: Did anyone issue a support ticket on this ? And what was the result ?

I would first check if something proposed in 2013 is still relevant in 2019. The world has turned a lot since, and in IT-related issues 6 years count a lot. I doubt anyone would build something static like the sample note shared in the first post. One thing is remarkable: The note shared in 2013 is still there in 2019, displaying just fine. It seems EN is made for eternity.

If anybody wants this to count, we need a counter. Moved to the voting section !

No similar experience. I just had a share not working a while ago due to the mailserver of the recipients company IT. Are maybe some black- / whitelistings or firewalls in between ? The share mail will not even make it to the spam filter if rejected before.

Works on both desktop clients, in the respective way how you do multiple selections in the given OS. EN does not deviate from the „usual way to do things“ in either client. But as the saying goes, being on Windows is like being on a dived submarine: You open the first window, and immediately the problems start. Just made it to my first Mac after 25+ years using Windows ...

The red underline is caused by spell checking. This is not an EN feature, it is borrowed from iOS. If you want to get rid of it, you have to go to iOS settings, choose „General“, and „Keyboard“. Spellchecking is one of the options. I think the word is not simply erased. iOS will offer alternative words for those detected as spelled incorrectly. It will mark the word to be replaced. If you hit something like return or space now, it will delete the marked word without replacing it. Maybe this leads to the impression of erasing. I have spellchecking activated, and do not experience any unintended erasing of words on my iPad Pro.

In the notes metadata (that you can look up through the note information) this information is available, and both searchable and usable for sorting of notes. I am not sure about this, but I think external programs like Mac Scripts or Filterize should be able to read this out and insert it in an automated process into the notes text.