BuddyPress.org

@miri
If you switch to the default theme (BP-Default), does it work?

That is useful for pagination, but delete the lines around the calls to bp_members_pagination_count() and bp_members_pagination_links() in /members/members-loop.php in your theme.

@rhivanz: If your site running on WordPress MS, you can put BuddyPress in the sub-blog, so all BuddyPress features, including user profiles, put there. About how to make it, can be viewed at https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings

Are you using a normal WP theme? If so you have to install BuddyPress template pack plugin.

https://wordpress.org/extend/plugins/bp-template-pack/

Then in admin>> reading chose a different front page

Ugh yeah this sucks… I got it working on a fresh blog install with the default theme. On the blog I desperately need it working on no go. I’ve disabled numerous plugins/removed any jquery includes etc. to no avail. Just can’t seem to figure out why it works one one blog and not the other. *sigh*

If you want to keep the functionality that the Members component provide, but want to remove the “tab” from the menu, edit your theme’s header.php

Saw your Trac ticket:
https://trac.buddypress.org/ticket/2556

This is a weird bug. It shouldn’t show the RSS link on an AJAX request. If you have any other plugins or custom code running, please disable them and only have BuddyPress and the BP default theme running

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-get-post-images-in-activity-if-theme-post-has-custom-fields-for-images/

There’s nothing that i’ve seen come thru yet on this.

Daniel, technically you should have labeled that link to your site as NSFW or PNSFW.

The adminbar is controlled from the adminbar.css stylesheet located in the bp-default themes _inc/css/ folder

You would need to change #wp-admin-bar from position:fixed; to position:absolute;

References to link colours can be found by scrolling down and looking for ‘#wp-admin-bar li a’ ‘color:#eee;’ and changing it to something more suitable.

When I visit the page to edit the group css in any group I get the following js error:
(I am using a custom theme with a few plugins)

jQuery(“.colourpalette li”).tooltip is not a function
[Break on this error] fade: 50

If you’re trying to use BP-Default on the non-BP_ROOT_BLOG site, and BP_ENABLE_MULTIBLOG (which is a mysterious parameter at the best of times) doesn’t fix it, I suggest you edit header.php in your child theme and set the links directly (remove the calls to site_url(), IIRC).

You’ll need to add CSS to your theme to make it work. If you switch back to the BP-Default theme, I bet it works properly?

i am happy to share.

so i use jquery-ui first off, but if you just want today’s events, you don’t need to use it

so the first part is what is in my sidebar.php file

<?
// first set up today’s date
$today = date(‘m/d/Y’);
?>

This next part is still in the sidebar.php
<?
generate_week_events(‘1’, $today);
// to figure out tomorrow, i use mktime and date together
$tomorrow = mktime(0, 0, 0, date(‘m’), date(‘d’)+1, date(‘y’)); $tomorrowCompare = date(‘m/d/Y’, $tomorrow);
// you can use the +1 to add as many dates as possible for your calendar
// the ‘1’ that is an argument of the function is the id of the jquery-ui tab. i just add a “generate_week_events” function for as many days that i want to show and increment this number by one for each tab
?>

the function then compares the date fed in as an argument to the date in the custom field. if there is a match, then it shows the corresponding events. i just placed this in my function.php of my theme

<?
function generate_week_events($id, $date) {
global $post;
?>

<div id="tabs-“>
<?
// The cat=>9 here is the Events Category for this site it was implemented on and gets all posts where with a meta_value of the date fed in
$args=array(‘cat’=> 9, ‘meta_value’=> $date);
query_posts($args);

// Here I just split the $date at the “/”. the client at one point wanted the date spelled out in the list as “January 1st, 2010” but later did not, but i kept it here for your reference if you want it.
$r_date = explode(‘/’, $date);
$mk_date = mktime( 0,0,0, date($r_date[0]), date($r_date[1]), date($r_date[2]));
$print_date = date(‘F jS Y’, $mk_date);
// echo $print_date;

if ( have_posts() ) : while ( have_posts() ) : the_post(); ?>

this is the basic concept if you want the full code lemme know and i can email it to you

Any questions feel free

Matt

Might be codes in custom theme have not been updated to latest BP version. Change theme to bp-default theme and see if same thing happens.

Very often with errors in either scripting or markup the reported point of error is not necessarily where the actual problem starts from it’s just where the validation finally fails to be able to parse the logic.

You are saying ‘IF’ something then do something and we are waiting for that to be finished, however you are only showing a snippet of code out of context which does mean one can only base things on what is shown.

looks like you have lifted the code that is used for the ‘if no widgets run the add widgets error markup’ that is really used more for distributed themes, the ! ‘not’ operator is useful for saying if these functions don’t exist and can’t be called then fallback to this following markup/script. Your code as written needs endif;

You can write the dynamic sidebar call in a more straightforward manner?

if ( function_exists(‘dynamic_sidebar’) )
dynamic_sidebar(“Profile Groups Area”) ;

The WP codex page gives more info:
https://codex.wordpress.org/Function_Reference/dynamic_sidebar

If you changed the folder groups to projects that will not work. The file structure should remain intact. Also, you should change the name of groups to projects via the language file, not via template files. I wrote a post about how the dev’s of BP should make changing groups to something else easier but they said there is no other way to do it properly besides the language file.

It ought to. Specificity is almost likely the culprit.

All rulesets are afforded a ‘number’ that represents their ‘Weight’ or specificity; the specificness of that rules properties over another, it’s calculated from the selectors which have various numbers assigned them.

To test try adding in antecedent selectors – ancestors or parents of the selector being styled until you find control, so :

body#bp-default a , body#bp-default #container h2 a:hover

Play around, add further selectors to the mix to increase the weight if necessary, see if that gives you control, then you will know what the issue is

In your child theme’s stylesheet, add this:
a {color:red !important;}

If you made a copy of the bp-default stylesheets in your child theme, that rule would be located in /_inc/css/default.css.

What’s all this talk about child themes? Read up here:
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/