Got impatient. Deleted everything and reinstalled, since I didn’t have that much content anyway. Still have a problem with pernalinks whether the plugin is there or not. I’m using “BuddyPress Twenty Ten Child 1.0” by bp-theme-converts for my theme.
Go back to a base WordPress install with the default 2010 theme. Then try to set custom permalinks to /%category%/%postname%/
Does that work? Can you go to categories and posts without problem?
If not, it is a problem with your server setup for WordPress and nothing to do with BuddyPress. You should fix that problem before attempting to use BuddyPress
As rogercoathup mentioned, before installing BuddyPress double-check if your WP installation is up to the task.
<snip>permalinks other than the default setting. But when I do that my links to my pages don’t work. What to do?
And when on the permalinks screen and having saved new settings what does the screen say? Are there any messages?
Thanks much for the suggestions. But I tried them and get the same results.
I deleted the plugin, reverted back to the WordPress Twenty Ten theme, and am working with the initial wordpress installation, that is, I have never posted or created any pages. The problem persists. When I go to edit the About page without actually editing it, just clicking on the “View Page” button. I get this message:
Forbidden
You don’t have permission to access /about/ on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Apache/1.3.33 Server at neighborsconnect.us Port 80
Same thing if I am on the home page and click on the About in the horizontal menu beneath the header.
That happens with any permalinks other than the default including the custom /%category%/%postname%/ .
And the browser window reads” url/About.
I don’t get any messages when I change the permalinks.
Then you have a WordPress / server config problem. You should fix this before installing BuddyPress.
You need to ask your server company and / or go onto the WordPress forums
Thanks Roger,
I posted the problem on both sites since I didn’t know where the problem was, but the above troubleshooting as you say indicates it’s a WordPress / server config problem. The exchange was much appreciated. Thanks again.