|
|
|
|
|
|
Thanks for your inquiry.
Please post a screenshot of your current EOT settings/configuration so we have some idea about what’s going on with your installation. Also, these are declines you said; are they failed recurring payments, or initial Buy Now transaction declines?
What version of s2Member® Pro are you currently running?
Is your Authorize.Net account connected to a US or Canadian bank?
Do you have s2Member’s logging routines enabled?
Please see: Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details -› Logging
|
|
|
@ Andrew Lock
Thanks for your submission. However, before reporting a bug in the software, please try to reproduce the issue that you’re having in a clean/default installation of WordPress® with only the s2Member® plugin active and running a default WP theme. If you can reproduce the issue there, and we can reproduce it on our end, or in that default installation on your server, we can forward the details to one of our techs for investigation.
When issues like this arise, we find that it is often associated with plugin conflicts and/or configuration. If you setup a clean/test installation of WordPress® when problems like this come up, it almost always helps find the underlying cause.
When you post a new Dashboard login that is running a clean/default installation with this problem, I will be sure that we have a tech investigate this for you ASAP.
|
|
|
Great! Thank you. We would REALLY appreciate that :-)
Please register @ WordPress.org and rate s2Member® 
NOTE: If you vote @ WordPress.org & LIKE us on Facebook, please reply back in the s2Member® Forums with a link to your nice comments (just to let us know). The company also has a way of saying thanks for this :-)
|
|
|
You should have gotten an email receipt and invoice. I’m forwarding this to accounting and you should expect a reply within 24 hours from Elizabeth in that dept. You may also want to inspect spam folders in case it went there by mistake. Sorry for the inconvenience.
|
|
|
This error was reported by a couple of other site owners after the initial release of s2Member v130731 and v130801. It was corrected a day later in the release of s2Member® v130802.
What version are you running please?
See also: s2Member® Unified Changelog » v130802
|
|
|
If you want a charge amount to show up on the PayPal® checkout form you will need to use Buy Now functionality in your s2Member® PayPal Pro Form instead of recurring billing.
Your current Pro Form is configured to charge on a recurring basis, and that’s why there is no specific amount listed on the PayPal side of things. The amount is displayed on your site (based on the desc="" attribute in your shortcode); and this is shown to the customer before they ever get to PayPal.
To clarify, with PayPal Express Checkout and recurring billing, the PP interface will not display a specific amount, because the Express Checkout routine is really just establishing a billing agreement between you and the buyer. The amount that you’re charging in a case like this, should be displayed to the customer before you send them to PayPal. Normally this is accomplished in the desc="" attribute of your Pro Form Shortcode.
See also: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained)
|
|
|
Closing this thread. I’m sorry, but this is related to general WordPress® support and not specifically to s2Member®. Please see: s2Member® » Support Policy. If you find this IS related specifically to s2Member®, please feel free to post a new request for support under a topic pertaining to a specific feature or functionality in the s2Member® plugin.
|
|
|
|
|
|
|
|
|
|
|
s2Member® stores this inside a user option value in the DB (s2member_subscr_gateway).
So you can do something like this in PHP code. Not sure how you might choose to integrate this with Simple Shortcodes, but hopefully this will send you in the right direction.
<?php
if(get_user_option('s2member_subscr_gateway') === 'paypal')
// do something for PayPal.
else if(get_user_option('s2member_subscr_gateway') === 'authnet')
// do something for Authorize.Net.
?>
|
|
|
A quick look at this site in the Chrome developer console reveals there are some JavaScript errors with plugins running on this site. Please test against a clean installation of WordPress before reporting bugs. Clean meaning, no other plugins except s2Member, and running a default WP theme. You are running a default WP theme, but there are several plugins running in concert with s2Member on this installation, making it very difficult to know exactly what the underlying of this is.
If you deactivate all other plugins except s2Member, does the problem still occur?
If so, please report back and we’ll have a tech assist you with this.
|
|
|
|
|
|
|
I recommend that you block this visitor to prevent unwanted interaction with them in any way. You can accomplish this with the .htaccess file in your WordPress directory.
Add these lines to the top of the file, where 1.2.3.4.5 should be replaced with the IP you want to block (and you can add a new line like this for each IP you want to block from the site in the future).
order allow,deny
deny from 1.2.3.4.5
allow from all
See also: http://wordpress.org/support/topic/block-ips-with-htaccess
|
|
|
Please see: Dashboard -› s2Member® -› Download Options -› Inline File Extensions
|
|
|
But the scenario I want is:
See teaser with buy-now button – click buy-now button – redirect to that specific post = read full post.
A teaser is possible through WordPress® excerpts. Most WordPress® themes will provide an excerpt of the content in one form or another. If your theme does not, you can always customize a template and use the_excerpt() template tag to get this information. See: http://codex.wordpress.org/Function_Reference/the_excerpt
You may also want to look over this KB article that discusses Simple Shortcode Conditionals, which allows you to protect parts of your content. These cannot be used with Specific Post/Page Access, only with Membership Level Access. However, there is more than one way to sell access to a Post/Page. Specific Post/Page Access is one way (more limited, because there is no user account associated with the purchase); whereas a Member (e.g. a User) will make things a bit easier to deal with all the way around.
Please see: Knowledge Base » s2Member® Roles/Capabilities
See also: Knowledge Base » Simple Shortcode Conditionals
See also: Dashboard -› s2Member® -› Restriction Options -› Post Access Restrictions
See also: Dashboard -› s2Member® -› Restriction Options -› Page Access Restrictions
See also: s2Member® » Video Tutorials
|
|
|
I would check the configuration of these Registration/Profile fields in s2Member® and be sure that you have this option is configured to something that applies at the appropriate Membership Level, and also at the appropriate visibility setting.
Also, in BuddyPress (under Users -› Profile Fields), be sure that you have a Base Group that s2Member® can integrate with. Normally there is a Base Profile Fields group which should contain just the Name field in BuddyPress. You’ll want to leave that Base Group, so that s2Member® can integrate everything into that default “Base”.
|
|
|
Thanks for the heads up on this thread :-)
Often times when something works on a test site, but not on the live site; the underlying problem is with server compatibility. What hosting company is being used in this case? Also, does this server use ModSecurity? Does anything show up in server error logs that may provide some insight?
See also: Knowledge Base » Mod Security, Random 503/403 Errors
If all else fails, please submit a clean/test installation of WordPress® privately, where you have reproduced this problem on your server. If our techs have a Dashboard where they can log in and reproduce the issue, that is about 90% of the way to getting the problem resolved quickly :-)
Please use: s2Member® » Private Contact Form
|
|
|
I can also confirm this works as expected (and as shown in Jason’s video). The only thing is, you must have the BuddyPress integration checked off in this section of your Dashboard. Please see: Dashboard -› s2Member® -› General Options -› Registration/Profile Fields
See also: Knowledge Base » BuddyPress™ + s2Member® Pro (Video)
|
|
|
Actually, I might be wrong. I don’t think referenced payments are defaulting back to PayPal… There is no $$ amount on the PayPal page and the description just says “future payment” rather than the description in the form.
This is normal for a Reference Transaction via Express Checkout. PayPal simply states “Future Payment” because it’s simply an agreement between you and the buyer. This could use some improvement on the PayPal side, I agree. However, it’s not abnormal. What you’re seeing there is the standard they follow.
|
|
|
It is not unheard of that PayPal (or certain portions of the PayPal service) are not available to certain merchants outside the USA. If PayPal specifically tells you it’s OK to remove Express Checkout from your Pro Form, then I would keep a copy of that communication with them for your own reference, and then proceed to remove that option from your Pro Form. I don’t see anything wrong with this, particularly in a scenario where the service is not working as expected due to a PayPal limitation.
The only remaining issue is that s2Member® Pro Forms will try to follow PayPal® policy by not allowing a site owner to remove PayPal® Express Checkout easily. However, it CAN still be done. Here is one way to accomplish this with s2Member® Pro Forms.
The following can be used to disable PayPal as the default payment option in this case.
Please create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
(NOTE: these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins)
(See also: http://www.s2member.com/kb/hacking-s2member/)
<?php
add_filter('ws_plugin__s2member_pro_sc_paypal_form', 's2_pro_paypal_form_code');
function s2_pro_paypal_form_code($code)
{
$code = str_replace('s2member-pro-paypal-checkout-form-card-type-paypal-label', 's2member-pro-paypal-checkout-form-card-type-paypal-label disabled', $code);
$code = str_replace('id="s2member-pro-paypal-checkout-card-type-paypal"', 'id="s2member-pro-paypal-checkout-card-type-paypal" disabled="disabled"', $code);
if(empty($_POST)) // Select default payment method (e.g. Card Type option).
$code = str_replace('id="s2member-pro-paypal-checkout-card-type-visa"', 'id="s2member-pro-paypal-checkout-card-type-visa" checked="checked"', $code);
return $code;
}
|
|
|
I can currently still access wp-login.php however.
The hack I posted earlier will only redirect away from /wp-login.php?action=register. You won’t want to block access to /wp-login.php entirely, because that’s how you gain access to the Dashboard.
1. the /register page is currently the buddypress and themes custom page which currently populates strangely and shows both ‘profile fields’ and s2′s profile fields, would need to be the paypal pro form. So I suppose i’m after complete turning off registration through buddypress? to free up this page for the pro form?
2. I need to understand where and how I would create all the profile fields for the users to show in their edit profile section, and understand how I would select a which ones are to show up in the pro form… which then auto updates their profile.
Please watch this video tutorial on BuddyPress + s2Member® Pro; and read over the KB article.
I asked Jason to create a tutorial for this and he published it this morning. Pretty nice of him! :-)
|
|
|
@ Kevin
Please be sure to run tests after you log out of the site (e.g. as a customer) and not as the site Administrator. The tech investigating this for you, informed me of this excerpt in your most recent log entry. In other words, your most recent test transaction was performed while you were still logged in, and you were logged in as a WordPress® Administrator also.
array (
0 => 'IPN received on: Sat Aug 10, 2013 6:53:13 pm UTC',
1 => 's2Member POST vars verified with a Proxy Key',
2 => 's2Member originating domain ( `$_SERVER["HTTP_HOST"]` ) validated.',
3 => 's2Member `txn_type` identified as ( `web_accept|subscr_signup` ).',
4 => 's2Member `txn_type` identified as ( `web_accept|subscr_signup` ) w/ update vars.',
5 => 'Unable to modify Subscription. The existing User ID is associated with an Administrator. Stopping here. Otherwise, an Administrator could lose access.',
|
|
|
Thanks for the follow-up.
Our techs looked at your installation and while they WERE able to reproduce this on your site, there’s been no indication that’s it’s actually a bug in the s2Member® software application. The working theory is that it’s a plugin conflict, or a server compatibility issue.
What we’ll need to do next is see this on a clean/test installation of WordPress® (on the same server); with only the s2Member® plugin active and running a default WP theme. If you/we can reproduce it there, it should give us everything we need to find the underlying cause.
It may also be worth your time to write your hosting company about this. It’s possible there is some security mechanism on the site that none of us are aware of, and they could help shed light on why this problem is occurring for you. It’s definitely not a widespread issue, it is likely server-specific, or installation-specific.
The clean/test installation may help reveal a potential conflict between two or more plugins that you’re currently running on the live site. This is often the case when mysterious issues like this arise.
|
|
|
Response from ccBill Tech Support.
Thank you for contacting the CCBill Merchant Support Department. My name is Erik, and I will be assisting you today.
I understand that you are concerned with some empty variables when receiving transaction data from the Background Post system. The responseDigest variable will only be populated with a string value when the purchase attempt is processed through the Dynamic Pricing system. The responseDigest variable is for validation purposes when the Dynamic Pricing system is used to call the payment form. If the responseDigest variable is returned as an empty value it means that the standard pricing system was used when calling the payment form.
|
Pre-Sale FAQs
Video Tutorials
Community Forum
Knowledge Base
News/Updates
s2 Codex / Docs
GPL v2 License
Contact A Human
About Us
Our Customers
Support Policy
Privacy Policy
Old Forums (READ-ONLY): The 
