yes buddypress 1.2.8 I looked at the particular line it was talkin about in the error and here is the whole function where the error started….
if ( (int)$this->total_member_count && (int)$this->pag_num ) {
$this->pag_links = paginate_links( array(
‘base’ => add_query_arg( ‘upage’, ‘%#%’ ),
‘format’ => ”,
‘total’ => ceil( (int)$this->total_member_count / (int)$this->pag_num ),
‘current’ => (int)$this->pag_page,
‘prev_text’ => ‘←’,
‘next_text’ => ‘→’,
‘mid_size’ => 1
) );
@boonebgorges not at all, thanks for response boone. I will.
I’ve just realised, through flushing cookies to check again, that these errors are thrown only for logged in users, and in a logged out state, several previous errors no longer get flagged (which is often the way when one thing is predominant in tripping up the validator). When I’m logged out, the output is entirely clean for Tranisitonal, and certainly tweakable for Strict.
Paul,
Thanks for your suggestion. I deleted .htaccess, restarted Apache, did the permalink switch and changed it back, and saw that the .htaccess file was regenerated, but it didn’t fix the problem of getting 404s on everything but the home page.
I’m beginning to wonder if it’s the host. Problem is, the particular (corporate) hosting package i’m using (SAVVIS) is such that I’m responsible for all apps. They don’t support anything above the basic OS setup, so I can’t turn to them for troubleshooting. However, if you can think of anything at the network (maybe the firewall settings?) or OS level that I might be missing, then I could ask them to troubleshoot that part of it all.
I think you’re probably right that this should be a class rather than an id, but it needs a bit more of an audit (in particular, a sweep through the rest of the core code to ensure that changing it to a class selector wouldn’t break everything else). @aljuk, would you mind opening a ticket on trac.buddypress.org to that effect, using the same username/pw as you do on this site?
@stevieg, there is nothing more that you are required to do than to remove the WordPress Admin bar, that they added.
Don’t get worried over nothing, updating to wordpress 3.1 is safe, it’s been a fare share amount of time since it was updated, so plugins can update their compatibility with it also.
may install in one site of multi-site wordpress, only? better install in wordpress only one site, or it does not matter?
bp-default is running XHTML 1.0 Transitional and therein lies the big difference.
I’ve got my custom bp-default child theme (BP 1.2.
passing validation, no errors. In addition, http://testbp.org, BuddyPress’ demo site using bp-default theme (BP 1.3 trunk) has only 2 errors on Activity Stream because of html5 element “role” which is not recognized in validator
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Ftestbp.org%2Factivity%2F
=== just want to find a good theme that i wont have to edit soo much. ===
Check out http://www.arrastheme.com/forums/ for tips on how to make theme compatible with BuddyPress. Changes mainly on HTML and style.css. It’s not soooo much 
Thank Virtuali ( @gunju2221). I really appreciate it, I will have a look at the code as soon as possible. Thanks again
Specifically, I get this message sitewide:
401 Authorization Required
Invalid login credentials!
an not everthing lines up. when the group widgets dose let you look at new old it just take you to group. just want to find a good theme that i wont have to edit soo much.
Thanks Paul. I did find https://wordpress.org/extend/plugins/shibboleth/, but installing it broke my .htaccess file for some reason (I couldn’t log back in to the site). I had installed 1.2.7, 3.0.4.
Don’t worry about BuddyPress for this, just look for WordPress plugins that enable shib login.
Delete your custom .htaccess and use the default (go into wp-admin permalinks, change it to another setting, then save, then change it back to what you want the permalinks to be. This should regenerated htaccess).
This is not a BuddyPress issue and better addressed at WordPress.org forums – https://wordpress.org/support/forum/plugins-and-hacks
single user or multiple users
with this you mean roles/permissions/users?
I have tried adding all these settings, selecting all different forms of pretty permalinks, relocating my .htaccess file to various locations throughout the /var/www/html hierarchy, and restarting httpd over and over again, but none of them have worked.
The only other thing I can think of is that at one point I was using a symlink to point documentroot /var/www/html/wp to /data01/home/username/production/wp (i.e. /var/www/html/wp –> /data01/home/username/production/wp). Right now, documentroot points directly at /data01/home/username/production/wp for the VirtualHost DocumentRoot directive without using a symlink. I still can’t get WordPress posts or buddypress activity, group, member, etc. pages to appear. All 404s.
Any ideas of other things I could try?
1. Themes
Current gallery/media plugins (free and paid) compatible with BuddyPress use the bp-default theme structure. So either you create a custom theme that’s a child theme of bp-default theme or be prepared to customize any other WP theme or custom BuddyPress theme to work with the gallery plugin’s.
2. Image storage
Images are physically stored in your server for some gallery plugins. Other BuddyPress-compatible gallery plugins require you to store your images in their servers and make you pay for extra storage.
== HOWEVER, in the version of BuddyPress running on our site (version 1.2.5.2) I can’t find any directories named bp-members/ at all! Have I gone mad? Has it been moved somewhere else? ==
`/bp-members/bp-members-signup.php` is one file of the very new BuddyPress Members component. Therefore the folder is not even in BP 1.2.8 and only currently available in BuddyPress trunk at this time https://trac.buddypress.org/browser/trunk
@christophG
You can do this with the s2member plugin. In the “API/Scripting” section, you’ll find some advanced conditionals that can be added in your theme templates, or included in a custom function. If you’re using s2member, you could try adding this to your theme’s functions.php file… should work anyway 
`function remove_member_profile_nav() {
if (!current_user_can(‘access_s2member_level1’)) {
bp_core_remove_nav_item( ‘profile’ );
}
}
add_action( ‘bp_setup_nav’, ‘remove_member_profile_nav’, 15 );`
