get_adjacent_post() doesn't find private posts

[scribu]

The status is always 'publish'.

[scribu]

You're a machine. :)

However, we don't want users without the 'read_private_posts' capability in on these posts.

Another reason why I think we should creatively leverage WP_Query.

Related: #17807

[SergeyBiryukov]

Replying to scribu:

However, we don't want users without the 'read_private_posts' capability in on these posts.

Right, totally missed that.

[SergeyBiryukov]

I'll look into using WP_Query in #17807.

Meanwhile, 18613.2.patch​ uses get_private_posts_cap_sql().

[weirdrubikscube]

Hi Sergey,

the second patch did fix my issue with previous_post_link & next_post_link when the posts were private

but now I got this error constantly :

Warning: Cannot modify header information - headers already sent by (output started at link-template.php:2) in pluggable.php on line 897

when updating a post (thought the post would be successfully updated) or when entering a wrong url (no 404 page coming up)
and also when I try to simply log to wp-admin

so I had to put back my old link-template.php

I'm using WordPress 3.1.4 (cannot update as client host doesn't have php5)

[wonderboymusic]

Patch blows up

[DrewAPicture]

Would someone care to refresh the patch here?

[tw2113]

I vote that we close this one as handled. From the looks of things, private posts were begun to be included as of the commit and ticket below for WordPress 4.2.

Originally SVN Changeset and ticket:
https://core.trac.wordpress.org/changeset/31302
https://core.trac.wordpress.org/ticket/30287