Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 26 through 50 (of 1,007 total)
  • @rogercoathup

    Participant

    a gentle 2 day bump

    @rogercoathup

    Participant

    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

    @rogercoathup

    Participant

    We had problems upgrading a large site – see: https://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.

    @rogercoathup

    Participant

    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.

    @rogercoathup

    Participant

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

    @rogercoathup

    Participant

    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.

    @rogercoathup

    Participant

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

    @rogercoathup

    Participant

    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.

    @rogercoathup

    Participant

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

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

    @rogercoathup

    Participant

    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’ );

     

    @rogercoathup

    Participant

    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.

     

    @rogercoathup

    Participant

    @rogercoathup

    Participant

    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.

    @rogercoathup

    Participant

    As I said previously, the group_id is passed as the first parameter to the action.

    You need to add the parameters to your function.

    If you are not familiar with writing action functions in WordPress, you should read here: https://codex.wordpress.org/Function_Reference/add_action

     

    @rogercoathup

    Participant

    If it’s on the members page, use a bp function to get the user_id, e.g. bp_displayed_user_id(), and pass that to your loops.

    The call you are using to get the queried_user_id is not going to work on a BuddyPress member page.

    @rogercoathup

    Participant

    The groups_join_group action gets passed the group_id as its first parameter:

    e.g. do_action( ‘groups_join_group’, $group_id, $user_id );

    So, you have the group_id already.

     

    Interestingly, there doesn’t seem to be a function to get the creator – so, you would then either have to:

    Create a new BP_Group instance using the group_id, and directly access the it’s ->creator_id attribute, or
    Make a direct SQL call on $bp->groups->table_name to return the creator_id where the id = group_id

     

    @rogercoathup

    Participant

    Which theme are you using?

    Find that out, and edit in:  /wp-content/themes/your-theme/members/single/member-header.php

    If you haven’t got your theme structure setup correctly – then you need to do that first of all — have a look at the advice on theme development, theme structures on wordpress.org.  The documentation on buddypress.org also has advice on building child themes from bp-default, and on adapting existing wordpress themes (see template pack pages).

    @rogercoathup

    Participant

    @rickkumar – I noticed loginradius have been spamming the Internet with fake users / testimonials for their product — so probably good to avoid that one.

    If you are looking for another free solution – you can investigate HybridAuth.  That one’s a PHP library, rather than a plugin, so you’d have to do some coding, but on the positive side would gain a lot more flexibility.

    @rogercoathup

    Participant

    It’s really badly named — very confusing.  You’re not the first person to not know that ‘send public message’ means post update on user wall.

    On the bright side, by adapting Brajesh’s plugin for 1.6, you’ll have learnt a lot more about coding for BuddyPress

     

     

    @rogercoathup

    Participant

    ‘send public message’ built in to 1.6+ provides this functionality — posting to another user’s wall

    @rogercoathup

    Participant

    Yes, they violate guideline 10.

    It’s a shame the guidelines don’t also include ‘spam / misleading marketing’

    @rogercoathup

    Participant

    @mercime – throwing their plugin out of the repository might be a good way of dealing with them!

    It might be a good idea to unlink their link in this thread as well — take away their SEO juice — are you able to do this?

    @rogercoathup

    Participant

    You don’t need to uninstall the plugins, you can just de-activate them (wp-admin will let you do that en masse).

    You can then reactivate one at a time – their settings will have been saved in the DB.

     

     

    @rogercoathup

    Participant

    See this other recent thread: https://buddypress.org/support/topic/best-way-to-enable-facebook-login/

    There’s also an OpenSource PHP library that you might want to investigate called HybridAuth: http://hybridauth.sourceforge.net/index.html

    @rogercoathup

    Participant

    @mercime — oa-social-login is from the company I referenced: One All

    As with the others, there is a free version, but you have to pay monthly subscriptions for their service if you want more features, users, etc.

Viewing 25 replies - 26 through 50 (of 1,007 total)
Skip to toolbar