Forum Replies Created
-
In reply to: Adding a link (button) on member directory page
Go to
/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/. The four files —activate,index,members-loop, andregister— are templates used for the Members Directory. Ignore thesinglesubfolder; that’s used for individual member pages.You will want the
index.phpfile.In your theme, create a
buddypress/memberssubfolder. e.g./wp-content/themes/my-theme/buddypress/members/. You’ll need to create both directories if they’re missing. Copy thatindex.phpwe found earlier into this new directory.e.g. you’ll end up with
/wp-content/themes/my-theme/buddypress/members/index.php. You’ll want to play around in this file to find where you want to add your custom CSS, which I’ll leave to you to figure out.In reply to: Showcase forum not about showcasesNo, you’re not. It’s just not used very well. I’d like to get rid of it one day, but we’re trying to get a new theme for the website built first. Sorry for the inconvenience in the meantime.
In reply to: Basic BuddyPress DemonstrationWe used to have testbp.org which last a few years until spam and DOS attacks forced us to take it offline.
Your best best is probably looking through https://wordpress.tv/tag/buddypress/ for recent WordCamp videos, and see if you can find one.
In reply to: Disabled connexionHi @josselinl
You will have to ignore this nag message, unless perhaps you write some custom CSS to hide this particular nag (for example). Sorry!
You’ll want to add
new_at_mentionto your list of types.Am leaving this topic open for now because you mention multiple issues, let’s try to fix them one at a time (BadgeOS first).
That error comes from the BadgeOS plugin. You’ll need to talk to that plugin’s developers for support: http://badgeos.org/support/
In reply to: Buddypress user registration with MUI don’t think we’ve consciously changed this behaviour (if this indeed happens as you say) in the last couple of years. It’s possible that something in WordPress changed the behviour with however BuddyPress adds sites internally.
I think I just about recall some conversation from four or five years ago about this, but I’m struggling to remember what it was about precisely, or even where to look. If I were to start investigating this, I’d set up an otherwise identical multisite (without BuddyPress) and add users via the wp-admin, and see if those users becomes subscribers or not. etc.
In reply to: Pending ActivationHi @leo1951
Are you using any email plugins for WordPress that you require to successfully send emails? Or SMTP config? Or anything custom in php.ini?
It’s not clear if “Easy WP SMTP” is required for your WordPress installation to send emails.
If you are not using SMTP to send email via a remote email server, are you running something likesendmailto do that from the server? If so, can you check that program’s outgoing email? Log file? See if you can find evidence if it’s actually receiving the email.@tw2113 @dcavins Did one of you have a plugin that logged if BP’s emails were sent successfully or not (from an internal point of view)? I can’t remember who it was.
In reply to: How to have some public viewable pages?As Steve says, everything is public by default.
In reply to: Adding a link (button) on member directory pagePage Builders are not be compatible with BuddyPress (at least, I don’t know of any support).
You would need to manually edit the template files. If you know basic CSS/HTML/PHP, I can give you some instructions and link to some docs.In reply to: Memory exhausted on forum sectionThis is a pretty common problem. You need to increase the amount of memory available for PHP.
There are many posts on the web about this — try https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/ — but if you need further help, I’d suggest contacting your web host would be a good idea.Hope this helps!
In reply to: ANOYING WARNING from call_user_func_array()Are you using multisite? Do you have
NOBLOGREDIRECTset — if so, to what value?
What version of WordPress are you using?Thanks.
In reply to: Do you even optimize bro?The original reporter has submitted a bug report https://buddypress.trac.wordpress.org/ticket/7436
The language used in that report is much more constructive than that of this forum thread, so I’m going to close this.
In reply to: Can’t get BuddyPress activated@johnjamesjacoby This specific error has already been fixed in BuddyPress trunk a couple weeks ago (I don’t have the changeset number to hand). netweb fixed an identical problem in bbPress a couple of months ago: https://bbpress.trac.wordpress.org/changeset/6113/trunk
In reply to: Can’t get BuddyPress activatedThe issue reported by @larsivar two weeks ago is by a change in PHP 7.1. We have fixed this specific issue for an upcoming release — our ticket tracking PHP 7.1 is here https://buddypress.trac.wordpress.org/ticket/7392
While we could ship a release today to fix that specific error, there is at least 1 other PHP 7.1 error that I know about, which is in WordPress itself, which I reported here https://core.trac.wordpress.org/ticket/39277
We’ll do more testing for PHP 7.1 in BuddyPress in the first couple weeks of the new year (probably) and ship what fixes we have. We may or may not choose to wait for the next minor release of WordPress (4.7.1) before doing that. Still to be determined.
In reply to: Broken after install@wautersandreas and @danbp Fatal errors with that exact message are caused by a change in PHP 7.1. We have fixed this specific issue for an upcoming release — our ticket tracking PHP 7.1 is here https://buddypress.trac.wordpress.org/ticket/7392
While we could ship a release today to fix that specific error, there is at least 1 other PHP 7.1 error that I know about, which is in WordPress itself, which I reported here https://core.trac.wordpress.org/ticket/39277
tl;dr We’ll do more testing for PHP 7.1 in BuddyPress in the first couple weeks of the new year (probably) and ship what fixes we have. We may or may not choose to wait for the next minor release of WordPress (4.7.1) before doing that. Still to be determined.
In reply to: Broken after install@baramagnus Unless you’re using PHP 7.1 on your server, please report your own issue with any relevant data from your PHP error log (ask your server host for help, if needed). We can’t debug anything given the very general report you’ve told us, unfortunately.
Are you using W3TC with Object Caching enabled?
In reply to: Repeatable Field groups requiredI looked into this a while ago. I don’t know if any plugins have provided it — if so, the code will be hacky — because achieving this requires changing some data storage we do in BuddyPress, which is a bit of a complicated issue to resolve well.
In reply to: Fatal error PHP 7.1The situation is BuddyPress is incompatible with PHP 7.1 as things stand. One issue means a fix in BuddyPress (which we’ve already fixed, and will have out in a release soon, but probably after Christmas), and the other issue I’ve found (which BP sites have a realistic site of running into) require a fix in WordPress, which I hope that team will get done for WP 4.7.1.
In reply to: [Resolved] Error update 2.5.3 –> 2.7.3Shouldn’t be. Ask your host to get you your server’s PHP Error log. It’ll be full up of stuff, if you’re getting 500s.
Then, post that here, and we’ll help identify where the errors coming from.
In reply to: Fatal error PHP 7.1Keep an eye on https://buddypress.trac.wordpress.org/ticket/7392
In reply to: Fatal error PHP 7.1I don’t disagree but until someone sets up PHP 7.1 locally, tests and patches everything, which is then signed-off by a regular contributor (also requiring a PHP 7.1) process, things are going to move slow. This is a volunteer project. Hopefully by next week we should see some fixes.
In reply to: Fatal error PHP 7.1Okay. The story is that PHP 7.1 is supported by WordPress 4.7 (or newer). Likewise, BuddyPress will need at least that version, too.
We’re currently tracking some unit test failures in PHP 7.1 (see the very bottom of https://travis-ci.org/buddypress/BuddyPress), but we’ve not figured out if they are our bugs, or some bug in WordPress core. Likewise, this
do_actionissue might be a regression WordPress should fix instead of us (if we’re getting caught by this, I bet many other plugins are, too).At any rate, I’m going to try to fix the unit tests once I get a PHP 7.1 box set up (hopefully this week), and then I’ll test the basics of BuddyPress, and see what other issues crop up, and fix or report them as necessary.
I think I’d wait a month or two to use PHP 7.1 with WordPress and BuddyPress in the wild, to be honest.
