basvanschaik

On an unrelated note: the script ran out of memory (limit: 128M) during the export, resulting in a blank page (and an error message in Apache’s error log). Adding

ini_set(‘memory_limit’,’256M’);

solved it for me.

Same issue here, solved it by adding a single line of code to initialise Buddypress (for xprofile).

Around line 159 of export-user-data.php (after check_admin_referer(…)), add:
do_action(‘bp_init’);

When omitted, the $bp global remains uninitialised, and all Buddypress queries silently fail (the table names are not initialised, which makes the queries invalid). Consequently, BP_XProfile_ProfileData::get_all_for_user($user->ID) returns an empty array, conveniently suppressing any SQL errors that arose.

Note that I’m using an older (and heavily modified) version of Buddypress – it might work out-of-the-box on more recent versions.

I tried to do the same thing, but it doesn’t work. Turns out that calls are carried out in the following order:

– add_action(‘bp_include’, ‘bp_em_init’) in events-manager.php
– something I haven’t quite figured out yet
– actual call to bp_em_init() function in events-manager.php
(…)
– function.php in theme with remove_action(‘bp_include’, ‘bp_em_init’)

As you can see, the ‘remove_action’ call occurs after the actual call to the bp_em_init() function in events-manager.php.