Cristián Lávaque

Hi Robert.

The ccaps are stored as capabilities in usermeta. You’ll need to use PHP to get them.

[hilite pre_code]

[/hilite]

That’ll return an array. You’ll need to go throught it and pick out the ones that are s2Member custom capabilities.

The custom field is that whole string. You can explode it in PHP to get the cv1. http://php.net/explode

[hilite pre_code]

[/hilite]

I hope that helps. :)

Okay.

It should be [hilite mono]%%automatic%%[/hilite], not [hilite mono]$$automatic$$[/hilite].

Also, you can just point to a URL, like: http://yoursite.com/wp-admin/profile.php

Have you tried those?

Thanks for the update, we’ll be looking forward to the next one. I hope they give you a solution soon. :)

Hi Stuart.

You can increase the memory limit. http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

I hope it helps. :)

Joe, Dave answered the questions quite well, but I’d like to add a few things:

1. This works PERFECTLY if you have a yahoo email but the subscriber never gets the email for their password if they use gmail? Yahoo mail works 100% of the time but we CANNOT get gmail to work?!?! I already submitted this question to the s2member forum which was answered by telling me to follow the instructions found here: (Knowledge Base » Troubleshooting Email Delivery Problems). I went through every step and still can’t get gmail email addresses to receive a confirmation email upon submitting a form. This is problem #1 – Please help me!!

I agree that it seems like a problem with Gmail not liking your server. If you don’t have your own IP, someone else you’re sharing the IP with may have been flagged for spam. Or who knows what the problem is. You should really contact your web host about this.

This is not an s2Member problem. s2Member uses the wp_mail function, which comes with WordPress.

Did you check if the emails to Gmail addresses are being sent? You can use the email logging plugin. http://wordpress.org/extend/plugins/email-log/

Are other emails from your site to Gmail addresses getting to their inboxes?

Lets say in (s2member>Auth.Net Pro-Forms) each of the forms (Authorize.Net Forms For Level #1 Access – through – Authorize.Net Forms For Level #6 Access) or otherwise (Modules 3 – 8) are setup like this:

I’ll offer the first 0 Days @ $0.00
Then, I want to charge: $50 / Monthly (recurring charge, for ongoing access)

This makes it to where you pay for access to Module 3 and you’re in – One month later it charges you again and now you have access to module 4 – Then 5, 6, 7, and 8.

2. Is this correct or not? Yes or no? If yes, then perfect! If no, can you please explain? :)

It gets tricky. The thing is that the subscriptions in s2Member are for a single level. s2Member doesn’t change the user’s Level after each monthly payment of the subscription. He’d remain at the same level and the new content would need to be dripped with conditionals in the body of the posts/pages.

The way content dripping works currently, is explained here: [hilite path]Dashboard -› s2Member® -› API / Scripting -› Content Dripping[/hilite]. Basically the conditions would be checking how long ago the user paid for the level, and based on that decide whether to show the new content in the drip sequence. It doesn’t check following payments, those times aren’t available, only the first time for the level, and the conditions would be based off of that.

The shortcode for the Auth.Net pro-form has the [hilite mono]rrt[/hilite] attribute available, which you can use to specify the number of terms the payments will recur, instead of going on indefinitely. [hilite path]Dashboard -› s2Member® -› Authorize.Net® Pro Forms -› Shortcode Attributes -> rrt[/hilite]

Now, what normally happens at the end of the last term paid, is what your Auto EOT Behavior setting says. [hilite path]Dashboard -› s2Member® -› Authorize.Net® Options -› Automatic EOT Behavior[/hilite]

Since you are giving lifetime access to the paid modules, you’d need to change the EOT setting so no demotion back to Level 0 happens. This is fine if someone pays all the terms, but if someone stops paying before, then the dripping of content will continue and, since he didn’t lose access, he’ll be shown the coming modules eventually.

Selling the modules individually with one-time payments, which is the one you set up already, is the one that would work for you with s2Member without customizations. From what you said, fixing the Gmail addresses problem would do the trick.

Now, if you want to customize the behavior a bit to do what you want, it may be possible to use the Notifications API in s2Member to load a script created by you, that will change the user’s Level after each new payment.

Video » s2Member (API Tracking/Notifications)
Knowledge Base » Changing Roles/Capabilities via PHP

If the payment doesn’t happen, then the notification won’t happen, so the script won’t be ran and the user won’t be moved to the new level. That would work for what you want. And payments would only be a set number if you use the rrt attribute, as mentioned earlier.

I hope that helps. :)

Hi Marco.

That’d be a problem with the WP parser for shortcodes. I don’t think having it inside an HTML should be a problem. If your table is generated by another shortcode, then maybe nested shortcodes can cause an issue.

Could you show us your code for the table with the button, please? Thanks!

Hi Jim. Sorry for the delayed response.

Let me see, if you use the s2Member custom field to secure pages in a page that doesn’t load any files from your CDN, do you still get the error you mentioned first?

You may have a plugin that’s causing a conflict, it is a possibility, even the theme. A test you can do is use the default theme and reload the page to see if you get the problem. If not, try deactivating other plugins one by one, and see if check the secured page after each. I’d start with the caching plugin, so you can actually see the difference after each change in your tests.

I hope that helps. :)

Hi Kris.

What could have happened is that the user wasn’t logged in to her account when she started the checkout process, so s2Member didn’t relate the payment to the existing account. Instead, it’ll tie the payment to the new account expected to be registered, which is when the New User email happens too. It’s possible the she didn’t create a new account, though, and instead logged in to the existing one. This would explain why the subscr ID isn’t in her profile.

If she’s already paying you through Amazon and now also PayPal, you’ll need to stop one of them so only one keeps going. You should be able to stop her subscription from your side.

I hope that helps!

Thanks for the update, Chad! Glad you sorted it out. :)

This particular attribute isn’t editable in the button generator’s interface, but you can generate the shortcode and then edit this manually without a problem.

s2Member will remove the access by default, but you can change this behavior from [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior[/hilite]. :)

You can use the pro-forms with PayPal Express Checkout too, which may be available in your country, even if PayPal Pro isn’t. Pre Sale FAQs » To use s2Member® Pro Forms, will I have to use PayPal® Pro?

Or use the pro-forms with Authorize.Net, that’s the option you have if you want to get payments on your site, without taking the customer elsewhere.

I hope that helps. :)

Sure, you can control that in the conditions you write to show the content. For example, if a regular member would be shown something after 90 days, then you can also show it after only 30 days to those that have the custom capability “show60daysearlier” or something like that.

[hilite pre_code]
if(S2MEMBER_CURRENT_USER_PAID_REGISTRATION_DAYS >= 90 OR
(current_user_can('access_s2member_ccap_show60daysearlier') AND S2MEMBER_CURRENT_USER_PAID_REGISTRATION_DAYS >= 30))
[/hilite]

Hi Tim.

Let me check this with Jason. I’m emailing him now.