We’ll push this update tomorrow, if anyone wants to test it before.
Posting here since the support site looks dormant.. I’ve had this problem for a while, went searching today, found this recent release and tried out 1.2.8, but same results, with a few strange clues.
WP, BP, EUD all latest versions.
One xProfile field, a text area (with data which was mostly manually imported on its own), exports fine; all ~15 other fields export blank. All xProfile Field Update Times export fine.
Before I turned WP Engine’s object caching fully off for further testing, I noticed that if I manually visited the frontend of a user’s profile, that user’s xProfile fields would show up in the next test export. Once, when I cleared all object/transient caches and re-ran the xProfile field export, all fields exported, but using only the first user’s data for all xProfile fields (correct data was used for user ID).
In all subsequent cache clearings, any users’ profiles I had visited individually that showed up in previous test exports went back to blank.
I can’t think of anything else to tweak or try in order to make all xProfile fields show data. Do any of those specifics help at all? i can try to dig through and interpret logs with a little guidance. Thanks–
(PS, just found/tried wp-users-exporter which hasn’t been updated in a year+, and the UI is a little janky, but seems to export these xProfile fields just fine. Weird. anyway, no urgency for my part (now).)
Thanks for your message, sounds like you’ve done some solid research.
Oddly, we run all our tests on a WPEnging hosted BuddyPress site ( with about 5000 members ) and for us, the xProfile data exports – visiting profiles and priming the object cache does not have a noticeable influence here.
However, when I get some time – I will run some additional tests.
You can check your error logs using the latest version of this plugin on GitHub and WP_Debug set to true to get some additional info.
Perhaps you can stage your site on WPE and run the tests again – the staging version should have no caching and might give some more clues.
In our own testing, we’ve not run into this issue – but check the new log() commands in the plugin which allows for better debugging.
