Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 1,821 total)
  • Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    See how BuddyPress does this: https://buddypress.trac.wordpress.org/browser/tags/2.0.1/bp-groups/bp-groups-template.php

    I don’t know why BP does it this way (I would have to check the logs – it seems fishy) but in any case, this probably explains why you’re not seeing anything in your template. You should mimic what you see in that function.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Can you share more details about the problem?

    - Can you see the groups in question in the Dashboard? Dashboard > Groups
    - Are you logged in as an administrator or a normal user?
    - Is the logged-in user a member of the groups in question?
    - Can you see the groups when you go to example.com/members/yourmembername/groups?

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    > I can’t find any arguments for not including the WordPress profile in BuddyPress.

    The arguments are:

    - The fields at wp-admin/profile.php are hardcoded in WP. There’s no way we can ask WP which fields it provides in a programmatic way; we’d have to hardcode them as well. This is inelegant; it causes problems when other plugins add their own (hardcoded) fields, which BP won’t know about; and it will require keeping up with WP if they decide to switch which fields are included on that page.
    - The fields at wp-admin/profile.php are very odd, and not appropriate for most BuddyPress installations (or most websites that were built after 2004 – who uses AIM, and who among them would want to store that information in their WP profile?)

    As noted in the ticket, First Name and Last Name are the two possible exceptions I see here.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @j-j Thanks for your patience working through the issues. As for the original question, I agree with @henrywright that 2.0.1 is a very good upgrade for sites like yours, because some of the queries have been refactored to be much, much more efficient.

    As for your 502 errors, it’s very hard to diagnose something like this without access to various logs. Since you’re hosted on WP Engine, I would suggest opening a ticket with them. Describe the specifics of the problem, and perhaps also point them to this thread. Ask if they can look in your error logs (and perhaps your slow query logs) to see what’s causing the issue. (NB a 502 error is very non-descriptive, and it could be that it’s not directly BP-related at all.) Only your host will be able to tell you for sure. If they come back with specifics that point to BP 2.0.1 as the culprit, we’ll be in a better position to help.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @blankpoint Sorry for the troubles. The upgrade routine necessary for BP 2.0 is fairly large.

    I’ll work in the upcoming weeks on improving it, but in the meantime, a few things to try:

    1. Your memory limit issue is due to the fact that WP will not allow you to exceed 256M per pageload without explicitly saying you want to (regardless of your php.ini settings). You can put the following into wp-config.php to override for the admin only:

    define( 'WP_MAX_MEMORY_LIMIT', '1024M' );

    2. Just to get up and running, you might also consider running the heavy migration manually: from the mysql command line.

    INSERT INTO wp_bp_activity (<code>user_id</code>, <code>component</code>, <code>type</code>, <code>action</code>, <code>content</code>, <code>primary_link</code>, <code>item_id</code>, <code></code>
    date_reco
                      SELECT user_id, 'members' as component, 'last_activity' as type, '' as action, '' as content, '' as
                      FROM wp_usermeta
                      WHERE
                        meta_key = 'last_activity'
                        AND
                        user_id NOT IN (
                          SELECT user_id
                          FROM wp_bp_activity
                          WHERE component = 'members' AND type = 'last_activity'
                        )
            );
    

    You could split this up with a LIMIT clause in case you need to run it a few times.

    The other problematic bit of the upgrade routine has to do with migrating your old signups to the new signups schema. (I’m assuming you have open registration + non-multisite.) That migration is not necessarily mission-critical, so you could skip it altogether. So, in other words, once you’ve run the ‘last_activity’ migration, you could comment out line 351 and lines 355-395 here: https://buddypress.trac.wordpress.org/browser/tags/2.0/bp-core/bp-core-update.php#L351 and then reload your admin to mark the migration as complete.

    Again, sorry about the difficulties. You’re running a very large BP site, and the migration tools were not up to the job.

    Then, you could comment out this line: https://buddypress.trac.wordpress.org/browser/tags/2.0/bp-core/bp-core-update.php#L351

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @texrat – Sorry you’re still having trouble. Do you have access to your database? If so, you should check in wp_usermeta to see what your user ID’s value for wp_capabilities is (if any). I’d also ask you to double- and triple-check that you’ve followed all the instructions in the plugin – it doesn’t give any visible feedback, and if you make a wrong step (such as putting it in plugins rather than mu-plugins, or using the wrong user_login value), it won’t let you know.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @texrat – Thanks. It’s possible that other plugins would cause this sort of problem. You probably are running now, or have run in the past, the kind of plugin that would cause the behavior.

    I’ve opened a bug ticket to discuss the bug and possible fixes: https://buddypress.trac.wordpress.org/ticket/5553#ticket

    For anyone currently affected:
    - By default, BP does not create users with a status greater than Subscriber. This issue only affects people with a role higher than Subscriber
    - If your admin user account does not have access to the Dashboard, I’ve written a small plugin that you can use to repair. Instructions and code are here: https://gist.github.com/boonebgorges/4ee64723ba75caa3c7e1
    - If you need to repair other users, I recommend that you use the bulk update tools at Dashboard > Users

    Note that this is something that only happens during the 2.0 upgrade, so you don’t have to be afraid that it’ll happen again.

    Many apologies for the inconvenience, and thanks for your patience and help as we sort things out.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @lchief – Many thanks for the additional details. I have a suspicion that bp-disable-activation is the culprit. @texrat – Are you by chance running this plugin too?

    I’m going to do some testing and open a bug ticket. I’ll also write a very small drop-in plugin that’ll regrant access to the dashboard. Stay tuned…

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @lchief – You might be onto something. This is supposed to be part of the migration tool to the new setup system. Can you share the following info:

    - Are you running WP Multisite?
    - What is your current registration setting?
    - Are you using any plugins (other than BP) that modify user registration in any way?

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @lchief – Thanks for chiming in! So, just to be clear, you’re finding that (a) edit_posts users are unable to access the Dashboard, even though (b) their capabilities in wp_usermeta are correct?

    Does anybody who’s experiencing the problem mind sharing a database dump with me, or giving me file-level access to their site (plus relevant WP login credentials)? I feel like this is something I could track down if I had access to a site where this is actually happening.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    OK, thanks, that’s helpful. It does sound sorta like you’ve been demoted from WP’s point of view. When you get a chance to access your database or filesystem, please look at wp_usermeta for the ‘wp_capabilities’ key corresponding to your user ID. It should have the word ‘administrator’ in it – but it sounds like it may not.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    The translations should still work for strings that have remained the same. Of course, strings that have changed, or strings that are new in 2.0, will not be translated.

    In any case, there’s no need to translate from scratch. A tool like Poedit will let you update your existing translations against a more current codebase, so you’ll only have to manage updated translations.

    You might also check out http://translate.wordpress.org/projects/buddypress, the official translation hub for BP. If you’re translating into standard Hebrew (ie, you don’t require a custom translation), you should consider using and contributing to the shared Hebrew translation, rather than building it all yourself.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    > I have lost all other functions. I cannot add new items, edit posts, check Jetpack stats, etc. Dashboard link is there but generates error when clicked.

    When you say that you cannot do these things, do you mean that (a) you don’t see the links in the toolbar, or (b) you can’t access the pages that they link to?

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Very weird. More questions, off the top of my head:

    - Logins are generally working correctly, right? Like, the toolbar shows you as logged in?
    - Assuming yes, are you seeing the proper admin-related items in the toolbar when logged in? Eg, are you seeing the “+” dropdown for adding new posts, and the Edit Post button when looking at a post? If so, then WP is definitely recognizing you as an Administrator
    - Are you running any other plugins that do anything related to the current issue? Such as: a plugin that keeps certain users from accessing the dashboard? Or a plugin that lets you modify roles to have custom capabilities?

    Once you get file-level access, it’ll be helpful if you can do a stack trace to get a clearer sense of what’s happening. Let me know if you need help doing that.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Really peculiar. Anything can happen, of course, but I’d be very surprised if upgrading BP demoted your account somehow.

    This is kind of a long shot, but have you tried clearing your cookies and trying again? I wonder if there is some sort of mismatch with your auth cookies (especially if SSL/HTTPS is involved).

    Is your site a multisite network? If so, are you attempting to log in with a super admin account, or just a regular site administrator?

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    What does “lost admin rights” mean? Your user has been downgraded to something less than administrator? Are you being redirected from wp-admin pages? Or are you getting some sort of error message in wp-admin? Or a white screen? Any additional information you can provide would be helpful.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Here’s more on how BP’s template hierarchy works. This is what you’re tapping into. http://codex.buddypress.org/themes/theme-compatibility-1-7/template-hierarchy/

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Thanks for the additional details.

    I don’t have access to the Vertex theme, so it’s hard to give precise instructions. But what you’ll need to do first is to identify whether the theme comes with a full-width (or one-column) page template. I’m guessing that it does. (You can test by creating a test page, then selecting the various Template options from the dropdown under Page Attributes when editing the page. Cycle through them, save the page, and view it on the front end until you find one that displays the page content without the sidebar.)

    Then you’ll need to identify the theme file that is powering this template. The geeky way to do this is by looking at the source code of the Templates dropdown (page_template) and get the value of the option you’ve located. Then find this file in your theme directory wp-content/themes/vortex.

    Then: assuming you’re using a child theme of Vortex, create a directory wp-content/themes/vortex/members/single/. Copy the template you found to wp-content/themes/vortex/members/index-directory.php. That should be all you need to do.

    If you’re not using a child theme of vortex, this change will be overwritten next time you update the theme. In that case, the following filter should be an all-purpose solution. “full-width-template.php” should be replaced with the name of the template.

    
    function bbg_vortex_member_directory_templates( $templates ) {
        $my_template = WP_CONTENT_DIR . '/themes/vortex/full-width-template.php';
        return array_merge( array( $my_template ), $templates );
    }
    add_filter( 'bp_template_hierarchy_members_directory', 'bbg_vortex_member_directory_templates' );
    
    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    What theme are you using? At a basic level, this is a theme-level issue, because the structure of your page templates (two-column vs one-column) is, at root, a question of what’s made available in your theme.

    > remove the sidebar widget area from only the pages after the member subfolder (not all member pages, because I still need a widget for the members page.

    If I understand correctly, you mean that example.com/members/ *should* have a sidebar, and example.com/members/* (any page under /members/) should *not*. If so, you’ll need to include some special BP-specific logic, because from WP’s point of view all pages under /members/ are “the same page”. But the details of how this will be done depend on the kind of theme you’re using.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    It looks like the $group_id is not passed along to the display() method in the same way as it is to the other display methods. That means you’ll need to implement your own technique to get that value. Try this:

    function display() {
        $group_id = bp_get_current_group_id();
        $setting = groups_get_groupmeta( $group_id, 'whatever' );
        var_dump( $setting );
    }

    I do think that you *ought* to be able to get the $group_id inside of display() like you can in settings_screen() etc. I’ve opened a ticket for that, which we’ll fix for 2.1. https://buddypress.trac.wordpress.org/ticket/5533#ticket

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    > the hobbled together mess

    Just to push back a little on this one. There are a couple of key ways in which BP’s current permalink router is not ideal (it’s not amenable to caching; it’s not non-pretty-permalink friendly; it’s hard to write unit tests for it; it leaves some slugs difficult to change). Moving toward the WP Rewrite API is a worthwhile project, because improving on these areas are worthwhile things to do.

    However, it’s important not to overstate the problem. The current system works just fine for many thousands of BuddyPress sites. While there would be new efficiencies and configuration possibilities with a new system, it’s unlikely that their absence to date has ever been a dealbreaker for any BuddyPress site. @synaptic or others, I may be wrong about this, and if there are specific ways that the current router is holding you back, it would be very helpful to know more about those details.

    In any case, while it will require a large amount of work to build a new system that’s compatible with the old, it’s not doing any active harm to existing (or new) sites to use the current (perfectly functional) system. So let’s not get too carried away with the idea of forking our own project :)

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Hi all – Many thanks for the feedback. I’m a bit at a loss, though, as to what’s happening. I guess my best advice, given that you’re running production sites, is to enable some sort of error logging. Then, look through those error logs around the time you expect to see activity posts but do not. It’s possible that there’ll be clues in the error logs to what’s happening.

    Aside from this, it’s unfortunately the sort of thing that can only be fixed if it can be reproduced. So any additional testing you can do to narrow down the conditions under which it happens will be helpful.

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @joesell89 Thanks for the report.

    > nothing new is appearing on the activity stream when I publish a blog post or comment on the forums etc.

    Does this mean that *nothing* is being tracked in the activity stream? Or is it just forum + blog posts that aren’t being tracked? How about new friendships, new memberships, new groups, etc?

    > The site I am running it on has a custom theme and lots of plugins/custom code so it could be a conflict rather than a bug.

    Unfortunately, it could be both – a bug that only arises in the context of other customizations.

    If you can’t toggle things on and off to test, and if you don’t have a sandbox environment – maybe you could check out your error logs to see if anything relevant is being logged there?

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Quick note: If you find bugs and would like to raise them with the team, please post them as separate threads. This thread will not be monitored for bug reports.

Viewing 25 replies - 1 through 25 (of 1,821 total)