bbPress 2 autocloses posts after a configurable period of time, so it’s got you covered.

BuddyPress makes a lot of MySQL calls. Those aren’t replaced by the pg4wp plugin.

1) Change titles using language translation file – https://codex.buddypress.org/extending-buddypress/customizing-labels-messages-and-urls/

2)
a) Setup forum without groups ==> Yes. Install Sitewide Forums via dashboard BuddyPress > Forums https://codex.buddypress.org/getting-started/installing-group-and-sitewide-forums/
b) Use Groups as Categories ==> Coming up in BP 1.6 or so per roadmap.

Great. Simplifying is better

> Running WP 3.2.1 and BP 1.5 — I know these aren’t the lastest versions, but I’ve made enough changes to the core to accomplish my needs that updating would prove problematic

If you changed BuddyPress, what did you change? Are we missing a filter or action somewhere that would allow you to avoid hacking core?

@kunthea, please make your own topic rather than hijack someone else’s.

Hello there,

I am new in this forum.

I have installed buddypress to my second subdomain as http://khmertrips.com/community/, so anyone know that, where could I found code or RSS to display do *Activities stream* of buddypress to my homepage of http://khmertrips.com/travel/ as i use both subdomain in wordpress soft.

Thanks/Kunthea

@mercime we’ll have to see if jjj can pinch that plugin from wp.org auto closing of older threads would be good, but for those that we can directly attribute a thread [resolved] tag to we close them at same time?

Hadn’t considered the theme compatibility threads needing to be open, but in regard of those it has struck me that really the main core of those threads ought to be removed and pasted into a codex sub page running under theme compatibility, so that you have a generic steps and code for a given theme conversion – users could still add updates etc to a codex page.

B. At the bottom of the same 16 files, replace:
`

`

with the following (except for registration/register.php):
`

`

with the following for registration/register.php:
`

jQuery(document).ready( function() {
if ( jQuery(‘div#blog-details’).length && !jQuery(‘div#blog-details’).hasClass(‘show’) )
jQuery(‘div#blog-details’).toggle();
jQuery( ‘input#signup_with_blog’ ).click( function() {
jQuery(‘div#blog-details’).fadeOut().toggle();
});
});

`

Save files.

C. Upload the 6 BP folders containing the 16 files you’ve just revised to your server wp-content/themes/neu/

D. Copy the style modifications made in BP Twenty Ten at https://codex.buddypress.org/theme-development/theme-dev-bp-template-pack-walkthrough-twenty-ten-bp-1-5/3/ and paste to your theme’s stylesheet. Adjust to taste.

Based on the HTML structure of your theme, you need to use the first option, i.e., change 16 template files within the 6 BP folders transferred to your Neu theme folder in server during the compatibility process.

If you’ve previously changed any of the BP template files in your theme folder, replace all of them for a clean slate by deleting the 6 BP folders in server – /activity, /blogs, /forums, /groups, /members, and /registration – then re-run Appearance > BP Compatibility.

Download the 6 clean BP folders to your computer hard drive. We’re going to use the basic HTML structure of your theme.

A. At the top of each of those 16 template files I linked to above, replace
`

@venusd no problem. Just to sure, could you post the source codes of your theme’s header.php and loop-page.php to pastebin.com or tinypaste. Please feel free to donate to the American Red Cross Thanks.

== Linux. Single WP. WP/BP is installed on the domain root. ==

Deactivate plugins esp. membership plugins and re-upload BuddyPress then activate bp-default theme.

== that sitewide forums was a known issue that was expected to be sorted out by BP 1.6 =

There have been some who posted in our forums about issues with getting both working at the same time. Some have been resolved by reinstalling WP manually instead of using webhost script to install WP. Many have been resolved by changing the Archive base slug of Sitewide Forums to avoid slug conflict with Group forums, etc. then adding the bbPress shortcode/s.

As for BP 1.6, it’s in the roadmap to migrate existing Group Forums into Sitewide Forums.

What could very well be causing your issue is that you used a webhost script to install WordPress in the first place and it could very well be causing issues with your BuddyPress installation – see https://codex.buddypress.org/getting-started/before-installing/#system-server where “WordPress should be installed manually i.e. via FTP, cpanel, etc. and NOT via webhost scripts which bring about numerous issues when BuddyPress is activated.”

@niwaroll Next Avengers cast eh? Thanks, glad it worked out for you

@venusd
– I recommend that we remove the featured area atop the “About” Page content like it’s done http://demo.colorlabsproject.com/neu/about/ and showing up in the Page template you posted per link above
– Plus, you’ll need some horizontal space for the BP components, so I suggest that we remove that categories column/widget on the left of the content area
– so before I proceed, are you okay with the recommendations above?

@hnla sounds like a good plan especially for topics posted from more than 6 months ago ago. We need a plugin to close forum topics automatically ala WPorg forums after a number of months/a year I think. Since group forums are moving over to bbPress plugin, then a plugin for a plugin

In the meantime, I need exceptions for theme compatibilty topics where a few users have even volunteered improvements to styles, structure, etc. among others. Come BP 1.7 or so with theme compatibility set up, I will make sure to close those topics.

” they apparently have access to my dash board. Does anybody have an idea how to set things straight on this issue?”
They sure do. They don’t see anything though – https://buddypress.org/wp-admin/index.php

if it’s an issue, you could code it really easily…
`function get_out_dude {
if(is_admin & !current_user_can(‘editor’)){ //if we are inside wp-admin and user is not an editor
wp_die(‘get out of my bedroom.’); //lets kill everything and tell the user to get out.
}`
* written quickly. don’t trust the code.