CPT Sticky Posts in Masonry

Hi Ismael,

I’ve already had it in this way before too. But for both queries, the sorting is incorrect. The ACF date field posts are first, but then sorted in the wrong order (they should be ascending), and the other posts are correctly after that first query, but also sorted in the wrong order (they should be descending).

It should be:
• 31.1.26 Test (with ACF date)
• 2.2.26 Test2 (with ACF date)
• And after those the posts without ACF date sorted desc by publication date (in the example “Minispielkreis” should be the latest post in the list in the frontend)

Can you change the order for each query and keep the queries in place like now (first ACF and the posts without afterwards)?

All the best,
Daniel

Hi Ismael,
That’s not the answer I was hoping for. Too bad. If I use two Masonry elements, I no longer have the option of outputting and filtering them as a single unit. So that’s not a solution.

But it should be possible to sort the posts with the ACF fields in ascending order first and then have all the other posts come after them, in whatever order. Until now, the ACF posts have always been at the end when they were sorted correctly. What I mean is:

• 31.1.26 Test (with ACF date)
• 2.2.26 Test2 (with ACF date)
• And after those the posts without ACF date sorted in whatever reason

You know what I mean?

Kind regards,
Daniel

So the query always has the posts with ACF in front, but the wrong way around, or in the very end?