Bruce

Hi Phil,

Thank-you very much for your patience

In the short term, I would suggest just creating a standard s2Member PayPal button to handle transactions, and wait to figure out what’s wrong with your account before you go live with PayPal Pro.

It sounds like your PayPal account has been mixed up somehow. Once you have some data in your logs please send us the data within them (with sensitive data xxx’d out) so that we can help you further.

—

Based on your previous replies PayPal is not receiving data for credit cards, which is causing the issue. We will take a look at the issue and see what might be causing this.

Try running the Server Check Tool and ensure that there’s nothing wrong with your server configuration that might be causing this. Also, do you have any plugins that could be blocking queries? If you could screenshot your plugins list within your WordPress Dashboard that would do fine.

Hi Frank,

I would just add that page I want to exclude to the No-Cache URI Patterns Box in Quick Cache, correct?

http://www.examplesite.com/members/account-info -> put in /members/account-info in the No-Cache URI Patterns box?

Yes that’s correct. You would most likely want to just put /members/ into the URL Patterns, however, because anything under /members/ shouldn’t be cached.

Also, what if I use s2 conditional short codes throughout some of the logged-in content? Will caching mess that up as well? For example, I use s2 conditional short codes to display certain messages to certain levels of members, while hiding that message from other levels of members.

This also would need to have caching disabled as well, because caching creates a non-dynamic copy of the page to show users, so ALL users would see the same thing.

Hi Frank,

If you have dynamically-created content in pages, such as that sidebar, caching is not possible in those instances because that sidebar would not show up, or may even show up differently than it should.

Perhaps you could create a different template without the sidebar for posts and pages and not cache pages that would have this dynamic content.

Hi,

I just took another look back through your posts and it appears that the problem lies in the fact that you have changed the permalinks on your blog. s2Member is not what’s sending the 404, but your site itself.

Try creating a new page (without changing your permalinks again) that requires s2Member level 1, log out, and try to access the new page. This should cause you to be redirected to the Membership Options Page, or at least redirect to the Membership Options Page’s old permalink, which will result still in 404.

Let us know how that goes.

Hi Frank,

You’ll want to play around with the features a bit, but I would recommend turning caching on for Logged In Users (assuming you don’t have something like a sidebar that shows user data) and turning on Client-Side caching. You will then want to make sure you have stopped caching on your Login Welcome Page, Membership Options Page, and any other page that you are running dynamically-created content.

Hi Lauren,

After doing a bit of digging, I believe that the problem may be that your server’s hosting environment is not allowing loopbacks. Someone else had this issue in this thread:

http://www.s2member.com/forums/topic/paypal-success-return-url-not-working/

Can you try uploading a Must Use plugin with the following data in it (you can do this by putting a .php file within your /wp-content/mu-plugins/ directory on your server, create the directory if you don’t already have it)?:

http://’ . $_SERVER[‘HTTP_HOST’]));
exit;
}
[/hilite]

You should then navigate to http://www.recoverysuperstar.com/?s2_diagnostics and see if it gives you errors.

Hi Lauren,

That’s very interesting. You said that PayPal is sending your users back to the signup page. Are you sure that you have the correct URL set up within your PayPal account? Find info on this in Dashboard -› s2Member® -› PayPal® Options -› PayPal® PDT Integration.

Hi Lauren,

Nothing is jumping out at me as to what might be the cause of this, your Server Check looks fine.

Could you send me a link to the page with the ShortCode on it so I might take a look and see if the the page is passing the success attribute?

Thanks.

Hi Lauren,

Based on your logs, it appears that your shortcode’s success="" attribute is not being passed to PayPal.

Is it possible that a caching plugin on your site is causing this?

If that’s not the case, please try running this Server Check Tool by uploading it to your main WordPress directory within your website, and navigating to the file within your browser. Post results in a reply.

Hi there,

I noticed that you do have a paid account at s2Member, and you are not currently locked out. If you cannot access your account you can reset your password here:

http://www.s2member.com/wp-login.php?action=lostpassword

If you are locked out of your own site, you will need to wait out the ban on your IP and change your settings under Dashboard -› s2Member® -› Restriction Options -› Unique IP Access Restrictions. The default ban period is 1 hour.

If you have changed the ban period to a time period which you are not willing to wait out, I found this article which can help you create a new admin account outside of the WordPress Dashboard so that you can change your settings, and unlock your account:

http://www.dnawebagency.com/how-to-add-an-admin-user-to-the-wordpress-database

Hi Buck,

No, users are not notified of changes to their EOT dates manually. You will need to grab their email address within the Dashboard while you are performing the change and notify them of the change manually.

Hi Quentin,

Thanks for all the information

Just scanning over this, I see the greatest probability for this incompatibility within this code:

function db_query_events_by_user($user_id) {
	global $wpdb;
	$result = $wpdb->get_var($wpdb->prepare('SELECT count(id)
		 FROM ' . $wpdb->prefix . AEC_EVENT_TABLE . '
		 WHERE user_id = %d;', $user_id));
	return $this->return_result($result);
}

I will, however, take a look at the plugin and find out what the incompatibility and either contact the plugin’s creator, or fix the incompatibility within the hack to prevent this from happening in the future.

Thank-you!

Ah, I’m sorry.

I got an error while I was posting one of my last replies. Try just adding:

$my_ccaps= 'wm' . date('Ym') . ',element,forum';
	echo do_shortcode('[s2Member-Pro-PayPal-Form modify="1" level="1" ccaps="'. $my_ccaps . '" desc="Element Creation Tutorial - GOLD" ps="paypal" lc="" cc="USD" dg="0" ns="1" custom="scrapbookcampus.com" ta="0" tp="0" tt="D" ra="15" rp="1" rt="M" rr="1" rrt="" rra="2" accept="paypal" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]');

My suspicion is that this error is being caused by the fact that you have the PHP tags in your code. Try taking them out.