Cristián Lávaque

Sorry I forgot you said that in the first post.

I’m sorry I couldn’t reproduce the problem you’re having. I’m just suggesting the things I’d try myself in case they help you.

Like trying raw tags around your code, or try other PHP execution plugins. Did you try those?

Thanks for your tests and detailed feedback. I’ll forward this to Jason to review it.

Cristián Lávaque said:
But you need something like the custom capabilities

Regarding what I said earlier about not being able to use ccaps to restrict access to bbPress, here’s a possible solution that Jason told me about: http://www.s2member.com/forums/topic/visitors-blocked-from-bbpress-why/#post-50991

I tried to test the free registration, but when I attempt to load your site, I get a redirection problem to wp-signup.php and can’t open it. This wasn’t happening the last time I visited it. Could you let me know when it’s online again so I can try the free registration?

I have another domain with an entirely different theme and less plugins. What I’m going to do is start using s2member pro on that see if they problem remains. Will let you know.

Cool.

No problem. :)

Cool. The redirection works, but the page you’re pointing to is the one with ID 2202, which will redirect the user to the Membership Options page, because the URL in the redirection doesn’t have the access credentials, he’ll get the access link in the confirmation email. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Specific Post/Page Confirmation Email[/hilite]

To redirect him to the protected page after payment, you’ll need to generate the access URL behind the scenes and then redirect him there. So your [hilite mono]success[/hilite] attribute’s URL could be

success="http://clubedasvendas.com/?success=%%sp_access_url%%"

and in a hack have something like this (not tested):

Create this dir/file: /wp-content/mu-plugins/s2hacks.php
Knowledge Base » Hacking s2Member® Via Hooks/Filters
[hilite pre_code]
http://adambrown.info/p/wp_hooks/hook/wp_loaded
http://php.net/manual/en/function.urldecode.php
http://codex.wordpress.org/Function_Reference/wp_redirect

Thanks for your patience, Timothy. Here’s what Jason said:

Jason Caldwell said:
How to reproduce the behavior:

– Sell a yearly recurring subscription with an Authorize.Net Pro Form. (e.g. [hilite code]rt="Y"[/hilite] and [hilite code]rr="1"[/hilite]).
– Signup today and use a credit card that is good today, but it expires before this time again next year.

What happens is that s2Member charges you today for a full year (and you get in no problem); but s2Member does NOT create an ARB, because it’s not possible. Your credit card will expire before next year comes around.

You will see this in your authnet-api.log file (e.g. the charge for today’s transaction).

array (
  0 => '1',
  1 => '1',
  2 => '1',
  3 => 'This transaction has been approved.',

Followed by s2Member’s attempt to create the ARB to handle billing next year.

array (
  'response_reason_code' => 'E00018',
  'response_code' => 'E00018',
  'response_reason_text' => 'Credit Card expires before the start of the subscription.',
  'response_text' => 'Credit Card expires before the start of the subscription.',
  '__error' => 'Error #E00018. Credit Card expires before the start of the subscription.',
)

s2Member ignores this error, because you did pay for a full year today. So you’re good for a full year. Instead of producing an error during checkout, we let this slide through, and instead of creating an ARB (which is not possible in this scenario); we set an EOT Time for this user (forcing the EOT Time to this time next year).

I investigated the log files submitted by this site owner and found this is exactly what’s happening to them.

So basically the subscription can’t be created because of the card’s expiration date, but the first charge is okay and is processed as a one-time payment.

No problem, Tony.

Okay, it looks like you’re ready to do your tests and have them logged.

By the way, I noticed your s2Member admin menu to be all weird. You may want to try these tips to find what’s causing it, in case it’s causing other problems that aren’t as obvious: Knowledge Base » Common Troubleshooting Tips

If the box is unchecked he won’t be added, if the box is not shown he will (he wasn’t given the option).

[hilite path]Dashboard -› s2Member® -› API / List Servers -› Registration Double Opt-In Box[/hilite]

An email confirmation will NOT be sent to the User, unless the Box is checked, or you’ve disabled the Box; by choosing No.

In other words: The email confirmation will be sent if the box is checked or you disabled the box.

Got it. Thanks for the update.

Not sure if it’s why you’re having this issue, but have you seen this? [hilite path]Dashboard -› s2Member® -› General Options -› Localhost[/hilite]

Here’s what Jason said:

One way to deal with this, is as follows.

– Leave the s2Member® defaults like they are.
– Integrate WordPress® Conditional tags into your bbPress theme.
– Use Custom Capabilities to prevent access where you like.

[hilite pre_code]

Display post form.

[/hilite]

See: Video » s2Member (Custom Capabilities)

Jason tells me that those settings still exist and showed me this screenshot to help you find them:

I hope that helps. :)

Yes, that’ll be the right way to go. Sorry I wasn’t sure how to answer that yesterday. Here’s what Jason said:

Jason Caldwell said:
A shared SSL certificate is one which is NOT tied to a site owner’s domain; it’s tied to a domain associated with the hosting company. It generally requires a site to be accessed from a different (alternative) domain name which belongs to the hosting company. It’s NOT compatible with s2Member, or any other software that I can think of.

It’s really just there as a way to access a set of files over SSL (and so a hosting company can say they provide SSL in their list of features :-). It’s not designed to replace the need for an SSL certificate that would power a domain name. Shared SSL is almost like not having any SSL certificate at all, really. You still need to purchase an SSL certificate.