BuddyPress.org

Hi @boonebgorges Thanks a lot for the reply – no I actually have root on my server. So I went in and copied all the WP 3.1.3 files and installed manually, editing the connection strings myself in wp-config.php

For Buddy Press I copied the files via FTP to /plugins and installed from there. I do indeed have phpMyAdmin access. It looks like the tables are there and I can create groups and post updates in them. It’s just when I enable forums then that page shows no topics displayed. Likewise when I got to post in a public group via that group’s Forum tab it will also error. I’ve tried every solution I could read in here all day long to no avail Even clicking and unclicking the group’s permission to allow discussion forums.

URL: http://stangnation.com
Forum Link: http://stangnation.com/forums

I’ve tried a number of permalink structures as well – I am currently using /%category%/%postname%

I CHMOD /plugins/buddypress to 755. I made sure of course the bb-config.php is accurate and in the root. BuddyPress SQL tables are on the same db as WordPress is..

Really stumped here…

@nicholmikey… thanks for the help on cubepoints implementation…

Have you integrated buddypress?

https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/

https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

BuddyPress Template Pack 1.1

If you want it totally separate, then install first WP at domain root – http://yoursite.com. Create a second WP install at say, a physical subdomain – http://community.yoursite.com/ – using same database but different prefix for tables and install BuddyPress there.

== why I do not have the option of Blogs in my component setup ==

Because you need to make it multisite first i.e. create a network https://codex.wordpress.org/Create_A_Network

1. Deactivate all plugins including BuddyPress

2. Create the network – if you hit some snags, support forum is at https://wordpress.org/support/forum/multisite

3. Before installing BP – https://codex.buddypress.org/getting-started/before-installing/

Hi Joanquingrech.

You can change any of the labels and messages in BuddyPress to whatever you want by making a customized language file. This article explains what to do: http://wpmu.org/basic-guide-to-creating-a-buddypress-language-file-for-sitewide-label-and-message-editing/

I like thinking of groups as “categories” myself. If you change them to “categories” or “topics” in the language file, then they can be geographical areas, or guilds, or whatever you want.

You can remove “groups” from the menu by creating a custom menu in WordPress that doesn’t have a ‘Groups’ tab.

Normally, users would join the groups themselves by clicking on the “join group” button, but as an admin you can move users around as you want between groups.

I can’t advise you on the theme for the forum appearance. I’m just going to edit the stylesheet myself to set mine up how I want.

cheers,

Clare

How? please always share how you solved a problem on a open forum as it may help others who come across the thread.

https://wordpress.org/support/topic/30-upgrade-bug-ftps?replies=100

`define (‘WP_MEMORY_LIMIT’, ’64M’); adding this to wp-config can solve my problem ?`

This is a non question the response to which always has to be ‘You tell us’! try it does it fix the issue? it’s a simple test.

if it doesn’t then your host may not permit individual sites to alter PHP at site level ( very sensible on shared hosting) in which case you may need to speak to tech support and ask that the memory limit is increased or whether it can be.

You probably need more memory…..

Here’s how to get around activation. I was having the same problem on my test server, since it couldn’t send out activation emails. If you need activation emails enabled, then this workaround will not work for you.

For users that have already been created and cannot login, you can go into the wp_users table in the database and change their ‘user_status’ from ‘2’ to ‘0’ (if you have database access). ‘user_status’ is not used in WordPress — it’s a dead field — but Buddypress uses it to redirect to the homepage if a user has not been activated (aka user_status=2).

To avoid the problem for future user registrations, you can change a file to avoid activation (if you have FTP access). In the buddypress plugin directory, find bp-core/bp-core-signup.php. Find the line that says:
`$wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 2 WHERE ID = %d”, $user_id ) );`
In my installation (1.2. it is on line 357. Change the 2 on that line to a 0. So it should look like this:
`$wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 0 WHERE ID = %d”, $user_id ) );`

Now when a new user is created, they will automatically be able to login without their email needing to be confirmed.

We can’t see what that file parses and outputs! It looks as though there is no structure?

So do a number of those function calls describe markup structure? You will need to look at them and edit or copy where necessary; however you shouldn’t really be having an issue? you view the generated output of an index.php or page.php and match that to a buddypress page and ensure that the BP page matches to your themes. What structure does the file above generate? it should match to the other pages in your theme and is the structure that your BP pages need to duplicate.

@famous, you are right about that. searching multiple blogs is too costly on database if the posts are not cached in a global table. The unified search does not includes it because most of the sites do not use any sort of global post caching, and searching the posts on a network of say more than 20 blogs will be too much for a shared server to handle. I remember there is a plugin https://wordpress.org/extend/plugins/multisite-global-search/ which does global search.
The problem is, It will put some real strain on database. if you still want to use it, you can extend the unified search with the above mentioned plugin.

hope that helps.

However, that’s running BuddyPress 1.3.

BuddyPress 1.2.8, which is the current version, does have a couple of small issues that we’ve noticed so far with WordPress 3.2, mainly with javascript in the BP-Default theme. If anyone spots any more, please let us know. We plan a same-day release of 1.2.something with WordPress 3.2 to address these.

You can get the latest in the 1.2 series from https://buddypress.trac.wordpress.org/changeset/4550/branches/1.2?old_path=%2F&format=zip (at time of writing. SVN is https://svn.buddypress.org/branches/1.2/)

You can do all that when you transform your single WP into a multisite installation by creating a network with subdomain structure https://codex.wordpress.org/Create_A_Network
Multisite support forum – https://wordpress.org/support/forum/multisite

“same content” – if you mean that each user has a portfolio page, or about me page, a contact us page, etc. this can be achieved by creating a custom theme which you can designate as the default theme for each new subsite created by your members.

Create a network/go multisite before installing BuddyPress plugin if you want to add social networking features – https://codex.buddypress.org/getting-started/before-installing/

wp in multisite/multi-user mode is for multiple blogs on the same installation, if that’s what you mean…

https://codex.wordpress.org/Create_A_Network

EDIT: darn it – beaten to it by moments….

You might start out small. Install BuddyPress and enable just the activity stream; disable everything else. Make sure that the theme css works well with the activity stream. You’ll need to install the BuddyPress template pack. After you are satisfied with the activity stream then change WP install to multi-site. You’ll want to lock it down so that you control creation of blogs – so that you don’t have to deal with splogs. Once you have that working then you can add a few other BP features – private messaging, etc.