Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Avatar of houfton
    Houfton
    Participant

    @houfton

    @mindyjoy do you have access to the database, eg through your Control Panel and phpMyAdmin?

    It might help to look in there to see what is going on.

    In the wp_users table there is a ‘user_status’ column. I don’t think WordPress uses it but BuddyPress does and so do these plugins (I believe). Active Users are ’0′ unactivated are ’2′.

    There is a ‘user_activation_key’ column but I think the relevant keys are found in the wp_usermeta table. Search the ‘meta_key’ column in that table for ‘activation_key’ and the keys will appear in the ‘meta_value’ column.

    Hopefully those tables should tally with what is shown by the plugins. Or else you could email your users with the keys…

    Avatar of houfton
    Houfton
    Participant

    @houfton

    I have gone for Unconfirmed too. It does everything that Pending Activations did without any hacking.

    Avatar of houfton
    Houfton
    Participant

    @houfton

    The link that was stripped from my last post is (hopefully):

    http://make.wordpress.org/core/2012/12/12/php-warning-missing-argument-2-for-wpdb-prepare/

    Avatar of houfton
    Houfton
    Participant

    @houfton

    BuddyPress Pending Activations has not been updated for quite a while now – back in 2011 I think – and it is not ‘officially’ compatible with WordPress 3.5 or BuddyPress 6.

    I have just tried it on a test site with these latest versions and it does seem to be working for me.

    It does however create Warning errors (which will show up in admin if you have display_errors turned on) because it still uses the prepare() function with one argument. See for an explanation.

    The warnings I get are like
    Warning: Missing argument 2 for wpdb::prepare(), called in /xxx/wp-content/plugins/buddypress-pending-activations/bp-pending-activations.php on line 18 and defined in /xxx/wp-includes/wp-db.php on line 990
    Warning: Missing argument 2 for wpdb::prepare(), called in /xxx/wp-content/plugins/buddypress-pending-activations/admin/bp-pending-activations-admin.php on line 6 and defined in /xxx/wp-includes/wp-db.php on line 990

    If you want to hack the plugin to stop the errors I think there is one instance in bp-pending-activations.php and several in bp-pending-activations-admin.php.

    Avatar of houfton
    Houfton
    Participant

    @houfton

    I think the answer to this is to use an ampersand. My version also has “&type=alphabetical” but that is optional:

    `bp_has_members( bp_ajax_querystring( ‘members’ ) . ‘&type=alphabetical &per_page=50′ )`

    Avatar of houfton
    Houfton
    Participant

    @houfton

    I don’t think this has been fixed yet with WordPress 3.4.1, BuddyPress 1.5.6, BP Group Management 0.5.4 and BuddyPress Group Email Subscription 3.2.1.
    My ‘solution’ is to remove it completely using my functions.php file. It is not ideal but better than having a facility that does not work:
    `remove_action ( ‘bp_group_manage_members_admin_item’, ‘ass_manage_members_email_status’ );`

    Avatar of houfton
    Houfton
    Participant

    @houfton

    I have found the same problem. The “Email status:” is shown but it is wrong and the facility to “Change to:” a different status does not work. It just goes to your own frontend profile and gives the message “User email status changed successfully”.
    This is with WordPress 3.4.1, BuddyPress 1.5.6, BP Group Management 0.5.4 and BuddyPress Group Email Subscription 3.2.1.
    My ‘solution’ is to remove it completely in my functions.php file. It is not ideal but better than having an facility that does not work:
    `remove_action ( ‘bp_group_manage_members_admin_item’, ‘ass_manage_members_email_status’ );`

    Avatar of houfton
    Houfton
    Participant

    @houfton

    I think I have answered my own question… the relevant add_action seems to be ‘xprofile_updated_profile’.

    Avatar of houfton
    Houfton
    Participant

    @houfton

    I take your point, thank you. I should probably use a list rather than divs. The main thing is I want to be able to manipulate the layout using css.
    [deleted rest: just my stupid mistake!]

    Avatar of houfton
    Houfton
    Participant

    @houfton

    In case anybody is interested (!) I found a solution using the bp_field_css_class function: `<div>`. This gives my divs a class name based on the field name eg: `

    `.

    The trouble I have now is that the profile loop seems to be ignoring the styles in my child theme’s style.css file – apart from the body tag styles which it applies. I can’t work that one out at the moment.

    Avatar of houfton
    Houfton
    Participant

    @houfton

    Thank you. That seems very obvious now you say it!

    I have been trying to add ids to my divs using a sanitised version of the field name eg First Name becomes `

    `.

    I have tried using WordPress functions like `sanitize_title(bp_the_profile_field_name())` but this does not work. How should it be done?

Viewing 11 replies - 1 through 11 (of 11 total)