Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 1,056 total)
  • Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    or even easier for the displayed user id:

    bp_displayed_user_id();

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    That’s more of an s2member question than a BuddyPress one – so, better asked on their forums.

    Anyway:

    In your PHP template for displaying the user, you can add the following code:

    echo get_user_field('s2member_access_label', $user_id);

    and to get the $user_id for the displayed user, you can use:

    global $bp;
    $user_id = $bp->displayed_user->id;
    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    @strangechild — there is some documentation here: http://codex.buddypress.org/themes/theme-compatibility-1-7/theme-compatibility-2/

    The intro is confusing, but if you jump to the second section, it tells you where to find files and where they need to be added to your theme, if you want to override them.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    ok.. props to @hnla

    Defining the constant BP_ENABLE_MULTIBLOG in bp-custom.php fixed the problem.

    @boone – any thoughts on this vs. enabling BP on a site by site basis (as suggested as preferable in your in file comments)? Is activity / members / groups, etc. shared when BP is activated separately for each site?

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    @rameshwormaharjan

    If you look in the implementation bp_has_activities(), you’ll see if no user id is supplied as an argument it will default to the displayed_user id on a member page.

    See lines 316 and 382 of bp-activity-template.php

    If you’re on a non member page it will show activity relative to the logged in user (line 382).

    Try passing the logged in user id as an argument to your bp_has_activities() call, that should override the displayed user default on a member page.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    We’ve used WP FB Autoconnect on a lot of BuddyPress sites – http://wordpress.org/plugins/wp-fb-autoconnect/

    There’s a functional free version, and just a few dollars extra for the pro version

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Sounds like you are using an old / outdated plugin with a recent version of BuddyPress.

    Looks like called wp-cache might be the problem — see if this link helps you http://wordpress.org/support/topic/advanced-cachephp-problems-on-upgrade

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Maybe I’m just confused by the naming:

    I know I can do this by creating my own class named BP_Legacy in my theme and customising, but this doesn’t seem a correct approach.

    Is the BP_Legacy class supposed to behave like a pluggable function? i.e. you are expected to redeclare the class with the same name?

    On a separate but related matter — if I want to create a completely bespoke theme (not theme compat), how do I stop an instance of BP_Legacy being created and registering its actions?

    I’ve tried declaring add_theme_support(‘buddypress’) hooked on to ‘after_setup_theme’, but that doesn’t stop an instance of BP_Legacy being constructed and registering its actions.

    Looking at the BP_Theme_Compat constructor, it would appear that add_theme_support(‘buddypress’) should stop it — does it need to be hooked on to something earlier than ‘after_setup_theme’?

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    You shouldn’t be using Genesis Connect with current versions of BuddyPress.

    From the Genesis Connect developer:

    As of BP 1.7 you do not need to have GenesisConnect. We are currently maintaining it for customers who had BP installs prior to BP 1.7.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Hi R-a-y,

    Yes, had looked at the implementation in the default BP components, and ‘gotten’ my head around it.

    Good to get confirmation that this is the right approach for 3rd party as well.

    Thanks, Roger

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Hey Dan,

    thanks, yes, BuddyDrive looks to have the ‘correct’ solution.

    It creates a BP_Theme_Compat class for the component – the same approach that the internal components (Groups, Activity, etc.) do.

    @boone, @r-a-y … is that the recommended approach for 3rd party components going forward?

    Cheers,
    Roger

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    a gentle 2 day bump

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Resurrecting an old thread, but we encountered the same problem on 1.7 install, and fixed in same way.

    I note the problem doesn’t seem to occur on testbp.org

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    We had problems upgrading a large site – see: http://buddypress.org/support/topic/wsod-in-wp-admin-activating-site-tracking-upgrade-from-1-2-9-1-5/

    I assume some BP script in the backend was timing out.

    We solved by:

    1. exporting our users / user_meta table. Leaving just the admin user
    2. upgrading BP
    3. Reimporting the users

    This worked fine. The problem only occurred if all the users were present during the actual upgrade process.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Depending where the links are being added / submitted, you might also be able to add a filter in your PHP code to strip them out.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    @r-a-y — looks like your reply and my edit with thanks crossed!

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Have the solution — the code to implement the BP_Legacy class in buddypress-functions.php had changed between beta and full release.

    I needed to update the buddypress-functions.php file in our theme to match these changes.

    @r-a-y: thanks for getting back to me. Yes, this is a considerable build based on the new theming approach — it’s been about 4 months in development (with a number of devs involved). We’d seen it through a number of alpha / betas of 1.7, so was a bit of a shock when the WSOD appeared! Anyway, that problem sorted now.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    @shanebpdev – sorry, just seen your comment. Thanks for the feedback.

    The client is partnered with a publishing company, and uses the publishing company’s servers — unfortunately, I don’t have too many details on the specification — concentrating on the development side of this project.

    At one stage, we had considerable server problems (when we were handling 100 / 1000s of new member registrations each day). I suspect though that this was due in no small part to the number of DB queries being fired off on each page view. Hopefully, that issue is considerably reduced with 1.7+. We’re still 1.6.x for Enterprise Nation.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Problem is that groups_create_group() doesn’t set the total_member_count — so subsequent calls to set up the Groups Template fail to load the groups.

    We worked around by explicitly setting: groups_update_groupmeta( $group_id, ‘total_member_count’, (int) groups_get_groupmeta( $group_id, ‘total_member_count’) + 1 );

     

    Will add to trac as bug.

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Hasn’t @ray already raised this on the trac?

    We’ve also been having issues with activation links not redirecting correctly in 1.7

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Yep, it’s one of the most useless things in BuddyPress.

    You can get rid of those links by adding the following to your bp-custom.php file:

     

    function remove_xprofile_links() {

    remove_filter( ‘bp_get_the_profile_field_value’, ‘xprofile_filter_link_profile_data’, 9, 2 );

    }

    add_action( ‘bp_init’, ‘remove_xprofile_links’ );

     

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    This is another example of directory features we built for a BuddyPress site: http://www.enterprisenation.com/business-directory/

    It’s based around custom post types & taxonomies, and integrates as a component with BuddyPress profiles.

    But, in response to OP @giannisff, these directory systems are custom builds – there’s no good off the shelf plugin providing the solution.

     

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    Avatar of Roger Coathup
    Roger Coathup
    Participant

    @rogercoathup

    The author of ‘friendpress’ took several snippets of code written by other people, and tried to package them in a plugin.  From other people’s feedback, I don’t believe it ever worked.

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