|Posted: Thursday Mar 15th, 2012 at 10:27 am #8236|
I have about 35 columns (fields) of extra data to collect about users which I was planning on adding in S2member. The structure in which this information is stored is concerning me as queries that apply filters to the members database will need to be created so as to get reports (such as ‘.. where member-region = ‘north’ ).
wp_usermeta seems to contain a single wp_s2member_custom_fields row with ALL the extra fields (fieldname1, fileddata1, filedname2, fielddata2, etc) all mushed in together. There are not any obvious tools for filtering / reporting in s2member so I am looking for advice on how best to handle this?
Is it OK just to add tons of additional custom fields?
When exporting the custom fields is there an easy way of reconstructing the data so it looks sensible in a spreadsheet rather than all the custom fields getting out of step in un-labelled columns?
I see that a future release may be handling things differently – if so any possibility of giving some information on what this means and what a -likely- timeline for release is?
Is one way forward to use a third party plugin to handle the additional profile fields? If so any suggestions on which? (ideally something that can appear on a custom profile page such as the one s2member provides easily and allows for some simple reporting.
- s2Member® Products