Andrea is right. Nothing about the WP 3.2.x Dashboard style changes should have affected anything on the front end of BP. It’s likely a plugin conflict, or perhaps your theme is out of date. What theme are you using?
I found the culprit – bp_core_load_template(), in `bp_example_screen_settings_menu()`, is pointed toward the wrong template. It should read:
`bp_core_load_template( apply_filters( ‘bp_core_template_plugin’, ‘members/single/plugins’ ) );`
I’m going to make this adjustment, as well as a few others, and release a slightly updated version of the Skeleton Component. In the meantime, please let me know if you find other problems.
If by “plain PHP” you mean that it’s not WP, then that’s your problem. You must be running WP to make BP work. Try:
`require_once( /path/to/wp/wp-load.php );`
There are many people on this website who would be willing to help you, but more information will be necessary about your site setup. What version of BP are you running? What other plugins are you running? Do you have access to the PHP error logs? What do they say?
I ask because BP is known to be working on the latest versions of WP. It is likely that there is something peculiar with your setup – probably a plugin conflict – that is causing your problem.
As a side note, I understand as well as anyone how problems like this can cause a great deal of frustration and anger. However, much of this frustration can be avoided or at least eased if you’re willing to come forward and ask for help before reaching the breaking point. Angry messages like the one you’ve posted here and the ones you’ve posted on Twitter are understandable, but they don’t do anyone any good.
I’m pretty sure this is already the way that BuddyPress works, with the exception that if you’re running multisite/network mode, only *super* admins have this ability.
No, it does not require CloudSponge to operate. Check to make sure that regular BP emails are working; this plugin uses the same mail mechanism to send messages as BP and WP.
Not sure what you mean about “page tab”. It shows up as a subsection of the profile nav: Send Invites.
bp_before_members_loop is not a function, it is a WP action hook. Plugins and themes can use this hook to add functionality to your members page. Read the first limo provided by chouf1 to learn more, or google “WordPress hooks”.
Also, as megainfo suggests, it’s a good idea to learn a little about grep, which will help a lot in these instances.
%20 is a URL encoded space character. So it could be that, somewhere along the line, something is adding a trailing space to your user_nicename. Do you have access to your database, so that you can have a look? If you create a new user with all of your plugins disabled, does the same thing happen?
Based on the nature of the error, I would say that you upgraded to WP 3.2 before upgrading to BP 1.2.9, and those errors were logged before you upgraded to BP 1.2.9.
What did you set your permalink structure to? When you say that the page is not found, can you be more specific? Is it a 404 page? Or is it some other kind of error?
Cool, can’t wait to see the results! My Import From Ning importer https://wordpress.org/extend/plugins/import-from-ning/ will handle content, but it’s not really built to scale to your network size. (Though you could peek inside the plugin to get a sense of how such a scalable import could work.)
Good luck with the last steps! Looking forward to learning more.
