{"action":"closed","issue":{"url":"https://api.github.com/repos/OrchardCMS/OrchardTest/issues/1588","labels_url":"https://api.github.com/repos/OrchardCMS/OrchardTest/issues/1588/labels{/name}","comments_url":"https://api.github.com/repos/OrchardCMS/OrchardTest/issues/1588/comments","events_url":"https://api.github.com/repos/OrchardCMS/OrchardTest/issues/1588/events","html_url":"https://github.com/OrchardCMS/OrchardTest/issues/1588","id":67820089,"number":1588,"title":" Default content sort on summary pages","user":{"login":"orchardbot","id":11788683,"avatar_url":"https://avatars.githubusercontent.com/u/11788683?v=3","gravatar_id":"","url":"https://api.github.com/users/orchardbot","html_url":"https://github.com/orchardbot","followers_url":"https://api.github.com/users/orchardbot/followers","following_url":"https://api.github.com/users/orchardbot/following{/other_user}","gists_url":"https://api.github.com/users/orchardbot/gists{/gist_id}","starred_url":"https://api.github.com/users/orchardbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orchardbot/subscriptions","organizations_url":"https://api.github.com/users/orchardbot/orgs","repos_url":"https://api.github.com/users/orchardbot/repos","events_url":"https://api.github.com/users/orchardbot/events{/privacy}","received_events_url":"https://api.github.com/users/orchardbot/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/OrchardCMS/OrchardTest/milestones/26","html_url":"https://github.com/OrchardCMS/OrchardTest/milestones/Orchard%20Future%20Versions","labels_url":"https://api.github.com/repos/OrchardCMS/OrchardTest/milestones/26/labels","id":1062871,"number":26,"title":"Orchard Future Versions","description":"A bucket for postponed items","creator":{"login":"orchardbot","id":11788683,"avatar_url":"https://avatars.githubusercontent.com/u/11788683?v=3","gravatar_id":"","url":"https://api.github.com/users/orchardbot","html_url":"https://github.com/orchardbot","followers_url":"https://api.github.com/users/orchardbot/followers","following_url":"https://api.github.com/users/orchardbot/following{/other_user}","gists_url":"https://api.github.com/users/orchardbot/gists{/gist_id}","starred_url":"https://api.github.com/users/orchardbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orchardbot/subscriptions","organizations_url":"https://api.github.com/users/orchardbot/orgs","repos_url":"https://api.github.com/users/orchardbot/repos","events_url":"https://api.github.com/users/orchardbot/events{/privacy}","received_events_url":"https://api.github.com/users/orchardbot/received_events","type":"User","site_admin":false},"open_issues":235,"closed_issues":93,"state":"open","created_at":"2015-04-11T05:02:18Z","updated_at":"2015-04-11T18:55:37Z","due_on":null,"closed_at":null},"comments":2,"created_at":"2011-04-20T16:05:51Z","updated_at":"2015-04-11T18:55:37Z","closed_at":"2015-04-11T18:55:37Z","body":"__zappan__ created:\r\nhttps://orchard.codeplex.com/workitem/17758\r\n\r\nFrom a discussion at http://orchard.codeplex.com/discussions/254652\r\n\r\nThe default sort order in Orchard seems to be by creation date, instead of publish date for the content summary pages.\r\n\r\nIt can lead to a situation, when having multiple drafts which get published in an order different than they were created, that they're ordered wrong on the blog homepage (and other summary pages).  I'd propose ordering by publish date DESC on blog summary, summary by tags, and other summary listing views, because the newest content is the most interesting to readers in the most use cases (blog, media).\r\n\r\nThe awkward situation from my blog documented in the attached screenshot (see post dates left of the post title)\r\n\r\n\r\nNOTE: As noted in the discussion linked above, the current logic is reasoned by when already published post is edited to correct a typo, or type in a small add-on, it needs to be republished to be visible on the frontend, and ordering by publish date DESC would then reorder that post as the newest. \r\n\r\nThere might be a solution to that when post is one published, 'Save' button would apply changes automatically to the public, no need to republish it. That would keep the original publish date. The other solution is that the Publish button doesn't change the date if content is in 'published' state, to change the date, one would need to unpublish then republish the content (blog post)."}}