Paul Gibbs (@djpaul)

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 6,792 total)
  • Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    @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

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    The 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
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    @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
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

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

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Are you using W3TC with Object Caching enabled?

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    I 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.1
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

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

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Shouldn’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.1
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    In reply to: Fatal error PHP 7.1
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    I 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.1
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Okay. 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_action issue 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.

    In reply to: Fatal error PHP 7.1
    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Thanks for finding that one.

    I’m trying to get someone from the WordPress team to confirm some details on their PHP 7.1 support, and once I have that, I’ll reply here again.

    Well, debug what bbp_get_reply_author_id is, etc. It looks like it should work, but I don’t know where exactly you’re adding this code (if it’s outside the reply templating loop, it won’t work, I’m guessing) — and this is something you should just debug locally until you figure it out.

    Yes. The option values themselves are stored in the database, and they need to be there to verify that the submitted form data is valid.

    Hi @davehakkens

    bp_member_profile_data() defaults to the current user in the members loop… It is probably coincidence this is the thread starter user, but I can’t remember how bbPress interacts with it.

    What I think you want to do is

    bp_get_member_profile_data(array('field'=>'country', 'user_id' => bbp_get_reply_author_id()))

    That way you’re passing the bbPress reply author ID to the BP function, to fetch the data for that user. Hope that helps.

    In reply to: Oembed for actives

    @r-a-y Since you worked on this. Any ideas?

    @scaffies (@jenfilgate i’m going to ASSUME you have EXACTLY the same issue, otherwise you should make your own forum topic)

    You said:

    type “Subscriber” / “Participant” can no longer upload new profile pictures, or pictures, video, or audio to their personal galleries

    BuddyPress doesn’t have “personal galleries” built-in. We only support uploading media for group and member profile pictures, and cover images for those. You’ll need to contact the author of the plugin(s) used to provide your personal galleries, we can’t support other plugins. Sorry.

    @r-a-y Did the livestamp changes in 2.7 affect how we’re storing the field *value*?

    You’ll need to get access to the server’s PHP Error Logs. Once you do, you should see repeated blocks of text at the bottom of the file defining a Fatal Error. Please copy/paste that message here so we can help you understand what the cause is.

    What language is your site running?

    I agree those all relate to running out of memory 😀

    No W3TC, so I’ve no immediate idea why you would be seeing problems with password change.

    In reply to: Scalability

    @johnykoch Well, it’s gated — I’m not getting past the homepage (registration) without creating an account, which I’m not going to do just to see the site. That said, it does feel slow.

    Are you using any kind of caching? Page caching? Object caching? If you could list your plugins, that’d be helpful to help you if you don’t know.

    Your homepage is 1.5Mb (!) and takes 5 seconds to load for me. Both are pretty heavy for such a light-looking page, you might want to look into that.

    Using the logged-out homepage to test on isn’t a bad idea. I’d suggest starting by adding https://wordpress.org/plugins/query-monitor/ which will only show up for Admin users, and load the homepage a few times, and see if it tells you anything useful. Notably, PHP warnings or errors, as well as slow Database Queries.

    That’s a good start, and I can offer further advice on the specifics of each of these if you require as you’re able to supply further data.

    If you have fatal errors, then that’s pretty much a problem that’s going to cause other problems, so you need to get this resolved, though I think you realise this. 🙂

    You need to let us know what plugins you are using.

    Specifically, are you using W3TC? With its Object Caching feature enabled? If so, there’s a bug in W3TC (we believe) that causes exactly this problem. We couldn’t figure out what was happening when we looked into it about six months ago. The solution is don’t use W3TC for object caching. 🙁

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    It’s not quite as bad as I thought. It’s referring to a BP 2.1 deprecated function, at first read I thought it was something in 2.7. Going to look into it more.

Viewing 25 replies - 1 through 25 (of 6,792 total)