-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Purchases: Site order #165
Comments
I agree, with a little tweak: any site with a subscription in a special state (failed auto renewal, has expired, domain in grace period or redempion) should be pushed to the top. |
+1 |
I'm not sure about that one because it means that the order is no more consistent with the site picker but also with what users are used to on this |
I think that moving the site to the top if it is in a special case is probably a different issue, and probably needs some design thought - we might like to change the way it looks slightly to show that it's been bumped to the top for a reason. We can easily handle these in two different PRs. |
I opened an issue for bumping purchases in certain states to the top of the list: #4620 |
site.plugin: add basic site plugins structure
The order of the sites in /purchases is currently based on the purchase date of their respective purchases. It should use the same order as the site picker.
The text was updated successfully, but these errors were encountered: