Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

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

    @djpaul

    Nice work! That looks like it ought to work. Assuming you’re logged in. Assuming that user has that capability.

    Have you tried adding text or something just output that PHP block, to double-check your edited template is actually being used? You might be touching the wrong file.

    Failing that, it might be output, but just hidden by your theme’s CSS? Have you checked for this element inside the web browser’s inspector tools, have you found it?

    Alternatively, you could use this code, but I don’t see why it would make any difference:

    
    <?php if ( is_super_admin() ) : ?>
      <div>hello world</div>
    <?php endif; ?>
    

    ^ That slightly different syntax for PHP in these template files (note the {} are gone) makes the file slightly more readable/less prone to be accidentally broken.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    @kavsc2 Please make your own support request. These tend to be very different fixes.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    You might be running a theme with BuddyPress-specific files. Have a hunt around your theme, look for a similar structure. etc

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Go to /wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/. The four files — activate, index, members-loop, and register — are templates used for the Members Directory. Ignore the single subfolder; that’s used for individual member pages.

    You will want the index.php file.

    In your theme, create a buddypress/members subfolder. e.g. /wp-content/themes/my-theme/buddypress/members/. You’ll need to create both directories if they’re missing. Copy that index.php we 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.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    No, 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.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

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

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Hi @josselinl

    You will have to ignore this nag message, unless perhaps you write some custom CSS to hide this particular nag (for example). Sorry!

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    You’ll want to add new_at_mention to your list of types.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Am leaving this topic open for now because you mention multiple issues, let’s try to fix them one at a time (BadgeOS first).

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    That error comes from the BadgeOS plugin. You’ll need to talk to that plugin’s developers for support: http://badgeos.org/support/

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

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

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Hi @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 like sendmail to 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.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    As Steve says, everything is public by default.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

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

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    This 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!

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Are you using multisite? Do you have NOBLOGREDIRECT set — if so, to what value?
    What version of WordPress are you using?

    Thanks.

    Profile photo of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    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.

    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.

    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.

    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.

    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.

Viewing 25 replies - 1 through 25 (of 6,809 total)
Skip to toolbar