You’re right. It does show blank in Firefox, but displays for IE.
@maineyak No it’s not blank 
Curious, what browser are you using? You’re the second one who mentioned that codex page/s are blank. Answer posted.
In some server environments, installation of BuddyPress can lead to blank pages. A great source for troubleshooting this problem is the error logs.
Memory Limit
Increasing the available memory may fix the blank page problem. Three methods are available for increasing the memory limit.
php.ini
If possible, increase the memory limit within the php.ini file.
wp-config.php
If possible, increase the memory limit in the wp-config.php file by adding define ('WP_MEMORY_LIMIT', '64M');.
.htaccess
If possible, add the following to the .htaccess file: php_value memory_limit 256M
talk to your host
If you cannot resolve increasing memory with the fixes above, it means that your hosting provider prevents increases in memory limits. Contact tech support right away. Some hosting providers might require you to upgrade your plan or pay extra.
clear your browser cache or try another browser
After increasing memory, be sure to clear your browser cache. Also, troubleshoot multiple browsers and multiple user roles (subscriber, author, admin, etc.)
I really appreciate your assistance drill-sgt.lewis, and sorry for wasting your time ;/ . It was a theme issue – I can’t isolate exactly what had done it, but the default layout for buddypress pages had been changed and was resulting in blank pages.
Status theme is for IE 9 above https://github.com/buddypress-themers/status/blob/master/readme.txt
To fix it for IE8, you need to use Firebug, the Firefox add-on, to identify the HTML tag which you would need to style. Last time I looked, this would involve adding specific width to the element. which was floated left.
@ds123 what theme are you using? Change to bp-default theme to check if issue is resolved.
B. COPY sidebar.php and Save As > sidebar-buddypress.php file
Open up sidebar-buddypress.php and at the very TOP of the file above all other code, add:
`
`
At the very BOTTOM of the same file, below all other code, add:
`
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 file.
C. Upload header-buddypress.php and sidebar-buddypress.php to your theme folder in server wp-content/themes/vagenta/ in the same directory where your regular header.php and sidebar.php files are
D. Final note: Copy the style modifications for some BP elements https://codex.buddypress.org/theme-development/theme-dev-bp-template-pack-walkthrough-twenty-ten-bp-1-5/3/ and paste those at the bottom of your theme’s stylesheet, then adjust to taste.
@misterhill You only need to create two new files, header-buddypress.php and sidebar-buddypress.php to make your theme compatible with BP.
If you’ve revised any of the BP template files transferred to your vagenta theme folder in server during the BP Compatibility process, please delete the 6 BP folders transferred to your vagenta theme folder in server – /activity, /blogs, /forums, /members, /groups, /register – then re-run Appearance > BP Compatibility again to make sure that you have clean template files.
A. COPY your theme’s header.php and Save As > header-buddypress.php
Open up header-buddypress.php and at the BOTTOM of the file, below other code contained within, add this:
`
@zaniwhoop please start a new topic next time. The code used from 2 years ago won’t work for current BP versions. Closing this one.
For your reference, this tutorial by pcwriter is pretty thorough http://wpmu.org/how-to-build-a-facebook-style-members-only-wordpress-buddypress-site/
@raminjan Sorry, not sure what you mean. Please clarify. By “wordpress buddypress comment box”, are you referring to the comment form in BP Default theme’s single.php file or to the Activity Stream comment form or something else?
Thanks @sooskriszta
Thought for a while it was about bbPress.org which has no groups 
Why do y’all think calling people names is going to help anything? That’s pretty silly.
Closing this topic, since it’s another one that’s all about criticism, and not about execution.
@mercime – Thank you so much for your time and assistance – I really appreciate it. Changing only 3 files sounds much better
I havent changed anything in the header-buddypress.php and the page.php that I pasted earlier, so the other pages you require are as follows..
index.php http://pastebin.com/YSapbSr3
loop-page.php http://pastebin.com/eRfPRvZP
sidebar.php http://pastebin.com/DsFKfk7k
footer.php http://pastebin.com/RuyJN18v
SKParticipant
Codex pages can be created through wp-admin, like any WordPress site: https://codex.buddypress.org/wp-admin/
Anonymous User 96400Inactive
@hnla
I do see the point and I did not mean at all that we don’t need a codex. I was merely replying to an earlier comment.
I have a custom menu but created long ago. In buddypress settings the component directories are set to active pages for activity streams, discussion forums, user groups and members.
Problem extends beyond this to main buddypress menu at top right of screen where profile edit etc are all blank too (not 404 page not found though). I have an active members widget in a sidebar which does actually work so i agree that it seems like a links issue – but the correct page URL displays when links are clicked.
@travel-junkie Lack of documentation will not necessarily turn developers away but generally the degree to which something is well documented is an indication of how things stand overall and reading how something flows, what is possible or not, is easier than having to trawl through core code to work it out, yes we can and do do that but being able to does not replace or negate the need for a good set of dev docs and having to trawl through core code because there aren’t docs available will turn away many developers..
Anonymous User 96400Inactive
@mercime
Linking to a wikipedia article will not, apparently, get you any brownie points with @ethanvan
@ethanvan
Just start writing on the codex. If you can’t cause of permissions or whatever, let the core team know and they’ll sort you out. This is a community-driven project. The more you participate, the more you’ll be recognized. Being disrespectful to people that have already shown their dedication and involvement will only make you look weak.
A codex is a valuable thing to have, no doubt, but I don’t believe that the lack of one will cause developers to turn away from the project. If you can write code then you can read and understand code. If you work with any of the dozens of IDEs out there, then any function, class or method is only 1 or 2 clicks away. That way is quicker than trawling through the codex, WP or BP. For me anyways.
Have you made sure the buddypress pages have been actively associated with the links? Have you created a custom menu in the dashboard? If the pages are not associated with these then you will get a page not found error.
I like the admin bar options as it’s so much easier and faster than having to go to the dashboard and then search for them and then delete.
The toolbar was much easier.
