A couple of my members suddenly had trouble accessing a couple of topics in our forums getting a “permission denied” message. I checked all permissions etc an nothing was amiss. We finally figured out that the two people affected had both put a certain user on their Adversaries list.
Is there something about the Adversaries feature that could somehow mess up permissions access to a topic?
Check Profile > Buddies and Adversaries > Manage Adversaries > Hide posts from my adversaries.
Do that have that turned on?
I believe they said they blocked both posts and PMs from this person.
I just checked to see what topics the blocked person has posted to and sure enough the two topics the blocked person has posted to are the only ones my members are having problems with.
So the question is, why is this denying them access to the entire topic rather than just “hiding” the user’s specific posts … it’s not the behavior one would expect from such a feature.
Yes sorry – I missed that didn’t I? You said the whole topic not just those posts.
I do not see any connection why this should effect topic level. Are you saying that the topics in question contained posts by these blocked users? Or is that actually nothing to do with it?
2 members blocked one poster (both PMs & posts)
2 members can now no longer access 2 topic in the forums (and only those two topics), they get “permission denied” error
blocked poster has only posted in those two same topics.
So it appears rather than the user’s POSTS being not-visible to our two members, any topic the blocked poster has posted to are being not-visible (ie, access denied!)
I can not replicate on a quick test.
But – question. The 2 topics effected…. do these ONLY have posts by the adversary? In other words if this topic were loading would the users see any posts by anyone else?
Odd. Then no – I am unable to replicate and think that this is most unlikely. But I will have a talk with Steve later today when he is around to see if he has any ideas.
I don’t know what more info to give you other than obviously there’s a connection (too much of a coincidence not to be!)
understand. but like wise, this is the only report of such behaviour and we cannot duplicate it on our test sites. so path forward is difficult. About only choice left would be to debug on the actual server…