Thanks for the response jaredatch, but I’m afraid it doesn’t work. I’d done it before, but I just tried again to be sure. I disabled all plugins (aside from bbPress) and refreshed the permalink structure. Still no dice.
I don’t have a post or page with “users” as the slug. Just to be sure I went into the forum settings and changed the ‘User base’ to something else (“userxyzwq” – definitely nothing else on the site called that!) and it still threw a 404. Changed it back, the same. Switched off the ‘Forum Prefix’ as someone suggested, and still the same.
Very frustrating as I spent a good while getting everything else working. And, as I say, even though the 404 status is being returned in the header, the page still appears in most browsers… which is confusing the hell out of me.
And sadly it’s not something I can just live with, as “most browsers” isn’t good enough for this project.
Bump. I’m going to refresh this topic once in the hope that someone can help (with my query, above). If not, with regret, I’m going to have to abandon bbPress and try some other forum plugin. bbPress does almost everything I want it to, but obviously the 404 error for user profiles makes it unusable.
Anyone?
I’m also experiencing this problem. Having installed the bbPress plugin (2.02) on my WordPress site, I’ve managed to get almost everything working. However, when I try to view a User Profile (http://site_url/users/username) I get a 404 error – but only for ‘Forum Participant’ members (not admins).
I do not have any other membership plugins installed. It happens for members created without spaces in their usernames (which was one suggestion), and it happens even if I switch off the “prefix forum area with forum base slug” and recreate the forum, as suggested here.
Does anyone have any ideas?
EDIT: one other point, and it’s an odd one, even though the page shows a 404 error in the headers, it displays fine in Chrome and Opera. However, it does not initially display in Internet Explorer 9 and shows a browser 404 page, but it does show up after two refreshes (though not 1). Go figure.
