Bruce

My Latest Replies (From Various Topics)
Author | Replies |
---|---|
Author | Replies |
Posted: Thursday Jul 11th, 2013 at 9:13 am #53287 | |
![]() |
|
Thank you for your inquiry.
Not that I’m aware of. I will ask our development team about this. I’m fairly certain that s2Member does not support PayPal Pro Hosted, though. |
|
Posted: Thursday Jul 11th, 2013 at 9:12 am #53286 | |
![]() |
|
Thank you for your inquiry.Sorry about the delay. First off, the way that you’d begin working on this is to check out the article on Variables in a Shortcode: Knowledge Base » Using Variables In A Shortcode You’ll need to check the current date for the month. This PHP function can help you do that: http://php.net/manual/en/function.date.php To get a numeric representation of the month, you’d use this:
|
|
Posted: Thursday Jul 11th, 2013 at 8:58 am #53285 | |
![]() |
|
Thanks so much. I’m sorry about the delay. I had to go ahead and download all of your logs to take a look, and as I was going through them I realized there is something really weird going on with your PayPal PayFlow integration… If you’ll look at your paypal-payflow-ipg.log file, the first thing that strikes me as off is the URL that your IPN requests are coming in on:
I had missed this yesterday, and I’m sorry about this. This is not your PayPal PayFlow IPN URL. This is a WP_Cron URL and it is an automated request. The second thing I noticed (which I did not notice until now because there are so many requests in this file), is that there are a lot of repeating requests. According to the description for your transactions, you are supposed to be charging Users $10.00 a month, but I’m seeing IPN resposnes for the same transactions 10-15 times in the logs, all within a couple days of each other. This looks like (to me) not a problem with your IPN setup, but with an external plugin doing weird stuff with the incoming requests from PayPal. I’m unable to log into the Dashboard so I can’t tell all of the plugins that you have activated, but I can tell via FTP that you do have several installed. I have to recommend turning off all plugins you can and doing some test transactions. As-is, I doubt any transaction will go through correctly, looking at your logs. I’m not seeing any logged successes in your most recent log files. The earliest I’m seeing log file that look like they are correct is the end of March. |
|
Posted: Wednesday Jul 10th, 2013 at 4:59 pm #53253 | |
![]() |
|
Which email configuration field is this? |
|
Posted: Wednesday Jul 10th, 2013 at 4:56 pm #53252 | |
![]() |
|
If you look through your logs, you should see that s2Member does receive a notice from PayPal that there was a failed payment, and does not do anything with the information but log it. During this time, the subscription is momentarily put into that Suspended status. When the number of failed payments reaches the maximum number (the RRA attribute), PayPal instead sends s2Member data to cancel the User. At least that’s how it works from s2Member’s standpoint. I’m not 100% sure on the information that PayPal actually gives you at PayPal.com, but that’s the gist of what’s happening. As far as what’s causing the failures, if it’s just a few random Users then it’s probably because of insufficient funds, or a problem with their PayPal account / card. If it’s happening on every User, then it might have something to do with something you have set up at PayPal. It’s unlikely that anything you set up at PayPal would cause sporadic failed payments. |
|
Posted: Wednesday Jul 10th, 2013 at 4:41 pm #53250 | |
![]() |
|
This has to do with the settings in your PayPal Options, as well as the RRA attribute:
By default, s2Member will keep things as streamlined as possible by allowing the User to register before the transaction is completed, because there is a chance that the payment will simply fail the first time, and then go through on the second try. However if the payment does fail for sure, then this does cause a problem because until PayPal registers that the User is unable to make the payment (meaning that the number of attempted payments reaches the RRA amount), the User has access. So if you’re having problems with this, change your Recurring Profile Behavior to Real-Time, and for additional security you can make failed payments at any time cause a cancellation by setting your RRA attribute to 0. Does that all make sense? |
|
Posted: Wednesday Jul 10th, 2013 at 3:45 pm #53245 | |
![]() |
|
s2Member makes working with Custom Capabilities as simple as possible. You can restrict access to a Post or Page with the same meta field in the Add/Edit Post Screen as if you were restricting access with a level:
To give access to a Custom Capability, you can either sell access to it on a One-Time basis (Buy Now) With capability Buy Now Forms, or you can use the extra field provided in the subscription forms for levels:
So no, it does not require any custom code to get started. However, when you start using Custom Capabilities you’ll notice that s2Member cannot restrict things quite as freely as it can with Membership Levels. As long as you’re just protecting select Posts/Pages or specific pieces of content then you’re fine. However, if you wanted to restrict access to a whole Category with Custom Capabilities, that’s not possible without custom code, due to their nature. Does that make sense? |
|
Posted: Wednesday Jul 10th, 2013 at 3:38 pm #53244 | |
![]() |
|
The function should be available anytime after ws_plugin__s2member_loaded. It sounds like you’re trying to use it as your plugin is being loaded, which won’t work. Hook onto the plugins_loaded hook. That should work. See: http://codex.wordpress.org/Function_Reference/add_action |
|
Posted: Wednesday Jul 10th, 2013 at 9:51 am #53237 | |
![]() |
|
Thank you for your inquiry.You’d just need to make sure the User has s2Member installed and that you’re loading the plugin with WordPress when you use it. |
|
Posted: Wednesday Jul 10th, 2013 at 9:29 am #53235 | |
![]() |
|
Thank you for your inquiry.
The integration plans for Bitcoin are not for the immediate release of the next major version of s2Member, so we have not actually decided on the provider for that integration. I would say that BitPay is probably the most likely choice for the integration, but I can’t tell you for sure. Sorry about that. |
|
Posted: Wednesday Jul 10th, 2013 at 9:20 am #53234 | |
![]() |
|
Okay cool. If the problem comes back after you’ve done that then let me know and I’ll take a look. :-) |
|
Posted: Wednesday Jul 10th, 2013 at 9:18 am #53233 | |
![]() |
|
That’s because of the login URL that you have set up at the top of your site. If you’ll look, it has an additional redirect_to variable set to send the User back to the homepage:
I can’t log in with the details you provided. I even tried using the FTP details at /wp-login.php, but it does not work for me. That’s okay though because I have FTP access. Right now I need a Subscription ID for a transaction this happened with. |
|
Posted: Wednesday Jul 10th, 2013 at 9:15 am #53232 | |
![]() |
|
That’s here: http://www.s2member.com/forums/topic/member-custom-field-exportimport/
Oh I see what you’re saying now. s2Member actually recently was updated to support this better. The new format is gone over in this KB article: Knowledge Base » Import (or Mass Update) Users We now have Custom Fields split into columns, which makes the answer in that thread incorrect now. This was changed in s2Member Pro version 130203. Here’s the changelog for that: |
|
Posted: Wednesday Jul 10th, 2013 at 9:02 am #53230 | |
![]() |
|
I got in via FTP. I’m looking at your logs and there are a lot here and I can’t be sure I’m looking at the correct transactions that went wrong. Do you have a specific Subscription ID that this happened with? |
|
Posted: Wednesday Jul 10th, 2013 at 8:57 am #53227 | |
![]() |
|
I’m getting an error trying to use the credentials you gave me for Dashboard Access. Is there something I’m missing? |
|
Posted: Wednesday Jul 10th, 2013 at 8:55 am #53226 | |
![]() |
|
Got it. I’m taking a look now. |
|
Posted: Wednesday Jul 10th, 2013 at 8:43 am #53224 | |
![]() |
|
Thank you for reporting this important issue.Does deactivating s2Member stop this from happening? I’ve never heard of anything like this happening before. s2Member does not deal with the visual editor in any way that I know of. Could you provide us with a Dashboard login so we can take a look? You can do that here: |
|
Posted: Wednesday Jul 10th, 2013 at 8:41 am #53223 | |
![]() |
|
I’m not sure if it’s possible to have PayPal record this value, but if you absolutely need this value then you might consider having a developer set up a hook on s2Member’s IPN processor to save the User’s address so you can track that on your site. I’m afraid I have no idea how you’d retrieve that data from your Users that have already signed up, though. Sorry. |
|
Posted: Wednesday Jul 10th, 2013 at 8:33 am #53222 | |
![]() |
|
Thank you for reporting this important issue.I’m very sorry for the delay in response. It sounds to me like you’re getting skipped payments and your RRA attribute is set to 2, so your Users are getting access until their payment fails twice. The quick fix here is to set your RRA attribute to 0, to prevent failed payments from being allowed in the future. |
|
Posted: Wednesday Jul 10th, 2013 at 8:31 am #53221 | |
![]() |
|
Got it. I’m seeing that the IPN processor is receiving data, but there isn’t enough data here for me to tell what’s going on. I see you did a test transaction, but you were still logged in as an administrator when you completed it:
Also, I’m seeing two different custom values. I’m not sure if that’s right but for now could you run another test transaction, creating a new User? Make sure that you log out of your account before you do that. Then send us your new log file? Thanks! |
|
Posted: Wednesday Jul 10th, 2013 at 8:26 am #53220 | |
![]() |
|
No, s2Member first gets the information from PayPal, and then redirects to the URL specified. That’s the different between just changing the PDT URL and using the success attribute is that the User is originally sent back to s2Member’s return URL, and then redirected to your URL after their transaction is processed.
With errors like this, s2Member doesn’t ever receive any information for the transaction, from what I understand. The User is stopped before the transaction is completed. With s2Member’s Pro Forms, the User is given an error back from the Pro Form because PayPal rejects the transaction, but with Buttons s2Member doesn’t ever get involved in the transaction’s data, because it never completes, so there’s no way to send the User to a URL that’s different, because they are still at PayPal when the error occurs. Does that make sense? |
|
Posted: Wednesday Jul 10th, 2013 at 8:18 am #53218 | |
![]() |
|
Thank you for your inquiry.I suppose you’d try something like this:
Here’s a thread where something similar was being done: http://www.s2member.com/forums/topic/registration-wont-update-mailchimp-merge-tags/ |
|
Posted: Wednesday Jul 10th, 2013 at 8:11 am #53217 | |
![]() |
|
Thank you for your inquiry.
I’m sorry for that. We’re addressing this in the rewrite of s2Member we’re planning to release sometime soon, but we’re not figuring on doing that in the current release of s2Member. The issue does not actually affect the functionality of s2Member, but it does display those errors with WP_DEBUG set to TRUE. You’ll have to turn WP_DEBUG off to run s2Member. |
|
Posted: Wednesday Jul 10th, 2013 at 8:08 am #53216 | |
![]() |
|
The best way would be to just give us Dashboard access via Private Contact Form. We’re going to be taking a look at the paypal-ipn.log file. |
|
Posted: Wednesday Jul 10th, 2013 at 8:06 am #53214 | |
![]() |
|
Thank you for your inquiry.
You’d do that by setting a trial amount of $15, and a recurring amount of $10 when you set up your Pro Form. See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained) -› ta |