Community Support Forums

Re: Member profile public if Member Paid

2011-08-17T03:38:57-05:00

Hi guys. Sorry Mungo, I had not seen your first post until now.

For a page with only level 1 users, you could try something like this:

Code:: $users = get_users('role=s2member_level1'); foreach ($users as $user) { echo '' . $user->display_name . ' '; } ?>

I hope that helps.

Statistics: Posted by Cristián Lávaque — August 17th, 2011, 3:38 am

Re: Member profile public if Member Paid

2011-08-16T14:33:16-05:00

Hi Mungo,

I have joined the forum today and I am looking to do exactly the same as you. That is display a directory of all of the members. Did you find a solution?

Best Regards
Stewartadc

Statistics: Posted by stewartadc — August 16th, 2011, 2:33 pm

Re: Member profile public if Member Paid

2011-02-03T09:56:28-05:00

Hello again,

I'm bumping this as there haven't been any responses and well... I'm feeling a bit sad about that

Maybe I wasn't clear enough:

The site is a free, public listing of all our members.

The members should be able to register and pay to be listed - i.e. if they register and pay they show up in search results.

All the examples given in the code restrict content based on current_user - which makes no sense for the scenario I am trying to create.

Does anyone know how I might go about achieving this with S2member or even know of any other plugins that might help?

Cheers
Mungo x

Statistics: Posted by Mungo — February 3rd, 2011, 9:56 am

Member profile public if Member Paid

2010-12-18T12:25:34-05:00

Hi,

I have looked through the discussion board and documentation for s2member, but can't see anything like this (or find anything anywhere else for that matter) so any help would be very much appreciated.

I would like to create a site that will take annual subscription payments and custom member profile data which is then displayed on the site as a searchable list of member profiles as a directory of services.

The members data must always be available to the public for free, but the member data must be removed from the directory if the member cancels their subscription.

All the documentation seems to suggest that the only thing s2member does is restrict access to content (in a multitude of ways) for the current_user.

It seems like quite a simple thing to achieve, but I am at the point of looking into developing with the paypal API and while this is OK, I'd rather not re-invent the wheel if there is something that would so this available already.

Any ideas?

Cheers
Mungo

Statistics: Posted by Mungo — December 18th, 2010, 12:25 pm