AnotherOpus

I don’t know. When I typed in the password it only had one field and no verification, and the field was password type so I couldn’t see what I was typing. Maybe I mistyped the password?

Hello Bruce,

Thank you for this info.

If I use a Thank You page, according to the info at…

s2Member® -› PayPal® Pro Forms -› Custom Return URLs Upon Success,

…what do I do about the PayPal® PDT Auto-Return Integration setups? Will there be a conflict?

And I looked at this page and section and I do not see anywhere to specify that s2Member should use a page such as thank-you.

I’m looking for the ability to have PayPal return a successful subscriber to a Thank You page, where we could have a generic message as well as use some of the common s2Member [ short codes].

Also, related to this, is there a way to send PayPal failures to a failure page? E.g. so that we can create a custom message for the ever so common Error # 36 message –which is meaningless to a would be subscriber, and leads to a small chain of emails with them each time.

Thank you,

Chris

TJ!

Elegant, simple and perfect solution!

I only wish our friends at s2Member had designed the CSS classes and IDs so that all fields could be changed with single code elements (e.g. s2member-field-email, s2member-field-first-name, etc).

…but this is a superb work around!

And it gives an excellent way to refine the forms.

Thank you,

Chris

Hello Cristian,

We have the API notifications set up already and they’re working–we get individual notifications and a daily report/summary/digest would be useful.

Our goal is to get a monthly report out of s2Member so we can compare it to the PayPal info.

It is difficult to compare s2Member to PayPal on a day by day basis due to the EOT difference where a member continues to have access until their payment date. So the pairing/matching is not exactly a day to day sync. A member may stop paying on PayPal and PayPal will report them as such. But then s2member won’t give them an EOT until the actual payment renewal date (based on the date they joined.)

On the other items, the members we need to sync up are people who joined the site before we used s2Member. These members have been entered manually. We want to know if we can go back into these records and enter a PayPal Paid Subscriber ID number. Then set their subscriber gateway to PayPal.

We’re hoping that if we get all the paying members in a report from PayPal, that we can compare that to a report from s2Member and find the members who are not paying on PayPal, and the members who are paying on PayPal. And we can see from the s2Member report which members do not have a Paid Subscriber ID.

Then we can manually demote all of the non-paying members. And we can enter the PayPal Paid Subscriber ID for the members who are paying, but don’t have PayPal info in s2Member.

We’re hoping that by doing this exercise we can isolate the exceptions and finally stop the issue where members have paid access but they are not paying and they never get an EOT demotion.

Integrations are there and registrations work–as do EOT’s, cancellations, upgrades and downgrades, for the majority of our membership.

We do have logging enabled.

Thank you,

Chris

Hello Cristian,

I tested the query string format on two podcast posts from last Friday, April 19, 2013.

And when I saved the posts it gave this error at the top of the page (above where it said the post was updated):

Error [http://www.domain.com/?s2member_file_inline=yes&s2member_file_remote=yes&s2member_file_download=file.mp3]: Unable to determine content type of media (e.g. audio/mpeg). Verify file extension is correct and try again.

And then I tested the link by checking our podcast in itunes for that day–and it worked.

However I’ve since discovered that the two podcast posts didn’t save that new query string URL–they reverted to the old URL. So BluBrry PowerPress stripped out the query string URL.

That leaves us with the option to get WPEngine to repair the mod rewrite URL.

I’ll keep this thread updated with our progress for others to reference.

Thank you,

Chris

Hello my friends,

Thank you for the updates and solution.

I copied the info to WPEngine so that they can take a look at resolving this on their servers.

Meantime…

I tested the normal query string on our live, staging, and sandbox sites, as well as on the bare bones install I did on WPEngine, and another bare bones install I did on a separate premium shared host.

Most interesting was that our live site, which has the buckets set to full public access–required authentication using this link. Then the streaming worked.

Our Staging, Sandbox, Bare bones and the Bare bones unique host site all use the same test Amazon AWS account, same S3 bucket, but of course each use their own unique s2Member generated CloudFront distributions.

I tested in logged in browsers and in logged out browsers. The result was the same each time.

Our Staging installation and my non-WPEngine hosted installation asked for authentication, and then began streaming!

However the Sandbox and the Bare bones installs on WPEngine, which use the same account info–asked for authentication and then gave this error:

<code>
This XML file does not appear to have any style information associated with it. 
The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>F7F28F82C235FF66</RequestId>
<HostId>
AKwX4CxJcViNOs7xK0JL+Anee2M9tUoyzdSFGoEotXlK2vNBZ0AhV8itB83Ff2kM
</HostId>
</Error>
</code>

That seems crazy because all four use the same AWS info and have the same settings in s2Member.

When I set up each of the sites, I diligently flushed the AWS info using the s2-hack PHP file method, then entered only the S3 info and saved. Then I entered the CloudFront info and saved. In all four instances the CloudFront distributions set up perfectly when I saved the s2Member settings.

– – –

The only reason this is a concern is because now my next step is to go to the Live site and do two things:

A. Set the S3 bucket back to default settings so that it always authenticates for all files, and
B. Begin using the standard query string for all audio streaming files.

…the concern comes in that two of four sites don’t work. And while the main goal is to reestablish authenticaiton on our live site, it would also be nice to set up our Staging and Sandbox sites to use the same AWS account and S3 bucket as we do on the live site.

Any thoughts on how that will work or fail? …and advice?

Thank you,

Chris

Cristian,

An important clarification…

You mention, ” I just tested the mod-rewrite format with a file in my own test installation with Amazon S3+CF integration, and I could download the files just fine…”

We can also download without any problems.

This is a streaming only issue.

All of our video files download and stream.
All of our audio files download.
None of our audio files stream.

This was not the case three weeks ago.

Thanks,

Chris

Hello Cristian,

I finished setting up s2Member and AWS on the new bare bones site.

Everything set up correctly (s2Member, S3 credentials and bucket, as well as the CloudFront credentials and the s2Member created download distribution and streaming distributions).

On the AWS side both of these distributions are created and enabled.

Download works:

http://www.ourdomain.com/?s2member_file_storage=s3&s2member_skip_confirmation=yes&s2member_file_download=filename.mp3

…and streaming fails:

http://www.ourdomain.com/wp-content/plugins/s2member-files/s2member-file-remote/s2member-file-inline/filename.mp3

This is using the same AWS account and S3 bucket as mentioned and tested above. The bucket was created and left as default–which Amazon AWS recommends. And it is secured.

The download and streaming distributions are new and created by s2Member. They are enabled.

So a bare bones site with s2Member and AWS info–no other plugins–fails to stream.

Streaming worked three weeks ago, before I started this ticket. Something changed between WPEngine, s2Member and AMazon AWS–and it also affects this bare bones site. I now see that the theme and plugins are not part of the problem.

Chris

Hello Cristian,

The above link also gives a 404:

http://ourdomain.com/?s2member_file_storage=s3&s2member_skip_confirmation=yes&s2member_file_download=/filename.mp3

I’m sending the info you requested via the private contact form.

Thank you,

Chris

Thank you Cristian,

I get a 404 error if I use that link with our domain and our file name.

Hey Bruce,

This one came in 19 hours ago:

Maybe it’s asking me to Approve, Trash or Spam it because I was the author of the post?

However I thought only site admins would get these emails.

Lastly, you good people should consider using Akismet (free), or some other plugin that filters spam on the site. Also, another good requirement is to only allow registered and logged in users to do anything on the site–then you could track these idiots. When your site is so open many SEO gray and black hat tools such as SENukeXCr find your site and automate these things. You gots to be pro-active in blocking non-registered people in today’s internet world.

Chris

– – –

from: s2Member®
to: chriseller.com@gmail.com
date: Tue, Apr 9, 2013 at 1:47 PM
subject: [s2Member®] Please moderate: "How to Hide Member Pages in Site Map & Menu"
mailed-by: amazonses.com
signed-by: websharks-inc.com
: Important mainly because of your interaction with messages in the conversation.

– – –

A new trackback on the post "How to Hide Member Pages in Site Map & Menu" is waiting for your approval
http://www.s2member.com/forums/topic/how-to-hide-member-pages-in-site-map-menu/

Approve it: http://www.s2member.com/wp-admin/comment.php?action=approve&c=198
Trash it: http://www.s2member.com/wp-admin/comment.php?action=trash&c=198
Spam it: http://www.s2member.com/wp-admin/comment.php?action=spam&c=198
Currently 10 comments are waiting for approval. Please visit the moderation panel:
http://www.s2member.com/wp-admin/edit-comments.php?comment_status=moderated

– – –

Hey Cristian,

Thanks for the support.

I believe this also, and I realize it’s easy to test–but I’m leary of testing this because we upset our members a couple of months ago when we accidentally used the same bucket on our staging site as we had on our live site. Needless to say all media died on our site and we didn’t know what the hell had happened! …and my director made me sit in the corner for an hour because I didn’t know what caused it. Oh, yeah, I also didn’t get fruit cup with dinner. :)

When something breaks on our site our 11,000+ paying members come out of the woodwork at us like the robots did in the end of iRobot, the apes in planet of the apes, or the aliens on the pyramid after that poor last, defenseless predator… I am Legend, 28 Days Later–you get the picture.

If I jack things up again I’ll be buried in concrete with Jimmy Hoffa.

Can you give me a definitive answer on this? :) …as in, “Yes, 100% if you use the same security credentials in another s2M, on another site, but use different buckets in each one, why you’ll be just fine.”

Amazon AWS support let me know they do not see a problem on the AWS side using the same security credentials in more than one site.

– – –

Another issue is we actually DO NEED to use the SAME bucket on the other site! Else we’ll be paying for duplicate AWS bucket storage. Is there a work around in s2Member that will allow is to do this?

Thank you,

Chris

Thanks.

No, that logging was not enabled.

But I did enable it now so we can see what’s what soon.

Thank you for helping us find a solution to this.

Chris