|Posted: Tuesday Nov 20th, 2012 at 12:47 pm #32114|
I have been holding off development of a members directory and collecting anything other than minimal information from my users for 9 months now, and can probably hold off just into the New Year. It is becoming pressing however to find a solution.
If I build something with AMR users and try and get it to ‘play nice’ with S2 Member it looks like something can be wrestled into place with a certain amount of effort ( see http://wpusersplugin.com/3086/user-lists-and-filtering-with-s2member-fields/ ).
I am unclear however if it is best to add custom fields to S2 member (ugly) or to AMR? Either way at such time as a hoped for upgrade to S2 Member might arrive supporting public members directories (and custom fields that are not all mashed into one user-meta record), which approach is likely to present the easier migration path?
Either way doing anything ‘interim’ is likely to end up taking a lot of extra time – so I guess I am really asking if there are any tips on how to make it as smooth and fast as possible. Obviously should there be any Christmas cheer in the form of a beta release of S2Member on the way this would be fantastic!
- s2Member® Products