BuddyPress.org

… and so you open up your instyle’s page.php file and compare the HTML structure of that page file with the HTML structure of the template files transferred to your instyle theme folder during the BP template pack process.

For more info about the whole process and a sample walkthrough:
https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

Only way your files can get written to is by someone getting your FTP passwords or has access to server. That is easily done if you get a virus/malware on your computer. Is somebody else accessing the FTP on another computer? Also, bad themes and plugins can do this as well. NEVER use a plugin or theme that was not from a reputable developer or from the WordPress repo.

You most likely have a trojan on your computer that stole your FTP passwords. If you are on a windows PC take a sledge hammer to it and get a MAC. <– just kidding. You should run some anti-virus and change all your passwords ASAP.

https://codex.wordpress.org/FAQ_My_site_was_hacked
http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
http://ottopress.com/2009/hacked-wordpress-backdoors/

Very strange. The fact that you’re having problems with the email notification of blog comments shows that this is not a problem with BuddyPress, but is some combination of your server, WordPress, and possibly Yahoo Mail.

Have you tried reading the problematic mail through another method? POP3 or IMAP? Or maybe the same email sent to another provider like Gmail? At least that could rule out the mail client.

You might be interested in CloudFlare. This will help with security as well as CDN. In the meantime, there is a plugin for wordpress that will help you analyze load times:

https://wordpress.org/extend/plugins/wptuner/

This isn’t exactly what you asked for, but in lieu of that this will at least encourage completion.

https://wordpress.org/extend/plugins/buddypress-profile-progression/

You’re right it could be better commented, but in BP’s defense, this is a core WP functionality, and part of just about every modern theme https://codex.wordpress.org/Template_Tags/wp_list_comments

This could be helpful too https://wordpress.org/extend/plugins/buddypress-restrict-group-creation/

Which comments are you talking about ?
Blog comments ?
See here: https://codex.wordpress.org/Function_Reference/comment_time

To do this, If you use BP 1.2.8, go to bp-themes/bp-default/functions.php or better to the functions.php of your child theme

In file there is a function bp_dtheme_blog_comments
Near line 78 change
`

to this

`

how to embed this function into your theme’s function ? read here:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-do-you-do-this/

So try this:https://wordpress.org/extend/plugins/register-plus-redux/

http://www.wordpressvsjoomla.com/

And you know that even network activated, all users have their BP profile on the main site?

BuddyPress is network-wide, not blog specific.

“One way you can prevent BP in main site or secondary site from importing data from all sites is by marking e.g. My Blog in Settings > Permalnks – “I would like to block search engines, but allow normal visitors” or even choose additional options with https://wordpress.org/extend/plugins/more-privacy-options/&#8221;

Which blocks search engines as well. Better off to mark the blog as mature instead.

It’s the same steps.

http://wpebooks.com/2010/09/how-to-enable-multisite-in-wordpress/

If you disable BuddyPress, can you register such a name with just WordPress?

If you can, we have a bug. If you can’t, then WordPress doesn’t support it.

Then as nexia mentioned above, that is a custom job. BP is network-activated i.e. by default for all sites of a multisite installation.

One way you can prevent BP in main site or secondary site from importing data from all sites is by marking e.g. My Blog in Settings > Permalnks – “I would like to block search engines, but allow normal visitors” or even choose additional options with https://wordpress.org/extend/plugins/more-privacy-options/

=== i want to disable the hole buddypress stuff to get a clean wordpressblog to use my old and self styled wp-theme. ===

Do you mean you want to delete BuddyPress? https://codex.buddypress.org/buddypress-site-administration/deleting-buddypress/

First pass at this is now in BuddyPress trunk. It relies on this WordPress core patch to prevent the following from occurring:

To see my approach in code, check out r4151 and r4152

== I have 40 entires as custom post types in a custom directory lists. ==

Supposed to be that Custom Post Types could be exported in Tools > Export from old site and then use Tools > Import WP WXR in new site. I haven’t had the occasion to test it yet, but per this WP trac, it’s supposed to have been fixed already https://core.trac.wordpress.org/ticket/14306. The best bet would be to check it yourself in a test install or in your new one at the other domain.

== I had no idea Fantastico was so bad, are lots of people finding holes in it? ==

It should be outlawed

btw, as i’m working on a tool right now that integrate the Buddypress Adminbar inside the official WordPress Adminbar, here is the setting i added when thinking of you:

http://nexialys.net/nex_bp_adminbar/nex_bp_adminbar_settings.png

@rossagrant shucks, before you mentioned that changing usernames/passwords affected all other themes, I was going to write that you should get theme support from @Bowromir again

Seriously though, there’s a silver lining to discovering about the perils/shortcomings of Fantastico this early in your installation – knowing never to use it again for another developer installation as @nexia said. There are many who have posted their woes in WP.org forums. Shaving off a few minutes of uploading WP manually, creating a database and installing WP is not worth the hours wasted on a shaky foundation set up via Fantastico.

At this stage, it’s a blessing you only have 4 members a few groups etc which you can recreate later on. So it would come as no surprise that I would recommend starting your installation from scratch – clean and solid – after making DB and server files backup (just in case). Contact your webhost tech support on how to delete WP and Fantastico files properly. There’s one topic in WP.org forums which gives a clue but no actual solution https://wordpress.org/support/topic/fantastico-problem?replies=1 so you need your webhost tech support on this one.

Read this post from @sbrajesh.. it’s extremely helpful!

WordPress Multisite 3.1 and fixing the problems with BuddyPress dependent plugins