BuddyPress.org

Cool! Back in the Dashboard, pick settings again and find “Permalinks” in the list. In the permalinks options, choose a link setting other than the default. I prefer the “Post-name” one, myself. After you save your changes you should be set.

BuddyPress requires “pretty permalinks’. mod_rewrite should be enabled

In your dashboard, go to settings and select “BuddyPress”. You’ll be brought to the BuddyPress options page. Select the tab titled “Pages”. From there it will help you create the needed pages and associate those pages with the BuddyPress components 😀

Yeah, happens to me too. More annoying than critical; we’ll take a look soon.

Hmm.. do you know how to use MySQL? If so, looking up one of those activities in the DB table (wp_bp_activity) and seeing what the quote mark is written us, would be helpful.

@jase-cook If you don’t need group forums and plan only to have sitewide forums, then go to admin Settings > BuddyPress > Components and uncheck “Discussion Forums” https://codex.buddypress.org/user/setting-up-a-new-installation/configure-buddypress-components/#settings-buddypress-components

As for the sitewide forums, the default slug is forums. If you want to keep that, then leave as is. If you want to change it to something else e.g. “Discussions”, change the forum slug in Settings > Forums, then create a new Page named Discussions. Add bbPress shortcode like [bbp-forum-index] or choose from https://codex.bbpress.org/shortcodes/

There’s a record in the user meta table that would need to be set (‘bp_last_activity’). Try https://wordpress.org/extend/plugins/activate-users-in-buddypress/ and see if it’s working.

@sn0zb0z

1. create a child theme of the BP Default theme https://codex.buddypress.org/legacy/building-a-buddypress-child-theme/

2. copy over index.php from BP Default theme into your child theme folder and change the_content to the_excerpt

the only one that looks wrong to me is the last entry the earlier entries appear correct.

TurtleBoy wrote a new post, “Son Of Rambow” (2007)

Good evening @djpaul @mercime @chouf1

Now i think this little plugin really rocks 🙂

as it can play with bbPress 2.2.3 or BuddyPress 1.5 to 1.7 (group forums or bbPress ones)

here’s 1.0-beta1 of “buddy-bbPress-Support-Topic”.

Some info about this new release :

• works in bbPress 2.2.3
• in topics backend list, adds a column to tell if the topic is a support one
• in topic backend edit screen, adds a selectbox to set the support status into the first right metabox
• in forum topic list on front end adds a mention about the status of the topic for support topics
• in forum topic single view, adds a select box to “ajaxset” the status of the support topic.

You can also style the mentions with a button effect or simple color :

`
//for example
.topic-not-resolved {
color:red;
}

.topic-resolved {
color:green;
}
`

if you find any bug please let me know, i’ve tested it on these configs:

• BuddyPress 1.7, bbPress 2.2.3
• bbPress 2.2.3
• BuddyPress 1.6.3 with “old” group forums

could be a language setting thing have you double checked that?

Still can’t find this plugin. @modemlooper, any chance you could reupload it to the repository?

@digitman2

I’m testing it in a LAN environment with activity and members link so that anyone that is not logged in, they are unable to see those section and it redirects to registration page. Just one suggestion but maybe other suggestions easier.

figured you might say that unfortunately if your existing plugin doesn’t support buddypress functionality then that sort of puts you in a box. if you decide to keep your existing plugin then you will either need to find another way to implement the restrictions (not likely to be easy), wait for the plugin to support buddypress or reassign your user levels with a plugin which does support blocking BP pages such as s2 member. maybe someone else who knows more then i do will have another idea but that’s all i got.

You couldn’t find this?!

https://buddypress.org/support/topic/how-to-make-a-private-community/?topic_page=6&num=15/#post-86316

Obviously play around with the code to get what you need  but that’s the basic principle for a re-direct away from pages wanted to be made private.

Create the patch from changes made on a copy of BP trunk checkout from the repo then attach the patch file to your ticket, then we can apply the patch to our trunk checkouts.

‘Trunk’  is effectively 1.7 and represents all the code that will be released as 1.7 when ready.