Blog posts macro ordering incorrectly

[Kathryn Reddie]

My Comms team has raised an issue whereby the blog posts macro is not ordering the blogs according to the macro when they are all published on the same date.  It seems to be a time issue from what I can see. 

Our blog posts macro is set up for :

1. Max number of 4 blogs.
2. Sort by Creation.
3. Reverse sort.

Here's our scenario:

Blog post 1 published 24/04 12:30 > v2 12:43 > v3 26/04 17:16
Blog post 2 published 24/04 14:56 > v2 14:58 > v3 14:59 > v4 15:00 > v5 15:07
Blog post 3 published 24/04 15:45 > v2 16:09

5pm 24/04 they displayed in order 1, 3, 2.  I would have expected, with a reverse sort on creation date they would have displayed as 3, 2, 1.

A few days later, they display in order 3, 1, 2.

My thinking is ...

1. If I go by creation date, they should display 3, 2, 1 as reverse sort by creation date.
2. If I go by modified date, they should display 1, 3, 2 as reverse sort by modification date.  I think.

Whichever way I go, the macro isn't displaying as I would expect it to.

Does anyone else have a better understanding of what is going on here, or if it is a bug?

Thanks in advance,
Kathryn.

[Sven Schatter _Lively Apps_ · Accepted solution]

Hi @Kathryn Reddie,

I'm one of the developers of the Lively Blogs for Confluence app and I have seen this problem in the past in our app as well. Some of our customers reported that the sorting of blog posts only accounted for the day of the blog post, but not the hour & minute. This was because we were using the Confluence sorting algorithm.

We fixed this for our blog post overviews & macros by sorting the blog posts ourselves instead of using the Confluence algorithm. Unfortunately, there seem to be several old bug tickets for Confluence describing similar issues, some of them closed as "Won't fix".

Hope this helps!

Cheers,
Sven

[Jeremy Swan]

I'd suggest changing the date as a workaround, except you can't change the publish date after creating the post! That's been a known issue for over a decade: https://jira.atlassian.com/browse/CONFSERVER-11740

[Jeremy Swan]

We were having this issue too (which brought me here). I rebuilt the search index and it seems to have fixed the issue: <baseurl>/confluence/admin/search-indexes.action