BuddyPress.org

You could create a .js file in your child theme which you could use for all of your custom JavaScript. You’d then enqueue it with the following code (which goes into your child theme’s functions.php):

function my_enqueue_scripts() {
    wp_enqueue_script( 'my-custom-js', get_stylesheet_directory() . '/js/script.js', array(), '1.0.0', true );
}
add_action( 'wp_enqueue_scripts', 'my_enqueue_scripts' );

Note:
This snippet will enqueue a script called script.js located at child-theme/js/script.js

Alternatively, you could just add the code to your footer.php file, just above the </body> tag like this:

<script>
    // JavaScript goes here.
</script>

That’s odd.

Are you sure you have deactivated all plugins / code snippets (wp-content/plugins/bp-custom.php, /wp-content/mu-plugins/) and that you switched the theme to one of the Twenties (Twenty Sixteen, Fifteen, etc.)?

Can we have separate template for any-group-name page?

Yes! That’s what the template hierarchy is for:

Template Hierarchy

Have you tried switching your theme to 2015 in order to see if there is a theme update needed?

We have deprecated support for the bp-default theme since v1.9:
The future of the bp-default theme

That being said, we can look into supporting this feature in bp-default for BP v2.5.0.

You might have to do a fresh install because BuddyPress 2.4.0 uses new code for the /groups/single/home.php template:
https://buddypress.trac.wordpress.org/browser/tags/2.4.0/src/bp-templates/bp-legacy/buddypress/groups/single/home.php#L75

The code you listed above is older code.

If you already have those changes, then I’m guessing you are using a custom theme with BuddyPress support that has overriden the groups/single/home.php template. If that is the case, you’ll have to change the group home template to use these new lines.

Hi, thanks and glad there was something in there for you. Don’t spend too much time digesting as above was provided as a generalised overview of possibilities, as too is below.

**I find once narrowing down a couple of solutions concepts for a project next step is roll out a concept build and play for yourself and see how things work or not work including if the concept platform sits well with your own methodology of design and capacities .

Re, including buddypress from the start, sure Why not?

I challenge you to list any reasons why one wouldn’t consider committing to buddy on initial planning. (no need to post, just a thought provoking exercise)

With my own project one primary key point goal was the project must be built on WP, right from the start I even consultant client against this idea, at the time I believed there are “better” solutions out there for a community building site (of this nature). Without going into details why and how such other platforms “could be” implemented.

The end result was I always came back to Buddypress being a perfect smooth integration as a small component of the complete project. At that time it was just a case of commitment and understanding there are going to be some big customs on the horizon, I’m very familiar with WP and its hooks and filters so developing bp / bbp was just a case of heading to the codex pages and certainly an influencing factor in using buddy – having an extensive self-help support system.

Regarding other community platforms built on WP I did look at other open and premium paid systems , my findings: in support of buddy for this project.

1. Self help support community – provides a wider understanding of what you are trying to do, and therefore can provide much wider access to resources and solutions (access to 100’s of developers , compared to a single tech support that can take longer to explain things before they “get it!”) – stuck on something just search the support, before posting you will be really surprised that even 5year old post can provide direction.

2. Plugin support – say plugins, today if there is not a plugin that does it, there will be soon… Very common on long term projects I work on, I will write a plugin / function code, then 6months later either a theme, plugin or even a core update is released with the same feature. That’s not a bad thing, it just means I’m always at least 6months ahead of the rest of the world……. Well that’s how I read it 

3. Warm and fuzzy feel good feeling in the open source arena – everybody to his own, with respect. And the open source arena means different things to different people. For me this project has opened further opportunities to release certain features / plugins back into the community once tested and proved etc. – so there is a level of warm and fuzzy for me regarding using buddy press being something not provided elsewhere. (but that’s just me)

What you use for the community building and offering of other features it’s really up to you. It makes sense that if your store is built on wp, then you would use wp for all other components of the project. (buddy, bbp etc).

So why not commit to buddy right from the start if you choose to using a wp based store?
You could consider the store / payment systems a separate project, where you decide to use a wp base store. And the other project is a wp based community building site.

you are just using the same wp install for both projects. –

referring to my suggestion “start with the payment systems first” it’s more so, maybe focus more energy on this part to ensure you get it working first before investing too much time in rest of the project.

Maybe consider your concept build to be an “out of box” wp / buddypress install (provides opportunity to play with buddy while working on the store / payment systems and check out the woo plugin library too.

One advantage will be each customer account (user id) will be same buddy press member id (user id) – from there you’re pretty much only limited to your own capacities as a developer and of course client time and budget.

My understanding of BuddyPress is it’s an extendable community building framework eg, has friend’s connections, member’s directory, forums(bbp), message systems + a bunch of other cool features etc. apart from the specific community building features it’s up to the developer to extend using existing plugins or creation.

Enjoy!

I remember someone reporting a similar issue last year or so. They used a theme which was not updated with the current BP version at that time. What have you done so far to troubleshoot the issue?

WP/BP versions? Theme used? If you change to the Twenty Fifteen theme, does the issue remain or is it resolved? Have you tried deactivating plugins except BP and use WP default theme to check if that resolves the issue? If that doesn’t solve it, do provide more information about your installation https://buddypress.org/support/topic/when-asking-for-support-2/

Have tested this issue with Twenty Fifteen, Twenty Twelve and Kleo

There appears (to me) to be two seperate issues.

1) irrespective of theme

Previously when Enforce Field Visibility was checked then the Option to change field visibility did not arise on the registration form.

Now it does appear, and can be acted upon, even when Enforce Field Visibility is checked.

And the new potential member is allowed to change visibility nothwithstanding that it had been marked (say) Admins Only.

(Haven’t yet gone into tho database to check what has happened in bpxprofile data – but i do think something is amiss)

2) With Kleo

In addition to the above (will notify SeventhQueen)

When the Registration page is opened the div containing the options to change visibility is open (default) on the form. – not good

On the other themes the div containing the options to change visibility is closed (default) on the form.- all good

@Agbams have you set up any Widgets for Buddypress sidebar http://vibethemes.com/envato/wplms/documentation/theme-guide.html#sidebar-setup.

Also check under the created page “Members” and see what sidebar is selected if that option is available.

Hi @Sweeny,

Woffice developer team here !

Do you have any ticket open here : https://2f.ticksy.com/ ? Please send us some access to your website so our team can figure out what’s going on 😉

The issues is also present with some other themes but it seems to be caused by the Birthday extension. As we create new Xprofile fields, but if was working fine before 2.4.0 and we can’t reproduce it.

That’s why we need more details 🙂

Thanks @r-a-y btw !

Cheers

2F

@sweeny – WOFFICE is a premium theme that we do not have access to.

The other replies in the thread mention that they are using multisite. Are you using multisite?

Of course, nothing special. I have installed the woffice theme and activated woffice birtday plugin. After this… The error appeared.

KLEO is a premium theme that we do not have access to.

– What happens when you switch to another theme? Does the problem still occur then?
– If the problem still occurs after switching the theme, what plugins are you using?
– Do you see any errors in your browser console?

@bum2 – I’ve split your reply into its own topic.

– What happens when you switch to another theme? Does the problem still occur then?
– If the problem still occurs after switching the theme, what plugins are you using?
– Do you see any errors in your browser console?
– Did you override the registration template into your theme?

@paragbhagwat – I’ve split your reply into a separate topic.

About the custom group homepage template, this is only for theme developers. It’s not something we bundle.

For more info, read the “Single Groups Front Page” section of this codex article:

Template Hierarchy