BuddyPress.org

@jstebbing better late than never
`add_filter( ‘bp_get_group_description’, ‘do_shortcode’ );`

Thanks @israelwebdev

I am quite a beginner. Could you explain how to integrate this code into Buddypress? EG where to paste it in functions.php

Do you have a working example on your site?

I don’t understand what you mean by ‘bunches’….

If you look at the wp-config-sample.php it should have a text block at the beginning like the following (quoted from wp 3.1.2)
`
<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information
* by visiting {@link https://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/
`
those /* and */signs mark the beginning and end of text blocks that should be ignored in a .php type file…. ( this also true for single lines beginning // )

Make sure that is the case with your config file.

To edit php files you should use a text editor such as notepad++ rather than a wordprocessor such as MS Word.

Not sure why your ‘site’ redirects to facebook but in that it does it’s not especially helpful in order to see the issues to which you refer

No, it’s not available.

I need to know the same thing. There is a much shorter code to use to get the album images at http://zacharydenton.com/how-to-display-buddypress-album-images-anywhere/
But there is no pagination to display more than the number defined per page on the first page.

I have also tried the wp-pagenavi plugin, this didnt work either did the standard pagination from twentyten WP theme

Hi i am having the same issue with replying to peoples post in activity…

Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/wp-content/plugins/buddypress/bp-themes/bp-default/_inc/ajax.php:142) in /home/xxxx/public_html/wp-includes/pluggable.php on line 693

Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/wp-content/plugins/buddypress/bp-themes/bp-default/_inc/ajax.php:142) in /home/xxxx/public_html/wp-includes/pluggable.php on line 694

Warning: Cannot modify header information – headers already sent by (output started at /home/xxxx/public_html/wp-content/plugins/buddypress/bp-themes/bp-default/_inc/ajax.php:142) in /home/xxxx/public_html/wp-includes/pluggable.php on line 695

I have also downloaded the new file and checked for any whitespace and was unable to find any.

If it doesn’t already exist you can just add

define('WP_MEMORY_LIMIT', '64M');

to the wp-config.php in the wordpress root directory.

It needs to go somewhere above

/* That's all, stop editing! Happy blogging. */

There are situations where this won’t have any effect, so you could try asking your host to increase your wordpress memory limit, or do a search on that subject as there are other ways to do it yourself…

If that doesn’t work, and for some shared server hosts it won’t, then have a look at the suggestions here and here.

Or find a host that offers more memory – which could be difficult as all the other shared hosting services, that I’ve found, don’t quote the memory available in their advertising….

I was having this same problem and posted a lengthy comment about it in the trac ticket mentioned above ( https://trac.buddypress.org/ticket/2647 ), but in the meantime, I developed a workaround that works on my site and doesn’t require modifying any core files (and will fix the problem in any BP component, not just with friend request emails).

Just add the following function (a filter) to your theme’s functions.php file:
`
/**
* Intercept bp_core_catch_no_access() when nothing is set to enable smart login page redirects
* and prevent BP from just redirecting the user to the homepage
*
* @param string $found_template The result of locate_template() call
* @param mixed $templates Not sure what it’s for, but it’s generally bool false
*/
function yourtheme_load_template_filter( $found_template, $templates ) {
if ( ! $templates && empty( $found_template ) ) {
// just set it as default theme file so that file_exists() returns true
$found_template = get_stylesheet_directory() . ‘/index.php’;
}
return $found_template;
}
add_filter( ‘bp_located_template’, ‘yourtheme_load_template_filter’, 11, 2 );
`

It’s not a good permanent solution, but I haven’t noticed it affecting anything else (including BP 404s) on my site, and it leaves your BP install happily untouched. If the issue is fixed in the future, of course, I would highly recommend removing this fix, but as far as I can tell, it’s harmless, and certainly makes your site far more usable.

It’s on the BP 1.4 roadmap https://buddypress.trac.wordpress.org/ticket/2348 – BP Roles and Capabilities

https://buddypress.org/community/groups/installing-buddypress/forum/topic/windows-iis6-problems-404-error/ which leads to https://buddypress.trac.wordpress.org/ticket/2299

As I am not able to program this type of thing… Is there anyone out there that already has a patch/mod for this type of “super-user” for BuddyPress?

I need users that can edit moderate every group as well as make text edits and delete items in the activity stream, yet has not access to screw things up in the back-end, because they are “admins”.

@psivait

re spam: I would do a little research as there have been some lengthy posts on this question /issue here so dig those up and give them a good read, there are plenty of steps you can implement to reduce spam, however be aware that there isn’t much you can do about human spammers and they account for a good deal of time wasting these days especially if you allow for blogs to be created at signup (something I don’t personally think a good idea).

As for approving multisite blogs as a single super_admin I’m not sure you can or should, multisite blogs are meant to be fully fledged blogs in their own right and the user that creates the blog is the admin. There are however steps you can take as the multisite admin to restrict what can be done on user blogs but that is more a question for WP than BP. If your meaning that you will have members on your primary blog that is running the multisite install and you want to elevate them above ‘Subscriber’ level to say ‘Contributor’ so they can post then that can be done and can and submissions will be ‘awaiting admin approval’ which you will see if you run through the options in the dashboard with perhaps a test user with a ‘Capability’ higher than ‘Subscriber’