Skip to:
Content
Pages
Categories
Search
Top
Bottom

Members page leads to 404 (not for administrators)


  • gheebuttersnaps
    Participant

    @gheebuttersnaps

    Hey there,
    I have an issue with buddypress on my WordPress site. I have installed the latest stable version of buddypress and registered the members component with the respective page.

    Whenever a user who is not administrator tries to access the members page, a 404 is shown. The same applies to everything beneath this page, such as editing profile. For administrators , everything is fine. I have tried to track the problem down. I have flushed the permalinks, disabled all plugins. When I switched to the default theme, everything works fine as expected. So, I suspect the issue has to be with my theme, enfold.

    I fiddled with the capabilites and found that if I add the “edit others pages” capability to a user he is able to access the members page. But this has undesired consequences such as the ability to create drafts for pages and accessing the theme options (why in the world?).

    Anyway as this is most likely a theme specific problem, I would like to ask if there are any experiences with such a matter or hints what I could look out for.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

  • Varun Dubey
    Participant

    @vapvarun

    @gheebuttersnaps Enfold does not have official support for BuddyPress, they have also mentioned it at their site.
    Inside their support thread

    BuddyPress is not officially compatible, therefore there might be some issues. We will ask our devs for BuddyPress compatibility.

    It will need theme specific testing to add any comment on it.


    gheebuttersnaps
    Participant

    @gheebuttersnaps

    Thanks for your reply. I thought it might be worth a shot as someone might have experienced the same issue.

    In the meantime I found a workaround for the situation. I added the “edit pages” capability to our user role and use a second plug in which prevents dashboard access.


    gheebuttersnaps
    Participant

    @gheebuttersnaps

    Just to let everybody know: I found the cause for my problem. I had to add the capability ‘view private pages’ to the role and now everything works as expected.


    Varun Dubey
    Participant

    @vapvarun

    Glad you figure it out.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.
Skip to toolbar