BuddyPress.org

Edit// Roger beat me to it
When you say if I put %category%%postname% sites go not found is this without BP activated?

Helga please check the other thread and just confirm (here) whether you can write to the .htaccess file correctly if you can then the issue lies with your server setup running under http://localhost/wordpress/ or whatever url you have to use.

@helverk – if custom permalinks (/%category%/%postname%/) don’t work for your WordPress without BuddyPress installed, then the problem is in your basic WordPress server setup, and not to do with BuddyPress.

You need to make sure you can run WordPress correctly with permalinks, before moving on to the BuddyPress installation. Unfortunately, the WordPress forums would be the best place to get an answer on this one.

@helverk – I think the crucial difference between your site and Christina’s, is that you are experiencing your problems trying to set up a local test server.

Does your site function correctly without BuddyPress installed? Including using custom permalinks (e.g. /%category%/%postname%/). When you switch to custom permalinks without BuddyPress what url’s do you see? Do they still have index.php in them (it shouldn’t be there)?

If they do, the problem is probably something in your basic server / WordPress setup, rather than a BuddyPress problem

@helverk

You wrote: But what I am ever going to do with it? in reference to your .htaccess file

You don’t do anything with the file the server does. The server must be able to write to the file to make any changes required automatically.

Have you tried going to the permalinks menu in the dashboard and set it to anything other than default, just change to day/month and save and tell us what the screen says , if there are any messages about not being able to write to the file or whether it simply kicks things into life.

I also note that your base is not ‘/’ root but ‘/wordpress/’ which may not help matters I presume you simply installed into the MAMP? web sites directory, it would be worth reading up on how to configure vhost containers and simple host file dev domains so you can run a site as a make believe top level domain.

I have the exact same problem as cristina.
running wp 3.0.1. on localhost (using WAMP to run it) with several different BP enabled themes (I blamed the themes at first) but no matter what the theme the permalink structure and the Buddy press seem to collide giving me the ever popular “Not Found The requested URL….was not found on this server.”

I am not very computer literate. The htaccess file is in the root
# BEGIN WordPress

RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index.php$ – [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]

# END WordPress

But what I am ever going to do with it?
index.php is also in the root and like .htaccess I have no idea what it says in it.
<?php
/**
* Front to the WordPress application. This file doesn’t do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/

/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define(‘WP_USE_THEMES’, true);

/** Loads the WordPress Environment and Template */
require(‘./wp-blog-header.php’);
?>”

@Bonlu – make sure you have WordPress set up for multisite: https://codex.wordpress.org/Create_A_Network

Then take a look at the recent site wide posts widget (in your wp-admin backend: appearance… widgets)

You need to develop your child theme so that it allows for the widget to be embedded on the home page, or take a look at the code in the widget and implement your own version in your home page template;

Developing your own child theme: https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

Almost always multiple ways to do it in WordPress. Depends on what type of changes you might want to make in the future.

https://wordpress.org/extend/plugins/wordpress-multi-site-enabler-plugin-v10/

Just create a child theme: https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

Then, you’ll want to overwrite the header.php file on line 79. Here’s the documentation for the wp_list_pages: https://codex.wordpress.org/Function_Reference/wp_list_pages the exclude parameter should work for you. If you don’t know the pages’ id, you can use this plugin: https://wordpress.org/extend/plugins/wp-show-ids/

Plugin: https://wordpress.org/extend/plugins/exclude-pages/

multisite is the new keyword you want. This is a good resource: http://wptheming.com/2010/03/wordpress-3-0-enable-network/

@adiljaved – yes, each individual having their own blog is a standard BuddyPress setup.

You’ll need to install WordPress 3.0 and configure it for multisite: https://codex.wordpress.org/Create_A_Network

Then install the BuddyPress plugin (from the plugins menu), and it’s as simple as that. You’ll have a default installation, default theme, and the ability for each individual to have their own blog.

Ask the hosting question separately – there are lots of possibilities (we use hostnine – a US company with servers in a few countries). Type of server you need will depend on the amount of traffic you get to your site.

BP.org follows a similar approach to wp.org’s forums.

This is a worthy agenda topic for the next dev meeting though.

Look out for the next one here:
http://bpdevel.wordpress.com/

Add the topic as an agenda item when the time comes.

Or at least supply us with a little more of a detailed explanation of what’s happening ‘Help’?

Then change those permissions!

alpha – https://wordpress.org/extend/plugins/bp-group-categoriestypes/

alpha – https://wordpress.org/extend/plugins/bp-group-categoriestypes/

@Pisanojm https://wordpress.org/extend/plugins/buddypress-badge/

@warut Thank you. Badge is working well in test install WP 3.0.1 – BP 1.2.5.2, subdomain structure, and upgraded from WPMU 2.9.2. Cool

@christinarule –

other than the check for mod_rewrite.c, you have the same .htaccess that I have in a default install, with permalinks set to /%category%/%postname%/ (http://playground.21inspired.com is a simple default install).

My .htaccess:
# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Unfortunately, this is beyond my area of expertise. Hopefully, someone else can help you get rid of index.php in your urls, and get the blog & BuddyPress urls resolved correctly.

Other quick thoughts: is your .htaccess in your site’s root directory? Do you have other .htaccess files in the subdirectories? Does your server support mod_rewrite?

Anyone able to help?

Sure, that is one place. But I still get different times in Sitewide Activity, a jQuery FullCalendar script that works fine in WordPress site without BP, etc.

I am on customized BP 1.1.3 + WP 3.0, but judging from hnla’s comment the issue has not been fully fixed in the latest versions. Anyway I’m trying to figure out where to fix it, where in the code, where in the database.

.htacess

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

wp-config:

<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information by
* visiting { @link https://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/

// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘***’);

/** MySQL database username */
define(‘DB_USER’, ‘***’);

/** MySQL database password */
define(‘DB_PASSWORD’, ”);

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);

/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8’);

/** The Database Collate type. Don’t change this if in doubt. */
define(‘DB_COLLATE’, ”);

/**#@+
* Authentication Unique Keys.
*
* Change these to different unique phrases!
* You can generate these using the { @link https://api.wordpress.org/secret-key/1.1/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define(‘AUTH_KEY’, ‘put your unique phrase here’);
define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’);
define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
define(‘NONCE_KEY’, ‘put your unique phrase here’);
/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = ‘wp_’;

/**
* WordPress Localized Language, defaults to English.
*
* Change this to localize WordPress. A corresponding MO file for the chosen
* language must be installed to wp-content/languages. For example, install
* de.mo to wp-content/languages and set WPLANG to ‘de’ to enable German
* language support.
*/
define (‘WPLANG’, ”);

/* That’s all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

If you use custom profile filters plugin (https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/) and add a field labeled “Twitter”, user can enter their Twitter handle and the plug-in will automatically convert it to their Twitter URL. No need to enter URL.

Just thought I’d mention that I had this issue and solved it by checking that the blogs.dir folder AND ALL SUBFOLDERS, RECURSIVELY, were set to ownership by ‘apache’ and had 775 permissions.

This took some time to trouble shoot, as it turned out my host was only setting the blogs.dir folder to ownership by ‘apache’ and not its sub-folders. I had to specifically ask a second tech support guy to check the sub-folders for me before I figured this out.

‘apache’ needs to be the owner on apache machines, the rest should have the main ftp user as the owner (you may have to enable group permissions so you can still edit them)

I Hope this article I wrote helps: http://erikshosting.com/wordpress-tips-code/buddypress-avatar-upload-failed-fix/