new articles not shown in sources sidebar or dashboard
Recently (a few weeks back, on and off), feedly started to behave strangely with respect to new items: sometimes, for some feeds, when there's a new article in it, the feed isn't marked as having unread stuff in it in the dashboard. Nor is it shown in the "SOURCES" sidebar (I have it configured to show feeds with new articles only).
The new articles are shown in Google Reader, on the "what's new?" page on the feed's page (which I have configured to show unread only; yet, the new article is shown there.).
I know this is awfully vague, but I'm unable to find anything logic behind which articles are detected as new and which aren't. Restarting Firefox usually helps, but not for long. This is quite annoying, because the "what's new?" page doesn't show everything (and in my case, is frequently full of news I don't want to read at the moment), so I use the SOURCES sidebar as primary navigation tool.
In case the following description wasn't clear, let me show you an example: right now, there's a new article at Groklaw, titled "Stipulation to Lift Stay on IPO Class Action and SCO's MORs Filed". I can see it in Google Reader. On the "what's new" page, it is shown as usual in the "News" category I put this feed into. But on the very same screen, the sources sidebar does not list Groklaw, even though it clearly should, because otherwise an article from it wouldn't be on the "what's new?" page in the first place! So I go to dashboard and there's the Groklaw feed listed as having no unread items again. I click on it and feedly's Groklaw feed page is shown and has this new article in "today" section -- as a new one (there's "mark as read"). But it doesn't have the round box with unread articles count next to feed's title that is used to mark all of the feed as read.
The new articles are shown in Google Reader, on the "what's new?" page on the feed's page (which I have configured to show unread only; yet, the new article is shown there.).
I know this is awfully vague, but I'm unable to find anything logic behind which articles are detected as new and which aren't. Restarting Firefox usually helps, but not for long. This is quite annoying, because the "what's new?" page doesn't show everything (and in my case, is frequently full of news I don't want to read at the moment), so I use the SOURCES sidebar as primary navigation tool.
In case the following description wasn't clear, let me show you an example: right now, there's a new article at Groklaw, titled "Stipulation to Lift Stay on IPO Class Action and SCO's MORs Filed". I can see it in Google Reader. On the "what's new" page, it is shown as usual in the "News" category I put this feed into. But on the very same screen, the sources sidebar does not list Groklaw, even though it clearly should, because otherwise an article from it wouldn't be on the "what's new?" page in the first place! So I go to dashboard and there's the Groklaw feed listed as having no unread items again. I click on it and feedly's Groklaw feed page is shown and has this new article in "today" section -- as a new one (there's "mark as read"). But it doesn't have the round box with unread articles count next to feed's title that is used to mark all of the feed as read.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
Update. Fixed in 1.2.38. You should get the fix automatically next time you start the browser. Please let us know if for some reason this does not work as advertised. Thank you very much for the heads up - this was a very interesting bug to find and fix and your detailed use case was *extremely* useful!!!
I’m thankful
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi vsl. sorry for the frustration. I will forward this use case to the team so that we can improve the usability. I have a couple of questions:
1) did you go to the feedly dashboard and click on the "favorite star" next to your favorite source? Doing that should help the filtering happing in the what's new and the layout on the sidebar.
2) how many sources do you subscribe to? How many favorites and how many non-favorites?
3) when you scroll at the bottom of the page, what is the version information you are seeing? It should look something like 1.2.XX
I will definitely come back to your when I have had the time to discuss this use case with the rest of the team.
Thanks
Edwin -
Inappropriate?Don't worry, it's not that frustrating. Still beats any other RSS reader I used by a wide margin ;-)
1) This particular example, Groklaw feed, is marked as favorite, so it should have appeared in "Favorites", not "Sources", my mistake. But it wasn't there either. I 've seem the bug happen with both starred and non-starred feeds.
2) At this time 154 feeds, 8 of them favorite. Ttwo of them are very high-traffic; some non-favorite are high traffic too and come to think of it, I couldn't keep up with them lately and have lots of unread items in there, ~1500 or so. Seeing that Reader reports unread count as "1000+", I'm beginning to suspect that this could indeed be the problem... Let me try to get it down to a sane number and see if the bug persists.
3) 1.2.37 (build 2022) (sorry, I assumed that everybody is on the same version with the auto-update in effect...) -
Inappropriate?Update: we did a review with the team. We think we have an idea of the bug which is causing the problem you are describing. It is not related to 1000+ (I have continuously more than 50,000 unread articles). We will try to push a fix out later this evening. We will update this post when the fix is out.
-
Inappropriate?Update. Fixed in 1.2.38. You should get the fix automatically next time you start the browser. Please let us know if for some reason this does not work as advertised. Thank you very much for the heads up - this was a very interesting bug to find and fix and your detailed use case was *extremely* useful!!!
I’m thankful
The company says
this solves the problem
-
Inappropriate?I still did see the bug using 1.2.38 (build 2026) today. (I now restarted FF and am at 1.2.39 (build 2028), but didn't run it long enough to know if it behaves differently.)
-
Inappropriate?Yes. Phil reported a similar set of problems this morning. We have made this the top priority for today. We will keep you posted.
1 person says
this solves the problem
Loading Profile...



EMPLOYEE