BuddyPress.org

You have 2 options. I’d recommend the 2nd:

1: Copy and paste the JavaScript to your my-theme/buddypress/members/register.php template. In this case you’ll need to copy the <script> tags also.
2: Create a separate file (my-theme/js/script.js for example) and paste the JavaScript into that. In this case you don’t need to copy the <script> tags. If you go down this route you will need to enqueue the script. See this article for info on how to do that:

wp_enqueue_script()

It’s being caused by the BP Group Email Subscription plugin.

View the following for a fix until the next version is released:
https://wordpress.org/support/topic/styling-issue-of-letters-with-v3-7-0/#post-8832281

Hi,

you need a child theme and a small code modification.

The code is explained here.

if ( bp_has_members( bp_ajax_querystring( 'members' ) ) ) is to replace by something like (can be different)
if ( bp_has_members( 'type=random' ) )

In a “buddypress” folder of your child theme, you add a copy of this file:
wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/members-loop.php

What ever you modify in that file while now be interpreted by BuddyPress. The advantage of this method is that BP can be updated while your modification in the child will always be save and taken in account over the current version.

You can also search the forum for members-loop to get other information.

1,2,3,4,6 should be left to WordPress plugins as these are specific to WP.

7, 10 have been discussed as core options. It just takes time for developers and the team to finalize specs and to code as this is all done on a volunteer basis. 10 is hard because it relies on a ton of dependent code that hasn’t been written or finalized yet.

5 – There’s been some preliminary work on this. See https://github.com/buddypress/bp-types-ui.

9 – If you’re using WordPress multisite, this should be already available as a WordPress option under “Network Admin > Settings”. Otherwise, this plugin might work, but does the opposite. It restricts signup to email domains that you specify.

Notifications

2 should already be in core.
3 is a good request, but unreliable due to how the notifications data is stored. It would be easy to do for BP core notifications, but notifications generated by plugins could store the user ID differently, making this unreliable.
4 could be done via a custom template or via a small code snippet.

You need to figure out what is causing the white screen.

Turn on WP_DEBUG and view the notices that are logged or displayed:
https://codex.wordpress.org/Debugging_in_WordPress#WP_DEBUG

List the notices here if you want us to attempt to diagnose your problem.

My first guess is your problem is memory-related as your webhost might have restricted memory usage. Or if you’re using a caching plugin that is not correctly configured.

Hi,

not the solution, but more a way to resolution and to see how you could do that title adjustment.
Read here.

WP function reference you have to explore:
pre_get_document_title
wp_title

..anything related to “title” in bbPress.

I use https://wordpress.org/plugins/buddypress-login-redirect/ – and it does exactly that.

This field is visible by default.

If not, so the problem might be with your theme.
For other what’s new form questions, search the forum.

Some answers here:

Height what’s new form

https://buddypress.org/support/topic/how-do-i-remove-textarea-resize-without-editing-the-js-script/

Hi,

did you considered this plugin ?

Hi,

sorry but this is not related to BuddyPress.
Dashboard access is part of WordPress and the way it is displayed on your screensht indicate that it is also theme dependant somehow.
You can hide any menu item from the WP toolbar by following these instructions

or you can chosse to active/deactive the toolbar option in BP settings or use a plugin to limit dashboard access.

That is used by the backbone – javascript library which is included with WordPress.
Perhaps something, maybe your theme, is preventing it from being loaded.
Try switching to a WP theme like 2015.

From my previous post, changing AllowOverride None to AllowOverride FileInfo seems to have made the member, groups, and other pages operational.

The following is a diff of the httpd.conf from the Yosemite version of macOS and my current version. Remember that there are three configuration files: httpd.conf, my.cnf, php.ini
https://bradleyaross.wordpress.com/2017/02/04/wordpress-installation-problems/

BradleyRossMacBook:apache2 bradleyross$ diff httpd.conf httpd.conf-YosemiteDefault
22,25d21
< #
< # History:
< # Starting with httpd.conf.pre.update which was dated July 1, 2015
< #
107,109d102
< #
< # The line for mod_include.so was uncommented 17-February-2017
< # to allow the use of server side includes
164,167c157
< #
< # The line for mod_cgi.so was uncommented on 17-Feb-2017
< #
< LoadModule cgi_module libexec/apache2/mod_cgi.so
—
> #LoadModule cgi_module libexec/apache2/mod_cgi.so
178,186c168,170
< # See http://askubuntu.com/questions/48362/how-to-enable-mod-rewrite-in-apache
< LoadModule rewrite_module libexec/apache2/mod_rewrite.so
< #
< # The two following lines had been commented out as part of the
< # update July, 2015. They are now being uncommented to
< # put them back in
< #
< LoadModule php5_module libexec/apache2/libphp5.so
< LoadModule hfs_apple_module libexec/apache2/mod_hfs_apple.so
—
> #LoadModule rewrite_module libexec/apache2/mod_rewrite.so
> #LoadModule php5_module libexec/apache2/libphp5.so
> #LoadModule hfs_apple_module libexec/apache2/mod_hfs_apple.so
235,237d218
< # Apparently the slash at the end of the Directory open tag
< # refers to the root of the file system rather than /> indicating
< # an empty tag
269,270c250
< # The attribute Includes was added 17-Feb-2017
< Options FollowSymLinks Multiviews Includes
—
> Options FollowSymLinks Multiviews
278,281c258
< # The attribute None was changed to FileInfo 17-Feb-2017:wq
<
< #AllowOverride None
< AllowOverride FileInfo
—
> AllowOverride None
453,455c430,431
< # The following two lines were uncommented on 17-Feb-2017
< AddType text/html .shtml
< AddOutputFilter INCLUDES .shtml
—
> #AddType text/html .shtml
> #AddOutputFilter INCLUDES .shtml
BradleyRossMacBook:apache2 bradleyross$

I have .htaccess
I have loaded the entire system three times and followed the directions
I have made sure that all of the files have an owner of _www

I have already screamed and will probably do so again. I am currently using

Apple Macintosh macOS 10.12.3
Wordpress 4.7.2
Theme: TwentySeventeen
bbPress 2.5.12
BuddyPress 2.8.0
Jetpack 4.6

The requested URL /blogs/wordpress/template/members/bradleyross/profile/edit/ was not found on this server.
The page register has the permalink http://localhost/blogs/wordpress/template/index.php/members
Does this sound correct

It also appears that multiple attempts to load the software may result in things like members-2 and members-3. You may have to send pages with those permalink to the trash and then empty the trash. Hopefully, you can then recreate the pages correctly

I now assume that the problem is somewhere in the rewrite module. In the httpd.conf file, I am going to change the line Allow None to Allow FileInfo. Does this sound reasonable and are there any other changes you think that I should make.

in httpd.conf, I have

LoadModule alias_module libexec/apache2/mod_alias.so
LoadModule rewrite_module libexec/apache2/mod_rewrite.so
#
# The two following lines had been commented out as part of the
# update July, 2015. They are now being uncommented to
# put them back in
#
LoadModule php5_module libexec/apache2/libphp5.so
LoadModule hfs_apple_module libexec/apache2/mod_hfs_apple.so

and

<Directory “/Library/WebServer/Documents”>
#
# Possible values for the Options directive are “None”, “All”,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that “MultiViews” must be named *explicitly* — “Options All”
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
#
# The attribute Includes was added 17-Feb-2017
Options FollowSymLinks Multiviews Includes
MultiviewsMatch Any

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# AllowOverride FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>

@indra1007

Have you read the article that was linked by @danbp?
Do you have .htaccess file in the same diretory where you installed WordPress?
If not, create it with this content:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

More details here: https://codex.wordpress.org/htaccess

Latest WordPress itself has issues on PHP 7.1, and while testing BuddyPress we allow failures on PHP 7.1 as well.
So in general BuddyPress should work on PHP 7.1, but no one spent extra attention on testing there everything and fix if there are any issues.

Try to downgrade to PHP 7.0.x.

Thanks for reporting!

A fix is already in trunk:
https://buddypress.trac.wordpress.org/changeset/11432

This will be ready for v2.8.1. Until then, manually patch bp-xprofile/bp-xprofile-admin.php with the changeset linked above until 2.8.1 is released.

See: https://buddypress.trac.wordpress.org/ticket/7445

Bug confirmed! Open a ticket on the trac.

To login, use same credentials as for this forum.

Hi. I struggled with this for a while, and I agree entirely that something like this needs to be in the BuddyPress core… actually, I think much better user management needs to be in the WordPress core, not just BuddyPress, but that’s a discussion for another time…

I eventually found the code that you’re using and modified it to be able to ignore all users with a specific WP role or roles, thus removing the need to hard-code specific user IDs.

To manage user roles you’ll need a plugin such as User Role Editor by Vladimir Garagulya and create a new role that you assign to users who you want excluded (I chose “suspended”). If you use URE you can assign this as an additional role to the main one that WordPress allows you to set.

The code is here: http://pastebin.com/9xYALGfR, but I’m no PHP expert, so offer no assurances… all I can say is that it works for me 🙂

You will need to integrate Multi Vendor plugin into BuddyPress.
That means create specific profile pages (there is an article in BuddyPress Codex), modify BuddyPress templates in your child theme (same – see articles in Codex).

You can check this as well:

• https://wordpress.org/plugins/bp-wc-vendors/
• https://www.wcvendors.com/help/topic/wc-vendor-products-with-buddypress/
• http://docs.buddyforms.com/article/151-create-a-social-marketplace-with-woocommerce-and-buddypress
• https://wpsoul.com/how-to-create-multi-vendor-shop-on-wordpress/

What are your WordPress and BuddyPress versions?