Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 42 total)

  • Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Well, you said that content needs to be fully public, so I guessed that full protection of BP’s content didn’t worry you.

    Apart from that, the only thing really missing from the Woo bundle is account area integration, but there is another plugin that deals with that:

    https://themekraft.com/products/woocommerce-buddypress-integration/

    It’s meant more for the shop side of WooCommerce, but it seems to do the trick.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    @henrywright Like I said… off the top of my head 🙂


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Actually, ‘Admin’, ‘Everyone (Admin Editable)’ and ‘Only Me (Admin Editable)’ are not part of BuddyPress and are added by the plugin.

    If you use the plugin and set the field visibility to ‘Only Me (Admin Editable)’ then the field will only be visible to the user and the Admin. You could also use the ‘Admin’ settings to, for example, add notes about the user that the user can’t see.

    The plugin initially sets the admin to be the main admin account, but it gives this code snippet in its FAQs to enable you to set the capability required, so editors can also see the field:

    function custom_profile_fields_visibility() {
          return ‘edit_others_posts’; // Editors
    }
    add_filter( ‘bp_admin_only_profile_fields_cap’, ‘custom_profile_fields_visibility’ );

    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Off the top of my head, it should just be a case of :

    $needs = explode( ", ", bp_member_profile_data(‘field=School Needs: Social Welfare’) );

    Which should then put an array into $needs like this:

    Array
    (
        [0] => Environmental programmes
        [1] => Sports development
    )

    http://php.net/manual/en/function.explode.php


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    If getting your hands dirty with SQL scares you (like it does me) BP has its own functions:

    $member_type = "doctor"; // slug of member type
    if ( bp_has_members( array ( 'type' => 'alphabetical', 'per_page' => 1000, 'member_type' => $member_type ) ) ) {
    	while ( bp_members() ) : bp_the_member();
    		// code
    	endwhile;
    }

    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Try the WooCommerce Members bundle… https://woocommerce.com/products/woomembers-bundle/


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    I know it’s not quite what you’re looking for, but you could always just disable profile uploading in Buddypress’ settings and encourage your users to set up a Gravatar account.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    I know it’s not quite what you’re looking for, but you could always disable profile uploading in Buddypress’ settings and encourage your users to set up a Gravatar account.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Try this plugin. It hasn’t been updated for 2 years, but it works perfectly for me.

    BuddyPress Admin Only Profile Fields

    Adds these options to the visibility options: ‘Admin’, ‘Everyone (Admin Editable)’ and ‘Only Me (Admin Editable)’

    Hope that helps


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    I don’t have a problem – I have BP & WP installed on 2 sites and have never had an issue, so I suspect it’s a co-incidence.

    You’ll need to do some investigation to find out what is actually causing the error. Start by changing your wp-config.php file to write an error log. Find the line which says define('WP_DEBUG', false); and change it (plus adding the other 2 lines) to:

    define('WP_DEBUG', true);
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    Then try to view the site again. It will create a new file in the wp-content folder called debug.log. This is a text file with all of your errors in. Hopefully you’ll see a fatal error or something which identifies where the error occurred.

    Hope that helps.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    As far as I know, there’s no way to do that with BuddyPress’ built-in tools.

    However, it is possible with plugins such as the one you identified.

    I had a similar requirement and ended up doing it by utilising BP’s Member Types functionality (which require a plugin or custom code to set up), a plugin called BuddyPress Xprofile Member Type Field to map that to an xprofile field (so that the user can change it herself… it was the easiest way I found to add that to the user’s profile, although there might be a better way), all tied together with custom code to patch in to the xprofile_updated_profile action to check what the change is and then use the groups_accept_invite() and groups_remove_member() functions to change the membership accordingly.

    I know that’s not very detailed, but due to lots of other functionality, such as adding to email lists, my code ended up being quite complex, so it’s not possible to paste it here.

    Hope that helps


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Add this to your CSS:

    #buddypress div.item-list-tabs ul li a span { float: left; }


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    groups_accept_invite( $user_id, $group_slug );


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Hi. I struggled with this for a while, and I agree entirely that something like this needs to be in the BuddyPress core… actually, I think much better user management needs to be in the WordPress core, not just BuddyPress, but that’s a discussion for another time…

    I eventually found the code that you’re using and modified it to be able to ignore all users with a specific WP role or roles, thus removing the need to hard-code specific user IDs.

    To manage user roles you’ll need a plugin such as User Role Editor by Vladimir Garagulya and create a new role that you assign to users who you want excluded (I chose “suspended”). If you use URE you can assign this as an additional role to the main one that WordPress allows you to set.

    The code is here: http://pastebin.com/9xYALGfR, but I’m no PHP expert, so offer no assurances… all I can say is that it works for me 🙂


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    https://buddypress.trac.wordpress.org/ticket/7395

    First time I’ve ever done that!

    Thanks


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Seems to me that BuddyPress could be extended to do all that… with a lot of custom coding.

    Or, a quick Google brings up loads of alternatives: https://www.google.com/search?q=wordpress+jobs+board+plugin


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    On my install, ‘forums’ is singular – ie, ‘forum’.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    This will turn off registrations altogether, thus removing the BuddyPress missing page nag:

    Go to your WordPress’ Settings > General page and uncheck Membership Anyone can register

    Don’t know how that will effect your theme’s registration, though…


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    You don’t say how you’re using them.

    My usage is:

    define ( 'BP_DEFAULT_COMPONENT', 'profile' );
    define ( 'BP_GROUPS_DEFAULT_EXTENSION', 'forum' );

    to change the default view in the user’s profile to ‘profile’ and the group to ‘forum’.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    I’m using a child of the bp-default theme, and I haven’t overridden the activity template.

    A search of the files in the buddypress/bp-themes/bp-default folder turns up nothing, so I’m guessing not.


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    🙂

    Nope, not permalinks.

    Not sure how that would effect the routine that adds the entry to the menu though!

    Cheers


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Sorry, @hnla, didn’t mean to offend! In my experience, if something doesn’t work and then you’re advised to change it to something else that does work, it usually means the original was wrong!

    Don’t suppose you have any insights into why it’s still not adding the entry to the Show menu?

    Cheers!


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Hmm… just come across some other problems.

    1. The codex example still isn’t inserting the entry into the Show drop-down menu.

    2. I have a post type called “document” and that isn’t working at all, although my others are.

    Finally, and this is just an observation, but I wonder why all of this is necessary. The WordPress function register_post_type() already allows you to set singlular and plural labels for post types – surely it would be better for the bp_activity_set_post_type_tracking_args() function that we’re modifying here to use these labels by default?


    Peter Hardy-vanDoorn
    Participant

    @petervandoorn

    Thanks all for this. I can confirm that it has solved the problem.

    I had already worked out that 'component_id' => buddypress()->activity->id was wrong and should be 'component_id' => 'activity', but it’s interesting to find that the source of the problem was that the codex example was (and still is, btw) hooking into the wrong action.

    Now, on a related note, does anyone know if it’s possible to insert the name of the post into the 'bp_activity_new_post' parameter?

    Cheers

Viewing 25 replies - 1 through 25 (of 42 total)
Skip to toolbar