Hello
I am having the same issues, the problem is IIS6 does not support url rewriting use the free program and information here http://www.helicontech.com/ape/
I am getting there with my buddypress install but am not yet there fully as some of the links still don’t work, the create a group is one of them, its all down to writing the .htaccess file in the correct way to make all work.
Hopefully this has helped you a little
Regards
Webdoc
If you are still getting errors even after URL rewriting is set up, try the solution in this thread:
https://buddypress.org/forums/topic/friendly-http-error-messages-causes-404
Its a nightmare if your on shared hosting!
https://trac.buddypress.org/ticket/2208
Hello,
downloaded BP yesterday, no probs, thanks for the easy set up.
i upgraded BP this morning and the sign up icon on the home page disappeared.
i can’t find it anywhere and didn’t see any posts about it.
any help is appreciated.
thanks
EDIT:
It was the Buddy Press Maps I upgraded today.
I’m having the same issues (and looking at the number of similar posts under a variety of headings, so are many others). My website is waterwaywatch.org.
I provide the following detail in case someone can figure out what the problem is.
What seems to be consistent is Home and About work whereas Groups, Members, Activity and Forums give either a 404 or report page not found. The urls that fail are mydomain/menuitem/ but usually if one inserts index.php like this mydomain/index.php/menuitem/ then one gets a page that seems to be a template for either Home or Activities but without any content. This page is always the same regardless of the menu item selected.
this are wp/wpmu issues.
Try better here:
https://mu.wordpress.org/forums/tags/iis
I’ve gone through all the BuddyPress files and inserted ‘/index.php/’ after each of the root_domain elements and that fixed it.
. clean_url( $bp->root_domain . '/index.php/' .
Someone else could probably suggest a better way of doing it that links into WordPress’s permalink structure.
The index.php one is not necessarily to do with IIS; see https://trac.buddypress.org/ticket/2552
