Kowalski78 0 Posted August 30, 2015 Share Posted August 30, 2015 Hello! As I've just written the web clipper extension started to duplicate every notebook, i.e. I got two notebooks with same content. If I delete manually evernote files in chrome folder it seems resolved but every time I restart chrome the issue appears again Can anyone help me? Thanks! Link to comment
jbignert 473 Posted August 31, 2015 Share Posted August 31, 2015 It's a bug in the Web Clipper. Please try in this order to:- Clear cache on your Chrome browser- Sign out from the Web Clipper / restart / sign back in to the Web Clipper. If that fails to fix it try uninstalling and then re-installing the Web Clipper. Link to comment
Kowalski78 0 Posted August 31, 2015 Author Share Posted August 31, 2015 Hello, thank you for your help, unfortunately the issue still remains... I cleaned the cash, uninstalled evernote web clipper, everything possible with that extension has been done but... nothing. Any hint? Thanks! Link to comment
Kowalski78 0 Posted September 3, 2015 Author Share Posted September 3, 2015 Ok, that's enough, I am going to unsuscribe my pro account. Link to comment
jbignert 473 Posted September 3, 2015 Share Posted September 3, 2015 If you have a few minutes to grab the Web Clipper error logs from the Web Clipper Options page and send them to me that would help us diagnose the issue. Link to comment
JEFFUK 0 Posted September 4, 2015 Share Posted September 4, 2015 Same just happened to me :-( Link to comment
Kowalski78 0 Posted September 8, 2015 Author Share Posted September 8, 2015 Hello, any news about my problem?! Link to comment
jbignert 473 Posted September 9, 2015 Share Posted September 9, 2015 Hi all,This is most likely a bug in Chrome 45 (stable channel) and 46 (beta channel). Here's the bug report on their side: https://code.google....etail?id=520303. According to the report, it is already fixed in Chrome 47 (canary channel) and will be available in 46 tomorrow (September 9). No word yet on when it will be available in 45. Unfortunately we cannot fix this client side so affected users will have to wait until Chrome pushes out an update. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.