Page 1 of 1

Export of S2member standard and custom fields

PostPosted: September 29th, 2011, 8:09 pm
by cwaorgnz
Hi

I am new to S2MemberPRO and I purchased this to have the ability to export out to CSV the member information stored including the custom fields I added.
I used both the default and easy read option but the custom field information comes out in a different format to the standard fields with the name of the custom field beside the data instead of above it like the standard fields and makes it difficult to read and use without having to manually adjust the data.

Is there another way of exporting out the member data where all the headings of the fields are on the top row and the data is below this corresponding to each field?

Thanks

Re: Export of S2member standard and custom fields

PostPosted: October 1st, 2011, 4:54 am
by Cristián Lávaque
No, sorry. At this moment that's how the custom profile fields are exported. Only those fields with a value are added to the row in pairs of field name and value.

Support to have a column for each field may be added in a future release, but there's no date for that.

Re: Export of S2member standard and custom fields

PostPosted: October 4th, 2011, 5:03 am
by cwaorgnz
I am disappointed to see this, paid for Pro version export capability to find it does not adhere to standard CSV format which was not stated in functionality. Would have thought this should have been a given to export in standard first row is field names, then all rows after this are the field values, I will not be rating this well :-(

Re: Export of S2member standard and custom fields

PostPosted: October 7th, 2011, 8:38 am
by carblanco
Same problem here, did you find a solution?

Re: Export of S2member standard and custom fields

PostPosted: October 7th, 2011, 11:14 pm
by cwaorgnz
Hi,

not yet, I am going to find a friendly person to see of there is a way I can extract the data directly from where the data is stored. I will let you know when I have found out :-)

Re: Export of S2member standard and custom fields

PostPosted: October 8th, 2011, 2:06 am
by carblanco
cwaorgnz wrote:Hi,

not yet, I am going to find a friendly person to see of there is a way I can extract the data directly from where the data is stored. I will let you know when I have found out :-)

Ok, keep me posted. Thx.

Re: Export of S2member standard and custom fields

PostPosted: October 11th, 2011, 7:25 pm
by cwaorgnz
Hi Cristian,

I would appreciate it if you please advise the name of the database that the custom fields are stored in so I may export them myself directly. I have reviewed the list of Word Press databases and cannot see anything obvious and cannot see any of the fields inside WP_USERS database ( did not expect to find them there either).
If you do not want to post this on the forum, please send to my email address treasurer@cwa.org.nz

thanks

Lindsay

Re: Export of S2member standard and custom fields

PostPosted: October 12th, 2011, 6:10 pm
by Cristián Lávaque
They are saved as a serialized array in a row of the usermeta table.

Code: Select all
$s2_custom_fields get_user_option('wp_s2member_custom_fields'$user_id); 


I hope that helps. :)

Re: Export of S2member standard and custom fields

PostPosted: January 4th, 2012, 3:19 pm
by philipt18
I have to agree with the others here that it is a bit absurd to use a non-standard format for the export. One of the features of the Pro version is touted as 'Advanced User Import/Export Tools' and was the primary reason I upgraded as well. I think you need to fast-track being able to put each field into its own column as a new feature, as you in reality have no way to export the full user list with all fields in any format that people can use. Don't take this the wrong way, but it cannot be described as 'Advanced' when it is non-standard and unusable. Please fix this, and soon.

Re: Export of S2member standard and custom fields

PostPosted: January 15th, 2012, 12:59 am
by Wendell
Agree with philipt18. I'm currently looking for an alternate solution, as the Pro version export is lousy at best and there doesn't seem to be any interest in making it work properly and to standard.

Furthermore, I've just tried a new export and I get unrecognizable characters, no discernible text.