Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 126 through 150 (of 6,157 total)
  • In reply to: Fatal error PHP 7.1

    @djpaul

    Keymaster

    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.

    @djpaul

    Keymaster

    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.

    @djpaul

    Keymaster

    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.

    @djpaul

    Keymaster

    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

    @djpaul

    Keymaster

    @djpaul

    Keymaster

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

    @djpaul

    Keymaster

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

    @djpaul

    Keymaster

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

    @djpaul

    Keymaster

    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.

    @djpaul

    Keymaster

    What language is your site running?

    @djpaul

    Keymaster

    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

    @djpaul

    Keymaster

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

    @djpaul

    Keymaster

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

    @djpaul

    Keymaster

    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.

    @djpaul

    Keymaster

    Whoops. That’s embarrassing. Two unrelated changes caused this. Sorry.

    We’ll get it fix ASAP.

    @djpaul

    Keymaster

    Yep, like @hnla said. BuddyPress’ DB requirements are the same as WordPress’.

    @djpaul

    Keymaster

    Because… something is redefining the wp_mail function. It is most probably Mailgun, you need to change its settings as I mentioned before.

    @djpaul

    Keymaster

    Good luck with your plugin!

    @djpaul

    Keymaster

    Last updated 23rd December 2016 for v2.7.4.

    @djpaul

    Keymaster

    Things that aren’t problems, or intentional changes

    (no content yet)

    @djpaul

    Keymaster

    Reported problems

    Extended Profiles – Field visibility option missing from registration form.
    Confirmed and being fixed for BP 2.7.1: #7298

    —

    Extended Profiles – “years” missing from “Date Selector” field type.
    Workaround: edit the field, and reselect the “absolute” range option, customising the date range as required (default is from 1956 to 2026 for most servers).

    Confirmed and being fixed for BP 2.7.1: #7300

    —

    Backwards incompatible function signature change for groups_get_group
    Confirmed and being fixed for BP 2.7.1: #7302

    —

    Changes to loading deprecated code causing fatal errors.
    For certain very old themes, and for sites that use the Sites component.
    Confirmed and being fixed for BP 2.7.1: #7307

    @djpaul

    Keymaster

    I remember looking at Mailgun before when someone asked about it. Looking at its code very quickly, it has an option to send via its API or not. You’ll need to disable its “useAPI” option (otherwise, it redeclares the wp_mail function, which will force BuddyPress to send plain-text only emails). Another consequence of doing this is that Mailgun configures PHPMailer to send via SMTP, and some web hosts/servers block external SMTP requests.

    If that has no affect, I think you’re going to have to do debugging inside the bp_send_email function. Specifically, I’d start looking at the return value of this line: $status = $delivery->bp_email( $email );

    With luck, PHPMailer will give you an error message with some clues in.

    @djpaul

    Keymaster

    > I have fixed the error I was getting of email_missing by adding information into the taxonomy tables manually. There is no documentation about this which is odd.

    I don’t think it’s explicitly documented outside of the PHP – but it is hard to find, at the best of time – but this guide https://codex.buddypress.org/emails/custom-emails/ does mention it uses a custom taxonomy, so I wouldn’t call it “undocumented”. “Very badly documented”, maybe 😀

    @djpaul

    Keymaster

    Assuming everything is working as it is, I don’t know why it would show more users than you have, either. Have you tried going to Tools > BuddyPress, and running “Repair total members count” as a workaround for now?

    @djpaul

    Keymaster

    By “blank”, how blank are we talking? Literally a white page — no content? Or something less dramatic.

Viewing 25 replies - 126 through 150 (of 6,157 total)
Skip to toolbar