newsplus
newsplus copied to clipboard
noinnion
[tt-rss] Items are not marked as read if no new items are available
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.
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 https://github.com/noinnion/newsplus/issues/84.
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.
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+.
