[HugoModerator @hnla 20 hours, 8 minutes ago]

Shouldn’t really call people specifically

However, perhaps you want to try using the WP login function over the BP login for ( if that’s what you’re using?) I have a reworked enhanced version of the older sidebar me login:
https://github.com/hnla/hnla-bp-sidebar-me

Logged out it uses the form as existed in the old sidebar.php with minor tweaks but essentially the same and it redirects to the front page. As an experiment I replaced it with the base WP function without any args passed to it i.e:
wp_login_form()

Now that logs me in at whatever page I’m on which is it’s default behaviour, and seems to work without any issues for BP as such (not sure about the cookie setting in the BP form though)

http://codex.wordpress.org/Function_Reference/wp_login_form

[HugoModerator @hnla 1 day, 2 hours ago]

I recently ran into the same issue – yes bp feels the need to strip out filters in theme compatibility mode as it feeds via the page content loop – I was pushing loop content through a do_action on a new group front page, my resolution was to re-instate the filter I needed ‘wpautop’ on ‘the_content’ just before my while loop then immediately after closing the loop I removed the filter again ( which could also have been via bp_remove_all_filters or add . Didn’t look further into this though.

[HugoModerator @hnla 1 day, 3 hours ago]

Switch to twentytwelve theme, does BP work correctly in theme compat mode, if so you have an issue with your theme but more information would be required in order to work out what that issue might be.

[HugoModerator @hnla 1 day, 5 hours ago]

You can prevent theme compatibility running by simply overloading those BP files as you did before in your theme root using full bp templates – in 1.8 we are looking to introduce the ability to overload templates in theme compatibility mode with files such as index-activity.php, index-component-profile.php etc:
http://buddypress.trac.wordpress.org/ticket/4639

[HugoModerator @hnla 1 day, 16 hours ago]

@nanaimomen You can grab a copy of this enhanced login and bp sidebar me widget- it has a few additions over what was normally found in the older bp version:

https://github.com/hnla/hnla-bp-sidebar-me

[HugoModerator @hnla 2 days, 4 hours ago]

What list? Where?

I don’t see this plugin on any list?

When you mention BP plugins page it sounds as though you mean this site here yet I see no mention of the plugin? Indeed this plugin isn’t even BP related is it?

[HugoModerator @hnla 6 days, 4 hours ago]

use character entities also if in doubt.

You’re lucky you can get in, I’ve been locked out from the codex for a week or so!

Before adding snippets to tricks & whatsists check what is permitted, as iirc some were stripped out recently.

[HugoModerator @hnla 6 days, 23 hours ago]

Nope. There’s no reason editing whatever file you are in that directory would break something unless you coded something incorrectly, or syntax wrong (but you should be warned of that)

[HugoModerator @hnla 1 week ago]

Not sure I understand the slight contradiction in ‘login on the front end’ = issues against ‘add a login plugin’ = no issues.

What do your server error logs say?

[HugoModerator @hnla 1 week ago]

@andy_blanc ok without necessarily knowing how the homepage was meant to look it wasn’t apparent their was an issue but as I see now a ‘working’ correctly? front page I assume you have things sorted, looking at the working page guessed the theme relied heavily on JS which was likely the issue but @aces I think nailed that issue down and you have dealt with and corrected, so are things now resolved?

[HugoModerator @hnla 1 week ago]

? what mode are you running BP in please – devil is in the detail we need detail on forum posts to be able to help.

The BP placeholder pages are meant to be empty, 1.7 theme compatibility uses page.php as it’s template wrapper, if you want to customize the BP aspects you can overload page.php with buddypress.php either in root theme or in dir under it named ‘buddypress’ or ‘community’ Check the codex for a fuller explanation.

[HugoModerator @hnla 1 week ago]

No they are filtered out. Needs a ticket raising no real reason why autop shouldn’t be allowed.

[HugoModerator @hnla 1 week ago]

I could open the link :p you move your mouse pointer over the text that’s red colour and push down the left button on…

@andy_blanc You need to be a little clearer about what is wrong also the index page isn’t showing BP content, checking BP content doesn’t show anything that wrong though, as for ‘responsive’ (a word becoming overused/misused) the theme hasn’t much beyond a little adaptiveness at a ~600px breakpoint, BP – as Merc – what’s a mouse – ime says BP should be fine with that in theme compat mode.

[HugoModerator @hnla 1 week, 1 day ago]

Not really clear what you’re trying to change, the head title tag, the members account screens bp_is_user, or members directory page title. As standard BP displays the users name on their user account screens or when you visit another users account, if your site isn’t then that’s a theme issue to ask of the authors.

You could use the below to get names, then what you do with that… :

$bp->loggedin_user->fullname

or
$bp->loggedin_user->userdata->user_nicename / display_name

[HugoModerator @hnla 1 week, 2 days ago]

You should be crashing & burning with:
$bp->loggedin_user['id']

It’s an object so should be this:
$bp->loggedin_user->id

Or better use:
bp_loggedin_user_id()

[HugoModerator @hnla 1 week, 2 days ago]

That is a sitewide notice, as far as I am aware that never did send emails just posted a notice on site. Oddly I was reading a copule of tickets or a ticket yesterday to understand what had happened in 1.7 and why the message had been fed through to wp_footer (r-a-y had a hand in it I believe ) Sure Boone mentioned some historic issue with BP suggesting it sent but never did and that action or part action had been removed.

[HugoModerator @hnla 1 week, 2 days ago]

Did you however scan that link I posted earlier on WP permalinks, I’m not sure the solution you have arrived at is a good one but I may stand to be corrected.

[HugoModerator @hnla 1 week, 2 days ago]

You did of course add a robots.txt text file? Use webmaster tools to give more granular control on the site with Google? Disabled feeds in case they are an issue?

[HugoModerator @hnla 1 week, 2 days ago]

Sorry didn’t mean to dismiss the fact you did bother to list your details, we appreciate that, brief explanations of issues are good form though.

Not sure what issue you’re having but possible, if BP is not in WP root, you may need to state the blog id BP is running under but that’s really a MS issue. Is this a MS install ? If so try define(‘BP_ROOT_BLOG’, 2) or whatever blog id is relevant:
http://codex.buddypress.org/user/install-buddypress-on-a-secondary-blog/

[HugoModerator @hnla 1 week, 3 days ago]

You don’t really preface all that with a brief description of what is wrong!

Windows for starters is an issue with permalinks, you’ll need to read this for a better understanding:
http://codex.wordpress.org/Using_Permalinks

Although you say WP was/is working what permalink structure do you have? BP needs anything other than the default set.

[HugoModerator @hnla 1 week, 3 days ago]

The usual test please switch to a theme such as twentytwelve and see if issue persists also ensure some activity has taken place, add an update just to be certain the member is picked up on.

WordPress.org-approved BuddyPress themes

Is that a theme name then! helps to perhaps state an actual theme you’re using when this happens.

[HugoModerator @hnla 1 week, 3 days ago]

@praveshraheja Just to let you know that I have removed that link, they’re is only one place to safely download the core BP files and that’s the official repo, please don’t post links like that again.

And that link chouf1 provided is the tag list, that is the full release history from day one.

[HugoModerator @hnla 1 week, 4 days ago]

exactly if you place members in the top root of your theme BP 1.7 will look for that and assume you are wanting to disable theme compatibility, it’s a means of ensuring backwards compatibility with themes already customised or template packed. BP theme compatibility only allows you to overload files by placing them in my-theme/buddypress/members/ (or community), soon, in hopefully 1.8, there will be further means of managing and using custom template parts under theme compatibility which should mean we can move forward from old methods and use theme compatibility exclusively.

[HugoModerator @hnla 1 week, 4 days ago]

No idea, the WP plugin forum is the best place for questions & answers.

[HugoModerator @hnla 1 week, 5 days ago]

@johnconner
You can pick this gist example set of nav styles apart if it helps:
https://gist.github.com/hnla/5390835