BuddyPress.org

I actually dont get it

what is the purpose of the POEDIT application… i chaged my “join Group” to “join Us’… but the text didnt change… but when i edit from buddypress core files ‘bp_groups_template.php” .. it changes to ‘join Us’ and it is my understanding that core files arent to be tampered with… due to future update… can sumone pls explain this language file thing proparly and how i can customize my texts and strings… or is the another way

I actually dont get it

what is the purpose of the POEDIT application… i chaged my “join Group” to “join Us’… but the text didnt change… but when i edit from buddypress core files ‘bp_groups_template.php” .. it changes to ‘join Us’ and it is my understanding that core files arent to be tampered with… due to future update… can sumone pls explain this language file thing proparly and how i can customize my texts and strings… or is the another way

Having looked further at this theme framework on a local test install and it appears to work pretty well in it’s default out of the box implementation with BP 1.7  so I’m afraid whatever custom settings / layout configurations you have set in the frameworks backend are causing issues.

Hello, I am interested in this option too, I want to give the user role to author when we makes new blog(site), and I saw your code above. But where shall I put this code? In buddypress files? But where?
thank you

hi guys

last night i started setting up a fresh WP installation with the newest version of BP. all good.
i then installed (via WP) woocommerce and after installation (i guess during activation) it just stalled. admin would not respond at all. no errors, just complete blank page, for every page i tried, except for one time i got a 500 error with no detail.

i eventually deleted the plugin folder and it went back to work without woocommerce.

if anyone has any suggestions here, i’d be happy to hear.i also want to install another couple of plugins, like Learn Dash – wondering how all theses templates are going to work with each other….

Thanks!

well it’s an interesting post but it is contrary to my own personal experience with WP Engine i signed up right about the time he gave up. I would note the fact that he states that the CEO issued personal apology and reimbursement for the migration issue, thats seems like at least they took the issue seriously at some point. Also way he closes the post “Where I am today Back at Linode, back to running it myself.” This is exactly the reason it makes sense for people along a spectrum of technical expertise not just novices. Granted the WP managed hosts are not without their drawbacks and even WPE has some quirks that take a little getting used to.

WP Engine is the only company that provides both phone support and specialized wp hosting as far i know. The entire system is built from the ground up only to host WP sites. I cannot tell you how valuable it is when you call into support and you don’t have to explain how wordpress works or what buddypress is every time you are trying to get to the bottom of something. It is also the only hosting company i know that Automattic is financially involved in, to me that means something, i suspect it also means something to WPE.

In my experience the notion of a perfect host is a canard, what may be a great host today could be horrendous two years from now, but WPE aside from any deal killing kind of quirks is the best platform you could be hosted on aside from wordpress vip unless you truly can afford to do everything yourself.

There is also bp_is_activity_component()

here’s the code for bp_is_page. You can use

if ( !bp_is_user() && bp_is_current_component( ‘activity’) )

`function bp_is_page( $page = '' ) {
      
       if ( !bp_is_user() && bp_is_current_component( $page )  )
           return true;
   
       if ( 'home' == $page )
           return is_front_page();
  
       return false;
   }`

yeah idk but i do know that it’s meant for the primary site none of the buddypress stuff would do anything on the sub-sbites anyway.

Oh and you ought really to ask this question of the theme authors, as they are the ones that have diverged from the norm so are best placed to understand or know how they have and how that has been done and suggest an approach you can take. They just need to know that BP attempts to use the standard WP templates and the content loop replaced with BP content.

Failing all the above you may need to fall back on the older method of  overloading BP templates into your child and ensuring the markup matches to the themes markup.

You may like to look through the codex to see if the constructor theme has been template packed by Mercime.

and what is in this file:

// load one of layout pages (layouts/*.php) based on settings
get_constructor_layout(‘page’);

This is going to be a problem with these frameworks that break with the normal WP methods for their own approach to templating and where users are going to have to figure out how to deal with this.

You could try creating a file named buddypress.php in your theme root and in that file copy the contents of what ever is in layouts/page.php but that file may also not be standard.

This is a problem with your theme.

BP theme compatibility is designed to automagically use standards WP templates if  certain custom ones aren’t found, assuming you haven’t created any custom files in your theme BP is looking for these files in this order:

page.php

single.php

index.php

If you theme does not have these or use one in a standard manner then you may well get a screwy layout, but it’s going to be very hard to tell you what is going on with a third party theme like this.

Looking at BP pages I can see straight away something not quite right as there is a distinct lack of WP/BP body classes that I would expect to see.

You’re going to need to look those standard files above, determine which is being used by BP components in theme compat mode then try and work out what your framework is using to generate your general page.php page views i.e what file is used when you create a WP ‘page’.

@cikez did you copy the buddypress css directory folder as well as its contents to the root of your theme? If I am correct it needs to maintain its directory structure so in the root of your theme if you copied it correctly there will be a folder named css and inside it will contain buddypress.css