|
|
Interesting idea
-
This reply was modified 4 years, 3 months ago by
 Mark R..
|
|
|
Jason –
Here’s a conversion between a BeyondPod developer and a devoted/talented member – it sheds some good light on what is going on behind the scenes.
http://www.beyondpod.com/forum/showthread.php?580-Young-Turks-Issue&p=1809&viewfull=1#post1809
This might leave S2M out of it completely – although the question still remains that others must be having the same issues – since anyone using S2M and S3 to secure podcasts will have the same results with all Android users. Do you have any comments/input on this issue? Is there by chance anything that can be done from the S2M side that might help resolve this issue? It’s worth at least asking. :)
|
|
|
Hi Jason –
Yes – indeed it will work from within an Android browser – just not any Android App (like DoggCatcher). The one exception is that BeyondPod was able to figure out a workaround. However, going to each and every podcast software developer and get them to add the same workaround is not a good solution.
We can’t just exclude Android users. And we can’t be the only one using HTTP Auth and have Android users. Have you run into this before? Has anyone got S2M + S3 CloudFront to work with Android users?
Thanks much for your time!
|
|
|
It does – and you’re right… PayPal’s naming scheme is horrible. I still don’t know for sure which one is actually working – but the fact remains it does work. So I’m not going to touch anything. :) Thanks again for your help!
|
|
|
Jason,
As you predicted – PayPal did have something messed up on their side. They corrected it, and at the same time, I did remove the settings that the above video said to set. It does appear to work (no errors on the client side), but then again – I don’t see the charge on the PayPal side either.
It doesn’t help anyone that PayPal keeps changing their nomenclature and product names. The S2M demo video doesn’t seem to apply at all anymore and should probably either be taken down or updated).
We’ll keep testing – thanks for your continued help!
|
|
|
An add on note:
It seems from your recommendations above that in s2M we should only use PayPal Pro or PayPal PayFlow–but not both.
Is that accurate?
|
|
|
Jason and Cristián,
Thank you for the support and responses.
We’re actively working with you and PayPal (at a DefCon 5 level) because we’re loosing members and the goodwill we’ve worked so hard to earn and keep with our membership.
From the above suggestions. “…removing all of your Payflow configuration options from the s2Member Dashboard panel, in hopes that your current PayPal Pro account will work without it,” and “…regardless of which API s2Member is working with, Recurring Billing service must be enabled,” it sounds like we should chose only one option in s2M. It seems we should chose either PayPal Pro, or PayFlow–but not both. Is this true?
If we gave 2sM admin access to our PayPal account, then s2M would be the one party with full access to all three sides of this issue (Our WP, S2M, and PayPal). If s2M could work in a “PayPal partnership” arrangement then s2M would be able to offer a higher level service agreement to its customers–and with a backstage pass to PayPal, s2M would be able to see all the settings and line them up so everything would work–every time.
This full access could enable s2M to further develop the s2M app so the app could use our PayPal credentials, log into PayPal on the app side, and coordinate s2M and PayPal settings. Then s2M would become a “one click” app by us and all other s2M/PayPal users. That one seems fairly obvious–but at the same time I fully understand implementing it would not be easy.
An app that could do that would/could/should eliminate the payment problems we’re experiencing now. And if that app gave s2M customers a high level service agreement option, the app could be called the s2Member Edge because it would give s2M a huge edge over all other competitors with WordPress:PayPal transaction management.
Another fitting name for this advanced app would be s2Member Utopia :)
Sincerely,
Pollyanna
|
|
|
Here are the results from the last test (all PASSed].
While we do feel like we set up PayFlow correctly (remember – it works 60% of the time), I’ll be happy to review it one more time. Since the last time this error came up on the forum, a fix that you supplied seem to work for the majority of them. We were thinking that might be the case here…
We’ll send the log files as well.
|
|
|
Here’s the screenshot.
Here it is in plain text:
Congratulations, you have PHP v5.3.2-1ubuntu4.14 installed!
Your server IS fully compatible with s2Member® Pro.
— Good to go! ( visit s2Member.com )
You said it was several pages… but that’s all that it displayed.
-
This reply was modified 4 years, 4 months ago by Mark R..
|
|
|
Thank you for the fast response Eduan,
I went through three log files. The data is sensitive so I can’t post all of the content here.
The three logs (from …/wp-content/plugins/s2member-logs) were:
- paypal-ipn.log
- paypal-payflow-api.log
- paypal-payflow-ipn.log
Log file: paypal-payflow-ipn.log
No errors
Log file: paypal-payflow-api.log
145 approvals and 75 transaction failures [note: “DAMN”!]
62 of these failed transactions had this in common:
Transaction failed: Fail to obtain approval for the online transaction
Referral: 10422-The customer must return to PayPal to select new funding sources.
I didn’t see a common thread with the 145 successful transactions.
Log file: paypal-ipn.log
ERROR: PHP v5.2.17 :: WordPress® v3.4.1 :: s2Member® v120703 :: s2Member® Pro v120703
http://www.domain.com/?s2member_paypal_notify=1&s2member_paypal_proxy=paypal&s2member_paypal_proxy_use=pro-emails,subscr-signup-as-subscr-payment&s2member_paypal_proxy_verification=xxxxxxxx&s2member_paypal_proxy_return_url=
User-Agent: WordPress/3.4.1; http://www.domain.com
0 => ‘Unable to verify $_POST vars. This is most likely related to an invalid configuration of s2Member, or a problem with server compatibility.’,
1 => ‘If you\’re absolutely SURE that your configuration is valid, you may want to run some tests on your server, just to be sure $_POST variables are populated, and that your server is able to connect/communicate with your Payment Gateway over an HTTPS connection.’,
3 => ‘Please see this thread: `http://www.s2member.com/forums/topic/ideal-server-configuration-for-s2member/` for details regarding the ideal server configuration for s2Member.’,
4 => ‘array (
\’payer_email\’ => \’syntaxterror7@gmail.com\’, < <<<<<<<[Chris]< This may also be a problem with one of the failed 62 transactions.
So if we’ve got “…an invalid configuration of s2Member, or a problem with server compatibility,” it’s inconsistent with about a 40% failure rate.
|
|
|
Cristián,
Thank you for enlightening me about server side object caching.
Yes, we were testing caching plugins when our site was slow–we didn’t know that the host was throttling our site. The site was just crawling on the front end and on the back in. Typical page loads front and back were running 40 seconds!
So I got the GTMetrix plugin, and also ran the site URL through every site analysis tool I could find on the internet.
I aggregated their advice and took care of the highest priority items first–one of the biggies was caching.
So we ran through a fist full of caching plugins, one at a time and then some together, because they addressed different issues. So we probably caused the object caching during this phase of our crisis.
The sad thing is that our site was a bit heavy but not horribly bad, normally loading in 8 seconds. But several of us lost a lot of time and we lost some member goodwill, trust and interest because Bluehost throttled our CPU down. We didn’t know this so all our work was essentially useless.
We’re in much better hands now with WPEngine. They manage caching for our WordPress site–so it’s like lightening now.
BTW I mis-typed earlier, “UE and EU” should have been “US and EU.”
|
|
|
Hello,
First, the behavior stopped. And yes, it should never have happened. IT was a registered user’s info and data. And of course it’s not a feature we want.
To clarify the behavior, our membership site has s2Member Pro and a few thousand members.
Randomly, the Upgrade Membership page (a WordPress page with the Upgrade Membership shortcode), began displaying one member’s information. We visited the page from different computers, different geographic regions (UE and EU), and with five different browsers (Chrome, MSIE, Safari, Firefox and Opera). At the time I posted the original message, all of us from our different computers, browsers and parts of the world, could see this same user’s info in the Upgrade Membership page. We were all Admins and the user was a free subscriber.
So if it was a caching issue–how did the member’s info appear in a page for all of use?
And if WP was caching the info–how did it get into the s2M shortcode fields in that page?
We have since ran into other issues with the hosting company so we relocated to a more robust host. And this issue is no longer an issue–but it would be real good to understand how all the world could go to our Upgrade Membership page and read private info about a registered member.
BTW We left the host because when our site got heavy traffic they throttled the CPU and choked our site during the time when we needed bandwidth and CPU the most. I won’t mention their names but their initials are Bluehost and Bluehost CPU throttling killed our site. Bluehost could have made money by charging us to upgrade our CPU rather than automatically choking it–but they’re not a problem for us any longer.
So this issue is gone–but we wonder how it happened and why WP and the s2M shortcode was displaying the private member data. That’s a very undesirable behavior.
|
|
|
Thank you Cristián, I’ll read the article and see if we can find out how to work around the mod rewrites. We don’t know where the mod rewrites come in–if it is s2M (we looked into the Remote Auth settings under File Download Options). We don’t know what app is creating the mod rewrites, but we need to work without them.
|
|
|
Eduan,
You are right. We suspected that this would only happen with logged in users.
That is why we are asking about this for non-logged in users:
Anybody from any computer and any browser can visit our upgrade page and the same user data appears:
1. First Name
2. Last Name
3. Email Address
4. User Name
Please help us!
|
|
|
Thank you Raam.
We’ll look into it and see what we need to change from your suggestions.
|
|
|
Our site is protected by s2Member Pro.
Our feeds begin as posts and podcasts with multimedia files protected by s2Member (L2 and L3).
PowerPress adds the posts to our feed.
When anyone uses a feed reader or iTunes to view the feed it requires the s2M L2 or L3 authentication to view the podcasts.
In browsers, unauthenticated feed readers are redirected to our Membership options page when they click a link in the feed.
Here is a sample link from the feed:
http://www.domain.com/wp-content/plugins/s2member-files/s2member-file-remote/s2member-file-inline/Sports-YYYYMMDD.mp3
|
|
|
Two with one stone – nice job.
|
|
|
Thanks Jason –
That does make sense. I did both – changed to non-safe mode, as well as upgrade.
Of course, the site you tweaked and got working was the temp site – without any content. I copied back the basic code (not much really – plain install with s2Member plugin and some content and theme), and I got this error when updating to CloudFront:
Unable to auto-configure Amazon® CloudFront Distributions.
Error code: 409. Error Message: Unable to create Amazon® CloudFront Downloads Distro. Unable to create Amazon® CloudFront Downloads Distro. Conflict
At least it’s a DIFFERENT error – perhaps this one is easier to troubleshoot.
** UDPATE **
Well that was easy – it was obviously a conflict since those CF settings we already manually set up. Once I deleted those, it created them again perfectly with the correct settings. WONDERFUL.
THANKS JASON!
-
This reply was modified 4 years, 10 months ago by Mark R..
|
|
|
Hi Jason,
Great (at least from a troubleshooting standpoint). I’ll set up the FTP account and submit now.
Bendix – we’re in the States, so I’m not sure what is going on. Perhaps when we get to the bottom of it we can help you as well.
|
|
|
Nope. new install – new database. Same exact issue. I added the S3 bucket no problem – but the CloudFront fails with the same exact error on a new install/new database. Now what?
Also, we’re running the most recent version as this is a brand new install (and we’ve never used the system before).
I’ll supply the admin U/N P/W on the form.
-
This reply was modified 4 years, 10 months ago by Mark R..
-
This reply was modified 4 years, 10 months ago by Mark R..
|
|
|
Hi Jason!
OK – backed up WP, installed new clean install, but I left the database intact. That might have been a mistake though, as after I installed S2member again as the only plugin using the generic theme, I got the same exact error:
Unable to auto-configure Amazon® CloudFront Distributions.
Error code: 400. Error Message: Unable to create Amazon® CloudFront Origin Access Identity. Unable to create Amazon® CloudFront Origin Access Identity. Bad Request
I can try it again, this time with a new database.
|
|
|
Sure thing. Here is the code from the player page:
<a href="[s2File download="video.mp4" /]">Download Now</a>
<div id="jw-container">JW Player® appears here.</div>
<script type="text/javascript" src="/jwplayer/jwplayer.js"></script>
<?php
/* A direct URL to the CloudFront RTMP source; counting the file against the current User in real-time. */
$mp4_via_cf_cfg = array ("file_storage" => "cf", "file_download" => "video.mp4", "url_to_storage_source" => true, "count_against_user" => true);
/* A direct URL to the Amazon S3 source; NOT counting this variation against the current User. */
$mp4_via_s3_cfg = array ("file_storage" => "s3", "file_download" => "video.mp4", "url_to_storage_source" => true);
/* API Function `s2member_file_download_url()` returns false if access is denied to the current User. */
if (($mp4_via_cf = s2member_file_download_url ($mp4_via_cf_cfg, "get-streamer-array")) && ($mp4_via_s3["url"] = s2member_file_download_url ($mp4_via_s3_cfg))) {
?>
<script type="text/javascript">
jwplayer("jw-container").setup({modes: /* JW Player®. */
[
/* First try real-time streaming with Flash® player. */
{type: "flash", provider: "rtmp", src: "/jwplayer/player.swf",
config: {streamer: "<?php echo $mp4_via_cf["streamer"]; ?>", file: "<?php echo $mp4_via_cf["file"]; ?>"}},
/* Else, try an HTML5 video tag with the `mp4` file. */
{type: "html5", provider: "video",
config: {file: "<?php echo $mp4_via_s3["url"]; ?>"}},
/* Else, this is a safe fallback. */
{type: "download", /* Download the file. */
config: {file: "<?php echo $mp4_via_s3["url"]; ?>"}}
],
/* Set video dimensions. */ width: 480, height: 270
});
</script>
<?php } else /* Access is denied to the current User. */ { ?>
Sorry, you do NOT have access to this file.
<?php } ?>
Depending on the settings, it will display:
Download Now
JW Player® appears here.
Sorry, you do NOT have access to this file.
The link works just fine (it references http://www.thenewtyt.com/?s2member_file_download=/video.mp4 – which does download).
The JW javascript can be directly accessed just fine by going to:
http://www.domainname/jwplayer/jwplayer.js
However, the jw-container DIV tag is of course no where references (there is no CSS file that it references). Where is that suppose to come since we manually installed the JW player per your instructions?
When I did finally get the video window to display, when you click START it errors saying the video cannot be found.
|
|
|
I absolutely have watched the videos (great to have) – and followed it exactly. And I get that error – just as others have. On a side note, one thing that it doesn’t mention is that if you haven’t entered in default download limits the video will not be displayed. I figured that one out after a bit, and at least now shows the window. But when you click play, it can’t find the video the download link works – but it’s using the S3 link rather than the CloudFront one.
The steps are rather simple: copy and paste the S3 settings, copy and paste the CloudFront settings, click the checkbox to auto-configure. That’s it. When that fails, it leaves us with a very frustrating “what next” feeling.
-
This reply was modified 4 years, 10 months ago by Mark R..
|
|
|
I’ve read many threads that tries to deal with this 400 error – and tried everything I can think of.
On a clean install, I try to set up CloudFront and also get the following error:
Unable to auto-configure Amazon® CloudFront Distributions.
Error code: 400. Error Message: Unable to create Amazon® CloudFront Origin Access Identity. Unable to create Amazon® CloudFront Origin Access Identity. Bad Request
I’ve triple checked the keys – copied directly without additional spaces. I still get this error.
Jason, since you’ve asked another member, here is my htaccess file:
===================================================
# BEGIN s2Member GZIP exclusions
RewriteEngine On
RewriteBase /
RewriteCond %{QUERY_STRING} (^|\?|&)s2member_file_download\=.+
RewriteRule .* – [E=no-gzip:1]
# END s2Member GZIP exclusions
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
===================================================
Any additional help would be greatly appreciated as we can not use S2 without this working.
|
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 
