Jason (Lead Developer)

My Latest Replies (From Various Topics)
Author | Replies |
---|---|
Author | Replies |
Posted: Tuesday Aug 13th, 2013 at 11:39 pm #55720 | |
![]() |
|
@ Kevin Cashman
Very welcome Kevin. Thanks for the follow-up :-)
|
|
Posted: Tuesday Aug 13th, 2013 at 11:39 pm #55719 | |
![]() |
|
@ Andrea CilentoThe site we received via Private Contact form was unavailable.
In our last communication with you (see above).
Mike said: http://www.s2member.com/forums/topic/ccbill-postback-not-working/#post-55114 The Dashboard that you sent over did not have logging enabled. Please confirm that your site DOES have logging enabled, and that we can access that site. Once you confirm those details, please submit a new Dashboard login (where we DO have access, and we DO have log files to inspect), and we will review this for you. |
|
Posted: Tuesday Aug 6th, 2013 at 7:18 pm #55330 | |
![]() |
|
Thanks for the heads up on this thread Mike.@TJI just wanted to chime in here & extend a very gracious THANK YOU for this review. That is a very well structured and well written review. We really appreciate it when a customer takes the time do this for us. Please DO let us know if you ever need assistance in the future :-) I’ve asked Mike to bump your account to the Unlimited-Site License as our way of saying thanks! |
|
Posted: Monday Aug 5th, 2013 at 7:35 pm #55250 | |
![]() |
|
Confirmed. You are integrated with PayPal® Express Checkout & PayPal’s DPRP (Direct Pay / Recurring Payments). In short, your PayPal account is not running under the newer Payflow Edition (which is fine). This simply indicates that you’ve had your PayPal account for some time. Everything looks good from our end on this.
If you run another test and this occurs again, please post a screenshot of the error message and record the URL of the page where the error occurred please.
|
|
Posted: Monday Aug 5th, 2013 at 5:01 pm #55239 | |
![]() |
|
We are also investigating further to be sure that you are integrated against the correct API on the PayPal side of things. One moment please.
|
|
Posted: Monday Aug 5th, 2013 at 4:58 pm #55238 | |
![]() |
|
@AnotherOpusI took a quick look at your installation and I find the following issue. Each of the tests against your PayPal® Express Checkout payment option were attempted by the same PayPal account that belongs to the underlying merchant (according to your s2Member® logs). PayPal does not allow a merchant to purchase something from themselves. Please run a test on your site (you being the merchant); but with a PayPal account that is not connected to the merchant account that’s being used on this site. Make sense? Please let us know if problems persist. |
|
Posted: Friday Aug 2nd, 2013 at 6:18 pm #54792 | |
![]() |
|
I’m seeing no errors reported in your s2Member® log files. However, what’s ODD here is that I don’t see any requests coming back from PayPal checkout for your customers. That is, it appears that your site is not responding when a customer returns from checkout at PayPal (e.g. when they choose to use their PayPal account). You should have log entries like this inside paypal-payflow-api.log but you do not have anything like this.
This is not a widespread issue. In fact, I’ve not seen this reported at all recently by our other customers. Therefore, I must assume this is an installation-specific problem. I also no have reason to believe this is caused by PayPal either. My best guess at this point is that you have plugin conflicts on this installation that are interrupting the normal checkout flow in one way or another. Here’s what we’ll need to continue an investigation into this matter.
|
|
Posted: Friday Aug 2nd, 2013 at 5:36 pm #54789 | |
![]() |
|
Thanks for the heads up on this thread :-)~ Investigating now. |
|
Posted: Friday Aug 2nd, 2013 at 6:15 am #54748 | |
![]() |
|
Additional Updates To This Feature in s2Member® v130802
Please see: s2Member® Unified Changelog » v130802 ~ This should resolve the desc="" empty error reported by some site owners.
|
|
Posted: Friday Aug 2nd, 2013 at 1:16 am #54736 | |
![]() |
|
Details received. Thank you!I investigated this installation and find the problem to be the following. This Page is not yet published; it is only scheduled to be published. Thus, a 404 error would occur as it does not exist yet. Also, please understand that a protected post being linked to from another site (if a user is not currently logged into your site) will always result in a redirection to the Membership Options Page, as it should; because the user has no access to this (e.g. the content is protected from public view). |
|
Posted: Thursday Aug 1st, 2013 at 6:59 pm #54677 | |
![]() |
|
Thanks for the heads up on this thread :-)
We’ve had this corrected in the release of s2Member® Pro v130801 (now available).
Please see: s2Member® Unified Changelog » v130801 This was a documentation error only. We’re not aware of any issues with the functionality itself. You should have the following, as Mike mentioned earlier. See below.
Please let us know if you can confirm this is working for you now. Thanks! |
|
Posted: Tuesday Jul 30th, 2013 at 6:03 am #54389 | |
![]() |
|
Thanks for your inquiry. ~ We appreciate your patience :-)It appears this installation of WordPress is running several other plugins and a custom theme. Please put together a test installation that is running a default WordPress® installation. If the problem persists, please report back to us with that Dashboard login and we will investigate further. NOTE: Upon review of your site, I find that all of your s2Member menu pages in the Dashboard are lacking some functionality. This is an indicator that you may have a conflicting plugin and/or a problem with your WordPress® configuration overall. Please put together a test installation running a default WP installation and we will investigate any remaining issues that you may have. For your reference: s2Member® » Support Policy |
|
Posted: Monday Jul 29th, 2013 at 3:59 pm #54352 | |
![]() |
|
You are VERY welcome Randy. That is such a nice review.
I will check w/ the rest of the team and see if we can get this on our testimonials page very soon. ~ Please let us know if you have any other questions. |
|
Posted: Monday Jul 29th, 2013 at 11:51 am #54344 | |
![]() |
|
s2Member® does NOT officially support back-end restrictions, so I can’t give detailed support on this, but Mike’s suggestion is a good one. s2Member® is designed to protect and sell content to Users/Members, and NOT to protect or restrict administrative areas of your Dashboard. At least, not officially. We have site owners that do this with s2Member®, but it requires a good working knowledge of WordPress® and Roles/Capabilities. Please see: Knowledge Base » s2Member® Roles/Capabilities |
|
Posted: Monday Jul 29th, 2013 at 11:47 am #54343 | |
![]() |
|
Yes, please include those tags also. Here is the problem that is showing up in your log files now. |
|
Posted: Monday Jul 29th, 2013 at 12:35 am #54323 | |
![]() |
|
Thank you. The underlying API call error is as follows.
An inspection of your Amazon Console indicates the same error. SolutionPlease signup for Amazon CloudFront service. It appears that your AWS account is not yet subscribed to CloudFront, and therefore it is impossible for s2Member to integrate your WP installation with that service (yet). See also: https://forums.aws.amazon.com/message.jspa?messageID=107972 |
|
Posted: Sunday Jul 28th, 2013 at 11:35 pm #54317 | |
![]() |
|
I suggest that you submit a Dashboard login for s2Member support reps. They can usually find the underlying cause and get right back to you. Please reference this ticket and use: s2Member® » Private Contact Form |
|
Posted: Sunday Jul 28th, 2013 at 11:31 pm #54315 | |
![]() |
|
So the problem you’re having is how to make them Authors, or how to give them unlimited downloads? |
|
Posted: Saturday Jul 27th, 2013 at 4:24 am #54205 | |
![]() |
|
Hi there. Thanks for reporting this important issue.s2Member’s existing AliPay integration was performed against an AliPay account that we no longer have access to. Given the language barrier & the difficultly associated with obtaining access from the US to an AliPay account, we could use some help. We’re going to make every effort to get this updated for you. However, if you are willing to help us by submitting a Dashboard login so we can test this against your installation, that would help tremendously. If one or both of you can setup a test WP installation for us, and submit a Dashboard login privately that would be great! We’ll go to work on this straight away :-)
If possible, please use: s2Member® » Private Contact Form
|
|
Posted: Thursday Jul 25th, 2013 at 10:45 am #54047 | |
![]() |
|
Thank you!
I’m having this fixed in development. This will get pushed out in the next maintenance release.
|
|
Posted: Tuesday Jun 18th, 2013 at 1:05 am #52067 | |
![]() |
|
Thanks for the follow-up :-)There should be another line that comes just below that entry. Can you please post the error message?
That’s just a marker that s2Member injects to indicate it concealed what it found to be a password. |
|
Posted: Monday Jun 17th, 2013 at 5:41 am #52030 | |
![]() |
|
Thanks for the heads up on this thread :-)There are two issues being reported in this thread.
The latest release of s2Member Pro will xxxxxx sensitive information out whenever possible. A password in the log file is NOT what was actually processed; it is what we saved in the log file after concealing sensitive information like passwords (when possible). Some information is NOT concealed, but we make an effort to prevent such things when we can. So this is not an error, it’s to be expected.
This is related to the version of s2Member Pro that was running during each occurrence. Some of the log entries you referenced were running different versions of s2Member Pro. In some previous releases of s2Member Pro, s2Member’s DataLink processor did NOT include &clientSubacc=0000; and this results in ALL sub-accounts being pulled in and processed by s2Member; regardless of sub-account ID. If we don’t send a sub-account ID, ccBill provides data for ALL of them. In the latest release of s2Member Pro, we DO pass &clientSubacc=0000; and this value is set to whatever you configured under s2Member -› ccBill Options. It is always set to that value, regardless of what you put into the Shortcode attribute. We only run DataLink communication for the sub-account that is configured in the Dashboard as the primary sub-account that is being used on the site. If you would like to revert back to pulling ALL data from ALL sub-accounts, please find this section of code. See: /s2member-pro/includes/classes/gateways/ccbill/ccbill-datalink.inc.php at line #79.
Change that to:
and you will have the old behavior back again. In either case, s2Member will ONLY process data it receives from ccBill which matches data it has stored within WordPress® (e.g. it only processes DataLink entries that are associated with transactions/subscriptions locally). Thus, you can have s2Member pull ALL data for all sub-accounts and this will even work across multiple installations of s2Member. So why don’t we have it setup this way by default anymore?The reason is because some ccBill accounts will NOT work properly w/o the &clientSubacc=0000 specification. In some cases we found that ccBill had to be contacted by each site owner to have the ALL sub-accounts functionality enabled. It would appear this has already been enabled on your account, because it was working in the past. |
|
Posted: Friday May 31st, 2013 at 10:24 pm #51102 | |
![]() |
|
Please see this section of our KB article regarding the filter to lock-in your mods.
http://www.s2member.com/kb/roles-caps/#modifying-roles-caps |
|
Posted: Friday May 31st, 2013 at 5:41 am #50996 | |
![]() |
|
Thanks for the follow-ups here.A couple of observations.
I found two instances of this error in your s2-http-api-debug.log file. In both cases the error was handled gracefully; and since the ARB did not event exist to begin with, there was no issue.
To clarify, Subscription ID is invalid If the previous transaction HAD been associated with an ARB (Automated Recurring Billing) profile, it would have been cancelled. Since I’m not seeing any other log entries referencing a cancellation, I’m not seeing a problem. Please let us know if problems continue. Also, please be sure to update the Shortcode attribute that I mentioned because that could result in unexpected issues. |
|
Posted: Wednesday May 22nd, 2013 at 9:28 pm #50404 | |
![]() |
|
This sounds like it could be an issue with the service provider (as you mentioned). It sounds like the ISP is blocking videos; or perhaps blocking the RTMP protocol. I would ask the ISP to confirm the following.
Anyway, something along those lines. Some ISPs may choose to prohibit streaming media content because they are incapable of dealing with the high bandwidth normally associated with such things. Not common these days, but possible I suppose. Also, I would check to see if any of these users are capable of downloading the audio/video content through a direct link to the MP4 file (for example). In other words, instead of playing it through JW Player; can they download the file with a direct link via Cloudfront? If you get nothing back from the ISP, I would suggest contacting Amazon about this too. Perhaps there is a legal issue in a certain country that is preventing them from serving content through this ISP? |