BuddyPress.org

@romik84 Ok, so if you’re not tracking each blog by channel, how do you know how much to pay each blogger?

I would be surprised if that was the reason though but noticed a few plugins showing this warning and on some of the better known and reliabal ones so it’s odd @DJPaul probably knows why or perhaps@boonebgorges does

i use this http://premium.wpmudev.org/project/buddypress-group-calendar is a premium, but i dont know another plugin

Not entirely sure what triggers that warning, I simply ensured I had correctly filled in the readme.txt ?

Tags: buddypress, profiles, map, profile map, location
Requires at least: WP 2.9, BuddyPress 1.2.4
Tested up to: WP 3.0.1, BuddyPress 1.2.6
Stable tag: 1.1

which you appear to have as well, wonder if it has to do with the loader.php or at least having a file with that name or similar I used upm-loader.php to initialize and call the main file slightly unnecessarily as I remember thinking as could quite easily have worked from the main file and run the BP init check

Check out this plugin on BuddyDev:

BuddyPress Sitewide Activity Widget

@xberserker: There are some problems with your plugin (which is awesome btw!).

You made a mistake when naming the folder or when calling the css/js files. When you install the plugin it tried to load the CSS and JS in the following path:

/wp-content/plugins/buddypress-activity-bar

While the actual path is

/wp-content/plugins/buddypress-activity-stream-bar

Changing the folder name causes a php error

Thanks Gökhan!

me. I think its confusing that when you are viewing the activity stream you see a name. if you want to do an @ in a reply, you have to go to the person’s profile to find their @name and then back to where you were to leave the reply/comment. Anyway ideas to work a way around this without a huge mess? Like maybe a little script/code so a tool tip pops up with the @name?

Confirmed on the trunk. Brandon’s diagnosis and fix looks right.

It’s been fixed in the trunk: https://trac.buddypress.org/changeset/3651 If you’re having the problem on 1.2.7, you should be able to fix it by making the following changes:
– In bp-xprofile/bp-xprofile-filters.php, change line 81 to
`$field_value = bp_format_time( $field_value, true, false );`
– In bp-core/bp-core-templatetags.php, change line 815 to
`function bp_format_time( $time, $just_date = false, $localize_time = true ) {`
and replace line 820 with the following lines:
`$root_blog_offset = false;
if ( $localize_time )
$root_blog_offset = get_blog_option( BP_ROOT_BLOG, ‘gmt_offset’ ); `

Thanks to Brandon for the fix.

Check through the plugins listings first to see what’s available that may cover your requirements.

Give this one a go:

https://buddypress.org/community/groups/oembed-for-buddypress/

I can confirm the problem. The issue occurs if you have a negative GMT offset. Since xprofile dates are saved for midnight of the chosen day, anyone with a negative GMT offset will have their date shifted backwards, which then displays as the day previous to the one chosen.

ie –
Date Chosen: January 4th, 2011
Saved in Database as : January 4th, 2011 at 12:00am GMT
Timezone: Central Standard Time (-0600 GMT)
After bp_format_time(): January 3rd, 2011 at 6:00pm CST

I’ve added a patch to https://trac.buddypress.org/ticket/2779 to fix the issue.

@Tekuan%20Coleman
is there a “real” and “fake” default theme? i have activated the

Yes and that is the point I was trying to make earlier there is only THE bp default theme all it’s files live in /plugins/buddypress/bp-themes/bp-default any other theme is what is referred to as a child theme and may have any number of custom changes that can cause issues. To trouble shoot it is essential that the defaults are used i.e the default theme is activated and no plugins other than BP are running.