Topic content not displayed – s2 + bbPress

Hello,

We are experiencing exactly the same issue as described here:

http://www.s2member.com/forums/topic/buddypress-bbpress-forum-post-does-not-appear/

All regular users (level 0) can create new posts and replies but cannot see the original topic content.
All replies are displayed properly.

As soon as the s2Member is disabled, everything is displayed properly.

Enabling/disabling the bbPress and s2Member plugins did not help.

s2Member log directly is empty.

Settings info:
– no URL restrictions
– no post type restrictions
– level 0 users have checked the “read” and “read private forums” capabilities

Site setup info:
– WordPress 3.4.1
– bbPress 2.1.2
– s2Member 120703 + s2Member Pro v120703
– no BuddyPress
– no content access plugins other than s2Member

Please come back to us as soon as possible as this is crucial for our community.

Thank you.

Aram

Hi Aram,

What settings are configured in Dashboard -› s2Member® -› Restriction Options -› Alternative View Protection?

Also, are there any restrictions in Dashboard -› s2Member® -› Restriction Options -› URI Access Restrictions?

Hi Raam,

Thank you for your response.

We found what caused this issue in the meantime.

One page ID on Restriction Options -> Page Access Restrictions did not exist anymore. The page was deleted from admin.
This caused unpredictable content access permissions, so users were not able to see the forum topics.
As soon as we removed that page ID, everything went back to normal.

The ID was in the “Pages that require highest level #4” field.

This is a bug/glitch in s2Member. You can solve it by implementing the delete_post or before_delete_post action and removing the page/post IDs automatically from the list of restricted pages.
Also there might be something wrong in the plugin logic which checks particular IDs – you can add an additional check to see if the page/post exists for sure and only then to continue.

As this possibly results in broken access permissions, the most appropriate is to address this issue in the next batch of updates. You have many paid customers who use your plugin for protecting private discussions and communities and they might not be even aware of this issue.

Let me know if you need any other details.

Regards,

Aram

• This reply was modified 4 years, 4 months ago by  Kevin Vaughn.
• This reply was modified 4 years, 4 months ago by  Kevin Vaughn.

Thanks for the update, Adam, and for reporting your findings. I’m forwarding it to Jason so he can take a look at this. :)

Thanks for the heads up on this thread,
and thanks for reporting this important issue.

So far I’ve been unable to reproduce this, but we’ll continue to look at this closely. Regarding the existence of a Post/Page, as it relates to s2Member’s Restrictions. s2Member is only comparing the current URL, Post ID, Page ID, etc, to the Restrictions, so if a Post/Page does not exist, it should not trip over any of s2Member’s settings.

Regarding the hooks for post deletion, we’ll certainly consider it. However, given the multi-layer restriction options provided by s2Member, deleting a specific Post/Page ID, may not cover all layers of protection, as this really needs to be handled by a site owner. For instance, protecting a URI, or a category/tag, or something that engages with a Replacement Code, can also have an impact on Restrictions, which is not easily detectable via a deletion hook which references a specific Post ID. In other words, it’s possible for Restrictions to exist on multiple layers, which may have a reaching impact upon a specific Post.

Question. When this issue affected your installation, did you have any of s2Member’s Alternative Views enabled? Please let me know what settings might have been enabled there, as it may help as we work to resolve this.

Please see: Dashboard -› s2Member® -› Restriction Options -› Alternative View Protection

Under “Alternative View Protection” the “Filter ALL WordPress queries” is checked.

The site does not use dynamic filter suppression.

Thanks Kevin. I emailed Jason letting him know what you replied. I’ll let you know as soon as I hear back from him, or he may just reply here directly.

Thanks Christian, I appreciate this…

Thank you for the reply!

I’m updating our diagnostic report on this, and we’ll continue our attempts to reproduce this. So far I’ve been unsuccessful, even with content filters applied, but we’ll do our best to continue the search.

Thank you Jason and thank you for your responsiveness. Best WP plugin developers I have worked with to date…

Thanks for the kudos, Kevin! :)