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

Following Management: after reload, subscriptions move to top of 'date followed' list when delivery settings only have been modified #140

Closed
bluefuton opened this issue Nov 18, 2015 · 2 comments
Labels
[Feature] Reader The reader site on Calypso. [Pri] Normal Schedule for the next available opportuinity. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@bluefuton
Copy link
Contributor

The API currently bumps the follow date on any modification to a subscription. This means that existing feeds find their way to the top of the list after you've changed email delivery settings, if you're sorting by 'Date followed'.

We should only change the subscription date on follow.

Reported by @ryanboren.

@bluefuton bluefuton added [Pri] Normal Schedule for the next available opportuinity. [Feature] Reader The reader site on Calypso. labels Nov 18, 2015
@lancewillett lancewillett added the [Type] Bug When a feature is broken and / or not performing as intended label Nov 25, 2015
@alisterscott
Copy link
Contributor

alisterscott commented May 11, 2017

Bug scrub 11 May 2017 - confirmed this is still an issue - changing email delivery option moved the item to the top of the list when sorting "By Date"

Could we just change "By Date" to "By Date Modified"?

@alisterscott
Copy link
Contributor

I can confirm this was fixed by a recent API change. Thanks @blowery !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Reader The reader site on Calypso. [Pri] Normal Schedule for the next available opportuinity. [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

No branches or pull requests

4 participants