just leave buddypress.css blank if you want to kill all bp styles from being loaded by the plugin. You could also deregister the css file from getting loaded
Template overiding works in same manner as the css file.
BP overrides WP a bit. If you use bp_is_current_component('activity') it works on BP pages. This is something that needs to be fixed now that BP uses any theme.
The best solution is to phase out bp-default from your sites or ask your theme developer to convert their bp-default derived theme to a WordPress theme.
This code is just a start, I did not test to see if field groups will break it but you can get an example of spitting out fields as an object array variable on profile load and then using the variable to get the values instead of requesting each time.
put this in bp-custom.php
// creates global object array from profile fields
function bp_profile_fields_array() {
global $fields;
$fields = array();
if ( bp_has_profile() ) :
while ( bp_profile_groups() ) : bp_the_profile_group();
if ( bp_profile_group_has_fields() ) :
while ( bp_profile_fields() ) : bp_the_profile_field();
if ( bp_field_has_data() ) :
$field_name = bp_get_the_profile_field_name();
$field_value = bp_get_the_profile_field_value();
$field = array(
'field_name' => $field_name,
'field_value' => $field_value,
);
$fields[] = $field;
endif;
endwhile;
endif;
endwhile;
endif;
return $fields;
}
add_action( 'bp_before_member_header', 'bp_profile_fields_array' );
// echoes value of field from object array based on param
function bp_get_single_profile_field( $param ) {
global $fields;
foreach ( $fields as $key => $val ) {
if ( $val['field_name'] === $param ) {
echo $val['field_value'];
}
}
}
Then in your member templates:
<?php bp_get_single_profile_field('PROFILE FIELD NAME'); ?>
Don’t worry, there will be an update to include the files and bp-default is getting moved out into wp .org repo but bp-default may be deprecated fully in the future.
There will be a 1.9.1 put out quickly to address this.
The reason this is happening is because bp-default was deprecated with this release of BuddyPress and the notifications templates are not included in bp-default. This is your warning to phase bp-default out of your sites. BuddyPress works with almost any theme now so your options are plenty.
I know WPTouch 3 has some improvements with only loading it’s own theme and files to lessen the loading times but it’s still the full WP theme getting swapped out for another theme. This is how nearly all the mobile plugins work.
You can edit the BP templates to make them fit into WPTouch or other mobile themes.
WPTouch doesn’t load anything less. It is essentially just another theme with a mobile UI. Also, the template files of BuddyPress are not 100% responsive and do not fit perfectly inside WPTouch. You would have to make them look proper.
If load times are slow then it could be that you are just loading too many files. This is an issue on even desktop browsers because more people visit websites from mobile browsers than from a pc now. I suggest you deal with making your regular site more data efficient in addition to serving up a better visual for small screens.
Viewing 25 replies - 326 through 350 (of 2,910 total)
