Search Results for 'wordpress'
-
Search Results
-
Lately, I’ve been seeing responses like this to BuddyPress help requests:
- Spam registration is a WPMU problem, not a BuddyPress question…
- Deleting users is a WordPress function, not a BuddyPress question…
- Hiding the admin panel is a WordPress question…
As a developer I agree, but as a site admin, I feel this is a bit like saying “I’m not worried about my lung cancer… It has nothing to do with my brain.”

WordPress is the “host”, but when BP is activated, BP/WP two are inseparable in some unique, exciting, and very complicated ways. It creates a whole lot of very unique issues that are NOT adequately resolved outside of BuddyPress specific resources, such as this forum. If you are a site admin, every one of these issues must be rethought and solved in the context of BuddyPress.
A good example is the BuddyBar. Plainly, it offers admin functions such as Delete User and Mark as Spam, yet I still hear people say that marking spammers and deleting spam blogs is a WPMU issue. We can’t have it both ways, in my opinion!
When I have my developer hat on, it’s clear as day what is a WP vs. BP issue, but when I put on my admin hat, there is no such distinction. It’s like pouring black and white paint in the same can, and then telling somebody to paint the living room using the black paint only.
Lately I get an error while creating a group at this stage: create/step/group-avatar
Error: There was an error saving group details. Please try again.
My site details are:
WordPress:
WP single install 2.9.2
Where:
On a Subdirectory – http://nijmegeneet.nl/club/
BuddyPress:
BP 1.2.3
Plugins activated:
All in One Webmaster,
Custom Login Page,
Tweetstream,
Maintenance Mode,
Facestream,
BuddyPress Links,
Invite Anyone,
oEmbed for BuddyPress,
W3 Total Cache,
Wordpress Backup,
WordPress Table Rename,
WP-DBManager,
WP Security Scan
Theme:
Child Theme of bp-default
bp-custom.php:
<?php
define(‘BP_MEMBERS_SLUG’,’leden’);
define(‘BP_GROUPS_SLUG’,’groepen’);
define(‘BP_ACTIVITY_SLUG’,’activiteit’);
define(‘BP_MESSAGES_SLUG’,’berichten’);
define( ‘HEADER_IMAGE_WIDTH’, 939 );
define( ‘HEADER_IMAGE_HEIGHT’, 132 );
?>
BbPress:
built-in
Hosting:
Servage Hosting
I got this after upgrading BuddyPress Links to version 0.4. Can this cause this error?
Thanks for your help!
Topic: Install on MU or regular WP?
Forgive me if this has been answered a hundred times, but I can’t find it – probably b/c of the common-ness of the search terms I have to use.
Should BP be installed on a working version of MU or just standard WP?
The installation instructions on BP website indicated a standard install of WP, but now that I’ve done that, I can’t seem to use a plugin designed for MU because it’s supposed to sit in the wp-content/mu-plugins directory — which I created, but WP doesn’t seem to find it — or the plugin just isn’t compatible with a non-MU install.
The plugin is the WordPress MU Demo Data Creator (http://wordpress.org/extend/plugins/demo-data-creator) and the plugin information states that I can find it’s settings at the Site Admin menu on the Dashboard. I see no such menu, so I’m thinking that must be part of MU, not WP (I’m running 2.9.2).
Any help would be appreciated. TIA
Bluehost
Buddypress from SimpleScripts, WordPress MU 2.9.2
Users cannot login to their blogs.
I think the problem is with www in the URL that is missing in the blogs that are created. The main site has www but their blogs don’t have. How do we change its behavior of creating blogs with no www? I think it will solve the problem. I just do not know how to do it.
I really think this is the conflict. Please help!
Example of how the URL looks:
Main site: http://www.google.com
User Blogs: http://google.com/myblog (with no www)
I could not find any similar post but I just found one in WordPress Mu that seems to be the same problem and it is not resolved: http://mu.wordpress.org/forums/topic/17651
