AAM blocks post-listing on the front-end

Hi schwarzgrau,
Please check this tutorial: https://whimba.org/forum/viewtopic.php?f=6&t=8

Regards,
Vasyl

Wow, I never got such a fast reply here on the forum. Thank you Vasyl.
For me only this url works, but I guess it’s the right tutorial.

Even if I set the Capabilities of _Visitor to Admin, I can only see some posts.

Weeeell.
First of all capabilities has nothing to do with visitor. That is why any changes to capabilities have no effect. What I’m suggesting is to select Current Role _Visitor and click restore default button (arrow next to save button).
Try this and let me know the result

Regards,
Vasyl

Good to know.

Unfortunately nothing changed, after restoring the default-settings for visitors.
I dumped the posts which gets displayed, with the ones which doesn’t get displayed and can’t find the difference.
But if I dump a post logged-in and logged-out there is a difference:
In some posts the meta-key ‘connected’, which is created by posts2posts to store the connected posts, is empty.
Unfortunately I can’t find a pattern in it.

I tried to create a connection with AAM activated and another one with AAM deactivated, but both connections are invisible if I activate AAM.
It seems like there is some general incompatibility between Advanced Access Manager and Posts2Posts. Unfortunately there is no alternative to Posts2Posts.

Finally I found the problem:
AAM seems to block connections from Posts2Posts if you use meta_keys to order them. I still don’t know why, but maybe useful for everyone, who struggles with the same problem.