FrankC

I have found that some documents which were OCR'd/Indexed by the legacy version are not fully OCR'd/Indexed by the latest version. This results in different search results between the two versions. I tracked this down by doing various searches and seeing what notes were returned by the same search on each version.
Doesn't make complete sense to me, as I would have thought both versions would be "looking" at the same index. The notes causing the discrepancy in my tests were not recent ones.

Support ticket raised recently, so am awaiting a response.

On 1/28/2021 at 9:31 PM, idoc said:

Not sure if I understand the logic of putting the "Notebook" selection on the top but the tag selection on the bottom. In Legacy Evernote when I adjudicate a note I usually assign tags to it and then select which notebook I want to put it in.  That has all happened on the top of the note where the tag and notebook features lie side by side.  In the new version they are separated by an entire page.  I literally have to select one thing on the top and then the next thing on the bottom.  Seems counterintuitive.  Am I the only person bothered by this?

Yes - reported even as far back as the beta version.

Same issue - I was prepared to live with the horrible (appearance-wise) widget. However, finding that images wouldn't display was a bit to much for me. I've reverted to the legacy Android version using the APK and turned off updates.

So, for now I'm sticking with legacy PC and Android versions for doing any work. I occasionally try v10 when a new release comes out - but it seems that every new release adds a bit of functionality, but introduces different bugs. Even in the latest release, merging notes still causes image loss.

I've activated the widgets for Android using v10.4.

However there doesn't appear to be any way to style the widget/action bar. I would be happy with the way it looked before. However, the the new version looks terrible and matches nothing else (green icons on a bright white background with almost unreadable grey text). Is there any way to change this ?

15 minutes ago, Mike P said:

OK very strange. I assume you are on 10.6.9. I'll keep on testing but so far it seems to be working much better for me.

Yes - 10.6.9 - On Win 10 PC

I'll see what support come up with. sent them some screenshots & logs.

4 minutes ago, Mike P said:

When did you test last? If it is some sort of sync issue and not a viewer issue then I suppose it is possible that could be corrected without an update to the Windows version.

This morning + again just before I replied here.

I also noticed that when I click on the "ENLARGE" button (under the missing image) it opens the original image in a new tab. However, this is actually a link to the image on the original website (which of course makes it useless for archive purposes, if the original site changes anything).

I've just now done another test with 2 web clips using "screenshot". Once again the images have disappeared. Of course, in this case, the full note is just an image - so nothing remains except the titles from the merged notes.

4 minutes ago, Mike P said:

Agreed. This is the behaviour I was seeing too. However, in all my testing described above it now only seems to be bookmarks that are not working. As I explained above I'm being cautious because I'm not convinced that they will not disappear in the future. So far so good and I have deliberately completely closed and reopened EN several times.

I used "Article" to clip in all my testing.

I have an open ticket related to this.

While producing some test examples, I discovered another apparent bug. If I merge two notes, then another two notes into two new notes, then these two new notes cannot be merged into a single note. It starts working, then I get an error message : "We were unable to merge all the items. Please retry"
 

The other funny think happening is that when I merge 2 notes, the images appear there initially. However, when I go back later, they're gone.
 

44 minutes ago, Mike P said:

Could you describe exactly how you are doing the webclipping. You are right this was reported way back in the preview stage but I thought it was now fixed. If I do a webclip of a page I get it in a webclip box as expected. I can't see any details of the images in the clip so I have no idea whether they have actually been copied or it is just a link. However, if I "simplify and make editable" the image has definitely been copied because I can edit it.

Copying and pasting from the web also works correctly. I get an editable image which was not the case in the past..

I am using the Web Clipper/Clip Article.

I've just tried it again, and am getting different (better !) results. 

This time it displays correctly in Android and the new version. I can't see any reason for the change in the new version, apart from the fact that some time has passed, and the image is now displayed ??? It could have been down to a delay in Evernote Update/Syncing.

The legacy version still just shows a link - but I now think this may be an internal (Evernote) link, rather than a link to the original source file. The image format is .webp, which I think the legacy Evernote can't display.  Here's a link example :

TELEMMGLPICT000249044382_trans_NvBQzQNjv4Bqe5jTtuvhyhg4PHi86V8a0uHC4uooAYptTLzL00kNATY.webp

If I try to right-click to copy the image, nothing happens. This is possibly  because the images isn't "in" the note, just a link to the image in the Evernote database (possibly an attachment ?). This could also be part of the reason why people are having problems with Copy/Paste of notes containing images.

Yes - same is happening to me.

Generally image handling is not working well. Some of the problems I'm having :

(1) As above, merging notes with images loses images in some notes.

(2) .webp images display on Android (latest version), but not in legacy (show a link in a box) or in v10.6.9 (show a broken link image)

(3) Webclipped pages (e.g. from newspapers) store links to the page images, not the actual images themselves. If the source article changes or is removed, then the images are gone. I think this was reported as far back as the Beta version. The only way I can see around this is to manually screenshot the images and paste them into the note. Not a viable,or acceptable, solution.

Following on from this update from Ian Small , I would love to see an AMA on Reddit - or here - with him.

Should help clarify some of the many outstanding issues, questions and suggestions many users have.

14 minutes ago, DTLow said:

It's working for me on my Apple Mac
No legacy option for Apple IOS

I'm not an Apple user - so just to clarify :

As I understand it, IOS is the mobile operating system, and Mac the desktop machine(s). So, if I understand you correctly you can't use the legacy option on phones, but can on any Mac desktop/laptop system ?

16 hours ago, DTLow said:

I consider the Version 10 product a work-in-progress; not ready for general use   
The Legacy product is working well for me.   
I'll review the Version 10 product when the work is completed

>>make your voice heard

Objective feedback is welcome.    
Sadly most of the posts are more "Boohoo, Evernote's so bad"; it clutters the feedback/issue forums

If it had been released as a Public Beta (or Alpha) all of that could have been avoided. Instead it was a "push" update. I'm on Windows - so continuing to use the legacy version. However Apple users don't have the same option.

On 10/28/2020 at 5:00 PM, DTLow said:

Would that include setting up a user discussion site
with forums for users to present issues and feedback/requests
and a voting system for users to indicate request support

Yes, that's one option. However an important part of that option is "engaging". That rarely (never ?) happens. 

35 minutes ago, Mike P said:

The structure of the two databases is completely different so you cannot have V10 and the legacy version using the same DB. Therefore as @PinkElephant said you will need the space on your HD for two databases.

Yes - but you have a choice where you store the Evernote Legacy database. It can be on any drive available to you. 

V10 seems to locate its database on the installation  drive (or C:), and without preferences you can't move it. 

So, if you're running both versions you can spread the usage across 2 drives, by moving the legacy system database. This is what I've done.

2 hours ago, PinkElephant said:

Your requests are reasonable, only nobody can tell when these issues will be solved.

I fI were you, I would go back to the legacy client and observe the releases to come. If you want some functions that come with v10, you can even install and run both, one for the current workflow, the other for functions yet not implemented. The downside is you double the local data base, so you need the space on your main drive to do it.

Actually, the legacy version still has preferences, so you can move the database to another drive, if you want to.

I've been an Evernote user back to the first beta in 2008 (user ~2400 - according to an email from Evernote).

Following the fiasco which is the latest release - I've been looking around for alternatives to Evernote - Nimbus and Notion being my current testing choices.

Funnily enough though, the best alternative I've found so far is Evernote Legacy. I cannot believe how the development and release process has been handled so badly for a mature product with millions of users. Relying on Evernote Legacy is not an option though - given there is absolutely no commitment to keeping it running - or no cut-off date specified.

Having participated in the v10 beta, my impression was that the opinions and suggestions from the beta testers were largely ignored. The only time significant attention was paid to us was when a feature didn't work as the Evernote team had already decided they wanted it. Then it would be actioned. Otherwise - crickets. Pushing out a 'live' release like this is just incomprehensible to me (having worked in SW development for 20+ years). At best, it could have been a public beta - but I don't even think it's ready for that yet.

So - I'm hanging on until my current subscription expires (or the legacy version stops working) and will re-evaluate then. However, based on what's happened recently, I don't have a lot of hope for improvement.