• I moved a site to Godaddy, who puts a prefix on the table names, and discovered that ‘wp_bp_xprofile_data’ is hard coded into line 2046 of export-user-data.php:

    $user_search->query_from .= " JOIN `wp_bp_xprofile_data ` XP ON XP.user_id = wp_users.ID ";

    As a workaround I changed that to:

    global $bp, $wpdb;
    $bp = buddypress();
    $user_search->query_from .=  " JOIN {$bp->profile->table_name_data} XP ON XP.user_id = {$wpdb->users}.ID ";

    So that it’ll look for the correct table.

    • This topic was modified 8 years, 2 months ago by cwjordan.
    • This topic was modified 8 years, 2 months ago by cwjordan. Reason: trying to get the code tag to include backquotes
    • This topic was modified 8 years, 2 months ago by cwjordan.
    • This topic was modified 8 years, 2 months ago by cwjordan.
Viewing 1 replies (of 1 total)
  • Plugin Author qstudio

    (@qlstudio)

    Thanks again @cwjordan.

    We’ve almost run out of steam to keep going on update of this plugin for the time being – I hope to be able to make some time over early winter to push an update and I’ll be sure to include this patch.

    By the way – if you wanted to become an official contributor and take over some of the updates – just let me know ??

Viewing 1 replies (of 1 total)
  • The topic ‘Hard coded table prefix wp_bp_xprofile_data’ is closed to new replies.