shouldn’t BuddyPress create those pages automaticallyyes, but only when it is the first install. As you sed a member plugin previously with a page name member, BP didn’t create one as it already exist. But BP doesn’t check for existing plugins, just for “his” pages.
Anyway, as you added BP, than reinstalled or reactivate, the page was already registered in the wp_post table, with a post_type of ‘page’ and a post_status of ‘publish’.
Also, in the WP system, when a page is in the trash, it is not deleted. The page is still in the table, but with a post_status of ‘trash’. To remove it completely you need to delete it permanently. Click on trash and use the appropriate button.
Now the issue. You have 2 member pages. The one has a slug /member/, the other has a slug /member-2/.
The one may show in the pages list and the other in the trash. This naming is the internal way used by WP to differenciate 2 pages with a same name. That’s fine, but BP dosn’t know about that, and you can run into trouble because of this. And other plugins also.
Ensure you have only one page called ‘member’ and clear the trash. And delete completely the other one. Do the same for any other BP page eventually. The principle is to have an unique page name in the pages list and no identical page in trash.
Yes you have to create these page manually now. By default, each component should have one page assigned. On a standart install, you should have at least:
members – activity. If activated, group. And depending of the previous status of your WP (before BP installation) a page for activation and registration. If not in BP’s page settings, you have to add them manually.
Note also that all these pages exist only to give a slug to each component. These page are not ordinary WP pages, but slugs placeholder used internally by WP to connect the components.
That’s why they should exist, be blank and without any model or template assignation.
The content is added dynamically by BP for each component with the appropriate template to the current action.
e.g. the member page. You can name it to what you want. Lets say you called it crew. His slug is /crew/
When typing your-site.xx/crew/ you will see something related to the member component.
The member directory is default: your-site/crew/ will show all your members
Now you want to see a profile. The slug wont change, but only the action.
Again your-site/crew/ (the default slug, aka page) and the new action: go to the profile of /username/
Click on a member name and you’re now on his profile: your-site/crew/username
Now from the profile you want to see that users friends.
your-site/crew/username/friends
As you see, you’re always on the same “page”, but with different content depending the context. This context is defined by anything appearing after the slug name.
This behave is the exact inverse of a traditionnal WP page, intended for so called static contents such as about page or TOS and similar stuff.
Hope this point is now clear to you.
