Jump to content

PinkElephant

Level 5
  • Posts

    25,037
  • Joined

  • Last visited

  • Days Won

    483

Everything posted by PinkElephant

  1. It depends how long your „finally updated“ is ago. The app will build the local database during the first days, which causes it to run slower. Further the download may not yet be complete. You should keep the app running in the background, to allow it to complete organizing things. If you have a lot of bulleted lists, it may be this is slowing down things. Headers (that didn’t exist in legacy) and bulleted lists are collapsible now. It seems this causes an additional lag. Hope it will be optimized with the next releases.
  2. No idea about the yellow bar. If it only appears on the first page, it must be software driven. Here is the link to convert an edition scanner into a regular ix500. It is a one way update - there is no way back.
  3. If you are on Free, you can’t. There is only 1 notebook allowed. if you are on a subscription, you create the new notebook, make it the default, and the erase the first. Erasing a notebook will send all notes in it to the trash ! I don’t see a logic behind it - renaming the existing default notebook would probably be easier.
  4. Subscription and payment issues need to be sorted out by support: https://help.evernote.com/hc/en-us/requests/new
  5. Can’t tell about Chrome, I don’t use it. If nobody steps in here, contact support: https://help.evernote.com/hc/en-us/requests/new
  6. Probably you were selected (without asking …) for yet another blind test of a new feature. Usually about 10% are picked at random to test drive this stuff. Send your comment about it here feedback@evernote.com or here https://help.evernote.com/hc/en-us/requests/new
  7. @Razmataz Problem #1 is that with every new feature introduced for the modern client, the devs need to check backward compatibility. Not to introduce it into legacy, but to make sure there are no side effects. This is important for users who use legacy and v10 in parallel. Problem #2 is that the old API and database is exposed to the internet. You need to monitor and defend it, even when there are no changes. To reach these conclusions you just need to read the official blog post about it. Killing outdated software is the better approach than taking risks. It needs to be killed anyhow, there is no gain in waiting. Or what would be different in 3 months, 6 months or a year ? Just more money burned by operating a zombie. So let’s nail the coffin, and move on.
  8. You mean as the current team at EN ? You can’t mean any of the management team before, c‘on. You know, those who let the technology rot away, and believe the future is selling merch 🧦.
  9. @fuchsfr Sure the servers will migrate. Do you really expect a company that is looking ahead to stick with an outdated server infrastructure, after you request they stick with outdated server code and outdated clients ? Nice industrial museum you want them to keep. The old server software is called Monolith - that probably describes it all: Immutable, impossible to adapt or move ahead. You are really fun to listen to: You tell the obvious, and at the same time ask to stay stuck with the past because you are afraid of what’s ahead. Of course there is more to come once they got rid of the ballast ! Or did you really believe once they streamlined everything, these guys will lean back and take it easy ?
  10. The legacy clients are deprecated since 2020. This means no more changes, even if an OS update breaks things. This is the case on the Mac - legacy Mac is practically unusable since MacOS Ventura, released late 2022. Furthermore the EN team of old doesn’t exist any more. The US and chilenian offices are closed, the employees have left. There is a new team run from the new Italian HQ (but maybe located elsewhere, who knows). There is nobody left with the skill set to touch this outdated software. And be assured: It would not be worth a single dime spend on it. Legacy and it’s technical debt was what nearly killed the company, and finally led the owners to put it on the block. Stopping the legacy server infrastructure is done to cut down this technical debt, in terms of maintenance, data volume and operational cost. EN took the only possible solution in 2018, to start the transition to a future proof technology. They just missed to pull it through on the operations / economical side as well.
  11. First import by notebook. Second I would try it with a single notebook first. The full process, including the server sync. When it all goes well, you know what to expect. Third I would do it fast. There will be no server sync of a legacy client in 2 days, as far as we know. If you want them in a legacy client, that is. ENEX can be imported into v10 as well, without a limit. Then look at your ENEX files, and your monthly upload limit. These 10/20 GB is all you can import within 30 days. More will clog your server connection. Make a sequence how important it is to get stuff synced.
  12. V10 uses a different basic data structure than legacy. This means that as long as there are legacy clients syncing with the server, the server needs to service 2 interfaces and 2 sets of data. The old server code is difficult to maintain. Assuring backward compatibility for changes is even worse. The consequence is obvious and will now be implemented, by taking the old part of the server setup offline. If v10 works for you you need to find out yourself.
  13. Simply scroll down the selection field. The first 3 entries show, there is more below.
  14. So many words, instead of: Just go to the EN website any install the latest version. Yes, for the Mac …
  15. Support as guest: https://help.evernote.com/hc/en-us/requests/new?ticket_form_id=254668&guest=true&guest=true
  16. Very likely it is the expandable bullets. Many users wanted the expandable / collapsible sections ... it seems they come for a price. I disagree however about the size penalty. I just build a note by copying a longer wikipedia text as plain text into a note. Note information says it`s 186.451 characters and 199KB. That is practically no penalty at all, each character takes up a single byte. Probably there is another mechanism at work: EN keeps a note history for every note. Changes are kept there, which allows to go back to earlier versions. This will force the note to grow its overhead data, to store these changes. If a note is altered a lot, note history will probably become significant.
  17. We have had similar reports in the forum. My impression is as well that this function has stopped. To know for sure ask support.
  18. Tried the link, nope, doesn't work anymore. Hope this one does. https://www.evernote.com/shard/s747/sh/b4e456be-7dcb-4fa1-b278-9a2da95df384/164e2b2b0c458c7ba6f5572c0e056c4f
  19. If the import folder was unconnected by an update, it won’t import. This happened to me twice after a regular update. It was easy to notice (oppps, where is the new note I expected …?) and easy to fix: Just reestablish the import folder again in EN settings. In both cases reconnecting made the missing files import by themselves. When I save a file into an import folder, it is recognized and imported. No fail, works always. To prepare it first and then save it info the import folder has the advantage I can give it a „good“ file name. Since the file name will become the note title, it scraps rework in EN to create a good file name first.
  20. Every iOS device is able to take rolling screenshots - just BTW. On the Mac the menu bar app Shottr has this ability as well.
  21. Check in another browser. If it works there, go back to the first, log out (if you are still logged in) and log back in. Then check in the original browser if the problem persists. If you don't have the problem in the other browser, and it persists in the first one, you need to check your browser extensions and settings for interference. Why do I tell ? Because I tried in 2 different browsers (Safari, Firefox) and found no problem at all switching between views.
×
×
  • Create New...