Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tt-rss] Items are not marked as read if no new items are available #84

Open
jochenberger opened this issue Sep 18, 2014 · 3 comments
Open

Comments

@jochenberger
Copy link

When there are unread items on the server and on the phone, then all unread items are marked as read on the server and then, the items are synced from the phone, the items are not marked as read on the phone. If, however, there are new items available on the server, they are fetched and the old (read) items are correctly marked as read. I guess there is some kind of early return; if there are no new items on the server.

@noinnion
Copy link
Owner

noinnion commented Oct 2, 2014

i could not follow you. could you explain it again.
Have you install tt_newsplus plugin on your server?

Could you try the latest beta v1.1.5?
http://noinnion.com/newsplus/updates

On Thu, Sep 18, 2014 at 6:44 PM, jochenberger [email protected]
wrote:

When there are unread items on the server and on the phone, then all
unread items are marked as read on the server and then, the items are
synced from the phone, the items are not marked as read on the phone. If,
however, there are new items available on the server, they are fetched and
the old (read) items are correctly marked as read. I guess there is some
kind of early return; if there are no new items on the server.


Reply to this email directly or view it on GitHub
#84.

@jochenberger
Copy link
Author

Have you install tt_newsplus plugin on your server?

Yes. I'll try to explain again.
Imagine there is 1 unread item (let's call it A) in tt-rss and that is synced to News+ correctly, so News+ shows A as unread too.
Then, I read the item A in tt-rss, so there are no unread items left. Then, I start the sync in News+ again. A is not marked as read in News+.
If, however, a new item B arrives in tt-rss (so there is a new unread item again) and I start the sync in News+, B is fetched and A is marked as unread, leaving only B as unread.

@Alkarex
Copy link

Alkarex commented Oct 3, 2014

I reported the same bug https://groups.google.com/forum/#!msg/news_plus/8c-5zWAkRW8/FpSka8Q3BUkJ in March. There is indeed the same bug with the Google Reader API, which we use in FreshRSS.
I can confirm that the bug is still present with version 1.1.5 of News+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants