BuddyPress.org

Unfortunately, the fatal error you are getting has nothing to do with buddypress. You can read the error that it’s in your wp-includes/class-phpmailer.php on line 34, and “Cannot Re-declare” means that the class is called twice somewhere.

Go into that file, above, and delete the “Class PHPMailer” is what I would advise.

@1stAngel I have not used the Atahualpa theme but try adding this to your theme’s style.css file :

`/* Inherit the default theme adminbar styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

@JamieWade replaced the read more with this code and it shows the numbers and arrow at the bottom… but when you click nothing happens… any idea why?

@1stAngel
First, can you tell which version of BP you are using?
Second, are you using template from BP template pack?

@mercime Ok no, I see no adminbar.css in the header.

@mercime I didnt but some strange things have happened recently and I had to remove some plugins. I have a feeling they have messed me up somewhere.

I have a job to make sense of my theme as it is Atahualpa but I will go see, thank you

not particularly odd the normal approach is to make the default web directory in htpd.conf extremely restrictive and from there one allows more specific directories relaxed permissions, it is odd however for that general rule in the vhost container to be there and so restrictive. The workaround in the link is not a hack as such I would set up my directories with main rules in this way. Control panels do have a habit of having to impose some strange conditions due to having to have control over files and of needing often an unusual structure in order to work. personally I prefer not to have control panels making a mess of servers.

== but suddenly the admin bar is in a list under my site ==

@1stAngel Did you change/edit your theme? Check if adminbar.css is still being called – look at header.php source code.

Boom, posted same time. No problem @berndw !

Are you using Buddypress 1.2.8? I think Kaltura only comes with the plugin BuddyPress Media Component. If you have that installed you could just disable it. Photo and Video are not default Buddypress component, I’m pretty sure they’re coming from a third party plugin.

Read: https://buddypress.org/community/groups/miscellaneous/forum/topic/buddypress-org-plugin-groups-not-working-properly/

Okay, I gotcha. In order to place pages before the default buddypress menu tabs, you need to modify your theme’s header.php file. Look for some code that looks like this and paste it just after code that looks something like this <div id="header"><h1 id="logo"><a href=&quot;" title=""></a></h1>

Now your pages will appear before your buddypress menu items. If there something specific you want, you can just hard code in the header.php file with good ole fashioned html.

Oh, and that Exclude Page plugin will allow you to easily hide pages you create from being added to the menu.

Not just you! We know about it and, in fact, it is being looked at by top men. Top. Men.

http://www.youtube.com/watch?v=yoy4_h7Pb3M

PDX came on IRC. For the benefit of Google, PDX is running on a server with the Confixx panel installed. It appears to do something funny with the Apache rules for .htaccess files, causing a 403 error on the entire domain (NOT just the WordPress specific files). http://wp.uberdose.com/2004/03/05/confixx-and-htaccess-and-mod_rewrite-403/ seemed to help

If by Jet Stream events plugin, you mean https://wordpress.org/extend/plugins/jet-event-system-for-buddypress/. I suggest you drop a line at plugin dev’s site http://jes.milordk.ru/forums/

== project management tool (with a budget tracker would also be cool) that has the ability to be integrated with wordpress and BB. ==

If by BB. you mean BuddyPress (BP), then try out https://wordpress.org/extend/plugins/bp-gtm-system/

I also had this problem and went through a deep analysis.

The issue stems from the fact that Bluehost requires that the email be sent from an account that exists on the system. They do this as an anti-spam technique and they require this even if the mail is originating from within the system.

Enter WordPress. PHP uses a mail function mail(). WordPress maps this to wp_mail() and pretty much everyone uses the wp_mail for the plugins within WordPress. This makes sense as it allows customization of WordPress mail at a relatively low cost of performance.

Enter Buddypress. Buddypress places a filter upon wp_mail() such that all email originate from the user ‘noreply’ on the domain such that end users don’t reply to the notifications. Sounds cool.

But remember that Bluehost does not allow email to be sent from non-accounts and that’s the catch.

Using a foreign SMTP does not work for Bluehost blocks those ports. Using local SMTP will work but you need to provide the right setup and credentials. Finally, using mail-from plugin works since it filter’s the Buddyhost filter changing the email from address back to a valid Bluehost email account.

Hopefully, this explains what is happening and you can choose which strategy you want to use to fix the problem.