Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 901 through 925 (of 3,962 total)
  • @hnla

    Participant

    Please do not jump in on other peoples threads (hijacking), start your own thread please on your particular issue, otherwise threads become jumbled and confused.

    @hnla

    Participant

    Don’t ever ever modify core files period! Not really sure why you are having to do this but don’t mess around with BP elements or their classes as many are required as a lot of the JS/Ajax functionality hooks to them.

    If you have to use bootstrap that’s your choice but bootstrap doesn’t replace the necessity for BP styles -overload the BP styles if required to edit / modify them.

    I assume you have a set up a child theme to setup your theme in and letting theme compatibility take over the template handling for BP pages.

    @hnla

    Participant

    It is correct to briefly state what the solution was please.

    @hnla

    Participant

    If I need to provide additional details please let me know.

    We shouldn’t really have to ask you for that 🙂
    https://buddypress.org/support/topic/when-asking-for-support-2/

    I trust this is a custom theme you’re using? If it is a custom theme then switch to twentytwelve theme and see if issue still persists if not this shows you it’s a theme issue and you need to contact the theme author in the first instance for support.

    @hnla

    Participant

    @sensibleplugins don’t think this is a bug necessarily, Not sure I can get the order of processing clear with your snippet but it suggests that you are applying your filters too early and BP is still getting to cut in with it’s own.

    In my circumstance I’m forcing a cpt content loop through to a do_action on a groups page so think my filters run and are processed before bp grabs that page content to push out to or replace the wp content loop.

    I have just changed my filters to bp_restore_all_filters(‘the_content’) and then add back via bp_remove_all_filters(‘the_content’) as I needed the do_shortcodes running as well, this, in my situation, works fine.

    @hnla

    Participant

    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)

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

    @hnla

    Participant

    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.

    In reply to: css and js missing

    @hnla

    Participant

    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.

    @hnla

    Participant

    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:
    https://buddypress.trac.wordpress.org/ticket/4639

    @hnla

    Participant

    @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

    @hnla

    Participant

    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?

    In reply to: The Codex Looks Great!

    @hnla

    Participant

    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.

    @hnla

    Participant

    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)

    @hnla

    Participant

    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?

    @hnla

    Participant

    @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?

    @hnla

    Participant

    ? 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.

    @hnla

    Participant

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

    @hnla

    Participant

    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.

    @hnla

    Participant

    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

    @hnla

    Participant

    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()

    @hnla

    Participant

    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.

    @hnla

    Participant

    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.

    @hnla

    Participant

    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?

    @hnla

    Participant

    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:
    https://codex.buddypress.org/user/install-buddypress-on-a-secondary-blog/

    @hnla

    Participant

    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:
    https://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.

Viewing 25 replies - 901 through 925 (of 3,962 total)
Skip to toolbar