BuddyPress.org

Hi Dyer,

I’ve just deactivated the User Role plugin and the problem is still there, no toolbar for new users. This is the link to the plugin that I’m using. http://shinephp.com/user-role-editor-wordpress-plugin/

Default setting is for all new users to be set as a subscriber.

Many thanks

Lynn

I reopened this ticket https://buddypress.trac.wordpress.org/ticket/3732 and DJPaul set the milestone to 1.7, and now I have no idea how to submit my patch (I am still not familiar with the process on buddypress.trax.org).

Anyway, I fixed up a patch and tested it on Buddypress 1.6.3. Maybe you can check out the changes and submit a patch on my behalf if you can. You can download files I modified at http://we.tl/HpU6emIJs4 and check things out.

> That function can not have filter because it is true or mot based on one thing.

Yes, and with a filter, that one thing can be expanded. If someone wants to create their own page for displaying a single activity, they should have a filter here so they can perform their own checks if needed. There are many other boolean functions in wordpress as well as buddypress which have filters.

Thanks! It works. The whole code will be:

`function my_formatter($content) {
$new_content = ”;
$pattern_full = ‘{(\[raw\].*?\[/raw\])}is’;
$pattern_contents = ‘{\[raw\](.*?)\[/raw\]}is’;
$pieces = preg_split($pattern_full, $content, -1, PREG_SPLIT_DELIM_CAPTURE);

foreach ($pieces as $piece) {
if (preg_match($pattern_contents, $piece, $matches)) {
$new_content .= $matches[1];
} else {
$new_content .= wptexturize(wpautop($piece));
}
}

return $new_content;
}

remove_filter(‘the_content’, ‘wpautop’);
remove_filter(‘the_content’, ‘wptexturize’);

remove_filter( ‘bp_get_the_topic_post_content’, ‘wptexturize’ );
remove_filter( ‘bp_get_the_topic_post_content’, ‘wpautop’ );

add_filter(‘the_content’, ‘my_formatter’, 99);
add_filter(‘bp_get_the_topic_post_content’, ‘my_formatter’, 99);`

I am going to have to dredge up this topic again as I have gone through the process of completely reinstalling wordpress 3.5 and the latest version of buddypress 1.6.3 to a fresh new Ubuntu server with only my custom theme, database and alterations to buddypress that were not in the buddypress core file (obviously since the old one has been nuked) and I am still getting a 404 response (from within our wordpress page, not an apache 404) whenever I try to edit, sticky or delete a topic in the forums.

this is still the case even with the default buddypress theme.

This is a buddypress set up to do groupt forums, not sitewide and I do not have bbpress running at all (though interestingly enough, when bbpress was running alongside buddypress, I was not getting our site’s 404 response, but was getting a new topic form and the notification of “Oh bother, there are no topics here” – 0r something like that)

would really like to get this figured out as it is pretty critical and I don’t know how else to debug this (there has to be *some* clues as to why this is happening.)

thanks in advance.

Thank you @mercime.

A small follow-up question on user sign-on/registration. As you clarified, there is a unified login for all wp and bp/bb components. Does it mean that the user profiles (wp profiles and bp extended profiles) are also unified/sync’d?

With regards to the twenty twelve – Buddypress compatibility, let me elaborate my set-up a little.

Twenty twelve is not compatible with buddypress out of the box (like bp-default theme is), so one needs to use bp-compatibility-pack plugin (or can be done manually) to copy-paste buddypress specific .php templates and other files to the theme directory. This also includes buddypress style sheet (bp.css) which seems to be a copy-pasted part from bp-default style.css.

Thus, when you make twenty twelve compatible with buddypress (I am doing this on child theme of twenty twelve), the styles of buddypress components resembles to bp-default (rather than twenty twelve). If one deletes all the css from bp.css, one gets plain styles (these are twenty twelve styles but as there is nothing in twenty twelve styles for bp, they are as good as plain). Fixing these plain styles would be like making a completely new theme from scratch (like styling _s theme) for bp component pages/sections. There doesn’t seem to be a simple workaround about this.