Forum Replies Created
You have a good point. I’ll unlock your thread. I suggest that you place a link back to this thread (for reference) and explain why you’re creating a new thread so that some other moderator does not do what I did!
So, you’ve managed to output the tab but cannot get the link to work?
Have you looked at the Skeleton Component–in particular in bp-example-core.php at the function bp_example_load_template_filter() and the section below that entitled “Screen Functions”?
You’re welcome! I’m glad you are up and running with BP Group forums.
With respect to a forum control panel in WP’s back end, you are not missing anything. When using bbPress as a BP Groups forum component, there is no sitewide bbPress admin control. Instead, each BP group has the ability to have its own forum. To get the group forums to work, a group admin has to navigate to the given Groups “Admin > Group Settings” menu and click the “Enable discussion forum” checkbox.
Your issue should be easy to fix!
1. Before going through this process, double check to make sure that the bbpress directory exists under /plugins/buddypress/bp-forums/. It should be there as it comes with a clean install of BP.
2. Assuming that checks out, then the next step is to make sure you have a backup of your MySQL database.
3. Now delete, or in DB parlance, drop the unneeded bbPress tables from your database.
4. Finally, go back to your WP admin screen and navigate to “BuddyPress > Forums Setup” and follow the instructions.
There may be a meta record that tells BP that you’ve already installed bbPress. If BP thinks that a bbPress instance has already been installed, you’ll get some verbiage like the following:
“bbPress forum integration in BuddyPress has been set up correctly. If you are having problems you can re-install”
If that is the case, just click the “re-install” link.
A successful bbPress install will have two bb-config.php files. The primary one will live at the root level of your WP install. The second one will be located at /plugins/buddypress/bp-forums/ and is a single one line piece of code to stop unauthorized access to your forums. It should not be an issue to delete the version living at the root level of your WP install as the process of installing bbPress for BP Group forum use creates this file. Do not delete the second, lower-level version of this file.
Please see my first post in this thread as I may have been editing it as you were typing your response.
As for your immediate post question above, the table prefix is not necessarily an issue (but it could be). It really depends on how you are trying to use bbPress (as a standalone forum, or solely for BP Group forums).
But, to get to the heart of your issue, we need to clarify in what way you’re trying to use bbPress.
Are you trying to integrate an existing bbPress install with BP group’s? Or, is this a brand new bbPress install with no data?
If the latter, there is no reason to do a separate install of bbPress. BuddyPress comes with a barebones version of bbPress already. It allows BP Groups to each have their own forums. However, it does not allow for the creation of a sitewide forum.
If you have an existing bbPress forum that you’re trying to associate with BP, then the bbPress tables must be installed into the same database as your WordPress tables. Make sure that you have read this BP Codex article: https://codex.buddypress.org/buddypress-site-administration/using-an-existing-bbpress-installation/
Finally, if you’re trying to have a standalone, global bbPress forum on your site, and not just have BP Group forums, then read this: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-do-i-create-a-non-group-specific-forum
That’s not possible with BuddyPress at this time. See this: https://codex.buddypress.org/getting-started/faqs/
In fact, I don’t see this ever being an option in BP–even when the new bbPress plugin becomes available. Both BP and the upcoming plugin version of bbP are software layers that sit on top of WordPress. So each is responsible for their own sets of data access functions. Even with BP Group-based forums, the bbP functions are being hijacked to work within BP but only barely.
To have a standalone install of bbPress functioning in WordPress (which is what would give you a site-wide forum) requires a process called deep integration. For more information on integrating bbPress with WordPress, search the WP or bbP forums. Or better yet, just wait until the pluginitized version of bbPress is available!
The way in which you check to make sure BuddyPress is installed and activated has changed over time. As @djpaul indicates, the proper way is to use a mypluginname_loader.php file and hook into the bp_include event: https://codex.buddypress.org/extending-buddypress/checking-buddypress-is-active/
The BuddyPress Skeleton Component is woefully out of date a this time. So you should use it as a general guide only. To get a clearly understanding of how things are done, I suggest studying a few of the more popular, major custom components that work with the latest version of BP.
Oops! Nice catch. It is next Monday, November 15 as detailed in my BP update here: https://buddypress.org/community/members/jeffsayre/activity/115287
[blockquote]Jeff, yes, I like MAMP, but also wanted to avoid creating lots of copies of Apache and php et al – and I want to run on port 80 anyway…[/blockquote]
I have a single Apache/PHP install (the default MAMP version) and simply use Apache’s virtual host directive to host 9 different WordPress development sites locally. They all have their own test domain (they do not use “localhost”), and they use the default Apache port (80) and MySQL port (3306). It’s simple to set up and manage. This is done with MAMP not MAMP Pro. If you don’t know how to do this, then MAMP Pro will do it for you.
I gave up a long time ago rolling my own WordPress and BuddyPress installs directly on OS X. It was too much of a pain for very little benefit. I switched to using MAMP (the free version) and both install easily without issue.
“For BP 1.3, we’re going to add current_user_can checks throughout so if someone wanted to add a capability to a certain role or user, they could.”
Providing that flexibility is nice. However, with the exception of groups, there is no reason that the current BP core components need to offer the ability to assign roles. Why would a user want to grant someone the right to control their personal content? Facebook and Twitter don’t offer users that option.
Blogs, which live outside of BuddyPress, are different of course. It makes sense to allow blog owners the ability to add helpers to their blog, to allow others to add content as authors or editors, etcetera. In BuddyPress, this type of collaboration is also currently possible with the group component.
But for all other core components, assigning additional roles seems like a bad idea as the focus is on individual users creating their own content which they alone control.
With the limited exception of BP groups, BuddyPress offers only one role — that of user. The forums are controlled by bbPress code, integrated into BuddyPress, but it’s bbPress that is in control of offering additional roles. Even when bbPress is relaunched as a WordPress plugin, forum roles will still be controlled by bbPress.
BuddyPress is a social layer that sits on top of WordPress. As such, the notion of user and author are synonymous. What does all of this mean?
With the exception for BP groups mentioned above, BuddyPress is a user-centric platform where there are currently no-jointly owned or controlled subsets of data. Ignoring the overall Site Administrator, in BuddyPress, there is a one-to-one relationship between a given piece of datum and a single owner of that datum. The key is who owns data. That person is the one with ultimate control (ignoring the super admin). Even with groups, the original group creator is the owner of the group–at least until he or she adds another admin. Group mods do not own the group data, they just help to manage it. Now, if the original group admin leaves the group, the new admin becomes the sole owner.
So user roles are irrelevant to the operation of BuddyPress as it focuses on users and not user roles. It is a social networking layer after all and not a content authoring and management layer like WordPress.
The component has been overly tested by a few people at various stages now. The code is stable and ready for primetime. Also, some people who I sent previous copies to never provided feedback, so it was my decision to release it into the wild rather than beg for feedback. As with all my plugins, this will be freely available on the WP Plugin Repository once it’s released.
@r-a-y is correct. This is not an issue of privacy. Privacy is about offering users the ability to control access to their data.
Well, @hnla beat me to the answer by 4 minutes!
A quick search with the proper terms will bring up a number of options. This post in this thread should help. Once my BuddyPress Privacy Component is out in the wild, you will be able to easily do this with a simple radio button selection in the Site Admin menu of the component.
Before performing such a major upgrade (both WordPress and BuddyPress), you should backup your database. Next, it is always best to be safe than sorry. Deactivate all plugins. This means BuddyPress too, as it is a WordPress plugin. Once WP is up and running, it is time to upgrade BuddyPress. You should read the additional details here: https://codex.buddypress.org/getting-started/upgrading-from-10x/ See the “Upgrading from 1.1.x to 1.2.5” section, paying special attention to the notes on the theme files.
Finally, you need to upgrade any BP-dependent plugins before reactivating them. If any of these have not been upgraded to work with at least BP 1.2.5, then they should not be reactivated. Nicola’s plugins are very outdated and will not work with the current version of BP.
You’re making it more difficult than need be.
Just use the function bp_core_get_user_displayname() found in bp-core.php. You can give it a userid and it will spit out the user’s fullname. Just make sure that you echo the output as follows:
echo bp_core_get_user_displayname( $userid )
Yes, the Privacy Component is a user-centric component, allowing a site’s members to control which pieces of their personal data they share with the world.
A plugin’s readme.txt file is your friend. It can answer many of the common questions you may have about a given plugin. Your question is answered on the first sentence of the Installation section.
From the Installation section of the readme.txt file for BuddyPress Links: “Notice: This plugin is under heavy development, and is not recommended for production environments!“