Cristián Lávaque

Great. :)

When you switched the theme and you say it worked, what were you testing? The generator in admin or the shortcode in a page?

The JavaScript problems are usually caused by the theme/plugin not adding its JS to WP correctly. It needs to be done with [hilite mono]wp_enqueue_script[/hilite]. http://codex.wordpress.org/Function_Reference/wp_enqueue_script

If you use the HTML code for the button, then you need to have a PHP execution plugin, because there’s a bit of PHP there. Or you can replace those PHP bits with the shortcode equivalents. [hilite path]Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants[/hilite]

I’d take it off and use the Level for that content’s restriction, instead of the ccap. If you use the ccap, then you won’t be able to remove that access without getting it mixed up with the other ccap.

Thank you soooo much for your help and you patience :)

You’re welcome! I’m glad I could help you. :)

Yep, that sounds right.

The only trouble I can see is if someone starts the Level 1 subscription, then buys the sockerfri ccap, and then ends the Level 1 subscription: he’ll be demoted to Level 0 and the ccap removed.

You’ll need to use a hack to avoid ccaps being removed on demotion and not have that problem. Move the file s2member\includes\classes\auto-eots.inc.php to the /wp-content/mu-plugins/ folder and comment out this:

I hope it helps. :)

If it’s paid monthly, then you have to sell a Level, the ccap can’t be sold with a subscription, it’s the level that can and you add the ccap to that sale.

Remember, too, that when the EOT demotion happens, the level is dropped to 0 and all ccaps are removed, even the ones sold without expiration. So it can get complicated to mix things like these with the current s2Member.

• This reply was modified 4 years, 3 months ago by  Cristián Lávaque.

By the way, in case there’s a misunderstanding with “independent” in Independent Custom Capabilities, that’s because they aren’t being added to a role, but the user, they’re independent of the WP role the user has. So it’s not like they’re independent so only one can be sold at a time, you can sell several at the same time too, just wanted to make that clear.

Hi Novo.

Do you mean the New User email sent on registration, which includes the username and password? [hilite path]Dashboard -› s2Member® -› General Options -› Email Configuration -> New User[/hilite]

Yes, it works, but in that case you have to set it yourself, because there won’t be a ccBill notification to make it happen.

Greg, good news! Another user shared a solution for his AWeber problem similar to yours. We weren’t aware of it, that’s why I had not suggested it, but now I updated the knowledgebase article and am letting you know about it to try it. http://www.s2member.com/forums/topic/aweber-integration-problem-resolved/

I hope that does the trick! :)

Ah, great! Thanks for the update. I’m very glad you found the cause and were able to fix it. :)

Okay.

Could you send me your site’s info? I’d like to take a look at this. s2Member® » Private Contact Form

Thanks. :)

Hi Mark.

1. Why can’t you make it so the button generator works?

The generator works normally, and so does the shortcode. If you’re having trouble, then it’s something specific to your installation. I’ll help you find what the problem may be.

First we’ll check for a JavaScript conflict, since this is what was found to affect the generator in the past. To test the theme, change it temporarily to the default TwentyEleven and try if the problem continues. To test other plugins, deactivate them one by one, testing after each if the problem continues. Once you found the culprit, it can be fixed or replaced.

Now, if you got as far as PayPal, then should I assume that you could use the generator, but the code didn’t work? In that case, you may have a parsing problem or a content filtering problem, also most probably caused by the theme or a plugin. Test as above, but checking the page where the button is instead of the generator.

2. What is the manual method for doing this so that I can upgrade a user even if I have to manually create the button at PayPal?

The PayPal created button works for new registrations only, existing accounts can’t be upgraded with it because it lacks the user info s2Member adds to the button in those cases, to relate the order to that account. The s2Member button generator needs to be used so it works properly.

Please let me know how it goes with the tests I explained above. :)

Okay, the configuration seems okay, except for one thing: the Clerk API is set to read/write in ClickBank, but the s2Member panel says just read. [hilite path]Dashboard -› s2Member® -› ClickBank® Options -› Account Details -> Clerk/API Key (Read Access)[/hilite]

I didn’t change it myself, because I don’t know if that account is tied to some other thing you’re using, that’d require that. Could you make that change to read in the Clerk API and do a test transaction? Or let me know if I can change it and I’ll do that to continue the test and look at the logs.

Thanks. :)

Doesn’t need to be a separate page for each user, it can be a single WP page where you use variables to customize the data for each.

These may be useful:
[hilite path]Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants[/hilite]
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals[/hilite]