[Plugin: BuddyPress] Conflict with permission

In what sense is this bug “wellknown”?

I have heard people report this issue before, but I have never heard anyone give enough details so that the developers could reproduce it.

WP version
BP version
Other BP plugins
Your theme
PHP version
Server type: shared vs VPS, etc

Are you able to reproduce the problem when disactivating all other plugins and turning back to the bp-default theme?

When there are over a hundred posts spread everywhere on the net that deal the same issue with the same error message, I call it a wellknown fact.
WP 3.4.1
BP 1.6.1
TinyMCE Adv (no other plugin or js present nor installed)
theme 2011
PHP 5.3.13
Problem occurs nevertheless on 2 different servers (basic and VPS) and locally on Wamp.

Please switch back to the BuddyPress Default theme to test if the problem persists.

Also:
– What is the URL of the page (you can leave out the domain name if you want) where you see the error message?
– What exactly are you clicking in order to get there?
– Are you sure you’re logged in as a super-admin user?
– Are you running Multisite?

@ Boone

OK, maybe I didn’t make myself clear enough (sorry, English is not my mother language). Anyway, I just ran this test:
– Installed WP 3.4.1 brand new, nothing added.
– Downloaded BP 1.6.1 and installed the usual way
– Activated the plugin
– Clicked on Settings:
error msg: “You do not have sufficient permissions to access this page.”
– Checked the BuddyPress folder for CHMOD permissions and it is the way it should be (755)

This is all there’s to say… it happens regardless of which theme or which plugins are installed.

I’m not a big fun of WP and I do prefer using MODx as a CMS or a real Open Source code in a pure php enviroment… but I do think that people who turn to WP deserve that things should basically work out of the box because that is the main reason these type of packagers are chosen for. Same thing should apply to plugins that have to be fully tested before release.

Anyway, if you care to have a deeper look into this problem, I’m willing to give you full access as an admin on my server.

best regards

> I do think that people who turn to WP deserve that things should basically work out of the box because that is the main reason these type of packagers are chosen for. Same thing should apply to plugins that have to be fully tested before release.

Not sure what to say about this. Certainly the BuddyPress team did not release the software knowing that this bug existed, but ignoring it. As I said above, no one has given us steps to reproduce it. I can’t reproduce it on my setup. And we can’t fix something we can’t reproduce.

Anyway, the “permissions” error you’re seeing has nothing to do with file permissions. This is the error that WP throws when attempting to visit a wp-admin URL for which a callback function has not been added, or for which the current user does not have access (according to WP’s internal capabilities system).

Could you please share the URL of the page you’re attempting to visit? Again, feel free to replace the domain name with ‘example.com’ for privacy – I just want to know the part starting with ‘wp-admin’.

I’m not clear what “Clicked on Settings” means. There are several places in the WP Dashboard where the text “Settings” appears. Can you clarify exactly which menu item you’re clicking?

Also, have you run the BuddyPress setup wizard? (There should be a yellow alert after installing BP that reads “BuddyPress has been successfully installed! Click here to complete the setup” or something like that.

I get the error after the setup wizard has ended and the msg ‘BuddyPress has been successfully installed’ appears. In the Plugin page, in the BP strip next to Deactivate | Edit there’s the Settings link. I click on it and the message comes out. You should know the page link since it’s part of BuddyPress’s files anyway:
…/wp-admin/options-general.php?page=bp-components

Can’t go any further than that

> I get the error after the setup wizard has ended and the msg ‘BuddyPress has been successfully installed’ appears.

This suggests to me that BP is not recognizing that the wizard has actually been run. You should see the ‘BuddyPress has been successfully installed’ message *before* running the wizard. Once it’s been run, the message goes away.

When you hover over the top-level Settings menu item on the left menu of the Dashboard, do you see a BuddyPress subnav option?

> In the Plugin page, in the BP strip next to Deactivate | Edit there’s the Settings link.

This is odd – BuddyPress does not add a Settings link here, to the best of my knowledge. Though the URL you list is the correct location of the settings.

This is sort of a shot in the dark, but could you try deleting your cookies that are prefixed with ‘bp-‘?

All I can say is that I I started in a clean config…. no cookies or temp files in cache, no wp_bp tables in the DB…..no extra plugin installed. I place the BP folder into plugins, activate it, run set-up from dashboard submenu, complete the 5 steps selecting Default BP Theme and getting the ‘Ready to go!’ final msg. At this point, I don’t see any config menu in the admin left column except the setup; the only settings available link is in the plugin page as you can see here:
snap-1
If I click on it, and you told me the link appears to be correct, I get the following msg:
snap-2

….and I’m stuck.

It looks like the setup wizard is not actually completing.

I’m afraid I’ve done about as much debugging as I can do remotely. If you want to send me creds to your server, you can do so at boonebgorges/gmail.

I’m getting the EXACT same issue…. argh… Same everything (WP Version, error message, link in ”installed Plugins” , it has a setting button….

In private conversation with the OP, it turned out that the problem was that the wizard had not been completed. Run it again (by clicking the link in the yellow alert box at the top of the Dashboard), and this time make sure that you click the Next button at each step – don’t click away on any menu items until the wizard is finished.

OK, I guess I can close this as a resolved topic