Jason (Lead Developer)

Thanks for your reply :-)

Find this portion of your Button Code please.

<form action="https://www.paypal.com/cgi-bin/webscr" method="post">

Add this JavaScript check if you like. Adding an onsubmit JavaScript handler to the FORM tag.

<form action="https://www.paypal.com/cgi-bin/webscr" method="post" onsubmit="if(Number(document.getElementsByName('a3')&#91;0&#93;.value) < 1.00){ alert('Must be greater than $1.00 please.'); return false; }">

Result looks like, functions like, this…

And is there any chance a later release of S2Member might incorporate pay what you want built in? I can see there being a lot of demand for this.

Definitely :-)

How To Customize The 503 Error Message, Should A Link Expire

Please see this post: http://www.s2member.com/forums/topic/registration-link-expiring/#post-37928

Thanks for the follow-up :-)

Just to clarify in this thread. Registration Access Links self-expire as an additional line of defense (i.e. this tightens security, it’s NOT the only line of defense). Typically, a customer completes checkout and is sent a Registration Access Link via email. That link is good for 2 days (48 hours) by default. This is a scenario that is repeated many times in the free version of s2Member®, where PayPal Buttons have been integrated as opposed to s2Member® Pro Forms, which do NOT use Registration Access Links at all (the process is smoother for a customer).

Having two full days to click a link granting you access to something that you just paid money for, and have not received yet, is usually enough for a customer. In situations where it’s not enough, for any reason, a customer may contact you about this, and it would be a good idea to generate a new Registration Access Link for them from the Dashboard. See: Dashboard -› s2Member® -› PayPal® Buttons -› Registration Access Links

How To Increase This Time Frame

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_register_link_exp_time', 's2_register_link_exp_time');
function s2_register_link_exp_time($what_s2_says)
	{
		if($what_s2_says === '2 days')
			return '10 days';
		// Anything compatible with PHP's strtotime() function will work here.
		
		return $what_s2_says; // Default value.
	}
&#91;/hilite&#93;

<h4>How To Customize The 503 Error Message, Should A Link Expire</h4>

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('gettext_with_context', 's2_translator', 10, 4);

function s2_translator($translated, $original, $context, $domain)
	{
		if($context === 's2member-front' && $domain === 's2member')
			if($original === '<strong>Your Link Expired:</strong><br />Please contact Support if you need assistance.')
				return 'My custom message with HTML markup.';
		
		return $translated; // Default translation value.
	}

• This reply was modified 3 years, 11 months ago by  Jason (Lead Developer). Reason: Adding 503 sample code

Please see my previous post where I clarified what this means.

Please let us know if problems persist :-)

KB article written to describe the process of debugging HTTP connections.
See: Knowledge Base » Debugging HTTP Connections

Thanks for your reply :-)

You said that our Server Scanner found this issue on your installation.

[WARNING] Plugin Directory Checksum (s2member)
Although NOT required, s2Member® recommends that you reinstall the following plugin directory: /home/rghjbrw/public_html/premium/wp-content/plugins/s2member. The checksum for this plugin directory (cc4870a41a3ee6b46af5aed5e36af405), does NOT match up with the official release of this plugin (afc37ccab81c6d39df41e3f6c7737e5c).

Yes, this would indicate a problem with your installation. Have you modified any of the s2Member source code files? I would suggest that you re-install the s2Member Framework plugin to ensure that you’re running the latest release, and without corrupt or missing files.

——– Output string/vars: ( Wed Jan 16, 2013 2:55:41 pm UTC ) ——–

array (
‘__error’ => ‘Error. Please contact Support for assistance.’,
)

This error would indicate to me that your server is having some trouble with HTTP connections. I recommend this KB article. Please install the logging routine described in that article and monitor the log file for HTTP connection issues. Feel free to submit your HTTP connection log file privately, so we can help you review. Please see: Knowledge Base » Debugging HTTP Connections

Please submit log files privately in the future. See: s2Member® » Private Contact Form

Thanks for your reply :-)

If you will, please follow the instructions here and let’s enable some additional logging routines on your installation. When/if this happens again (with this logging routine running), please send the log file over to us for review. That way we can try and make sense of this.

I don’t see anything wrong with your Roles/Capabilities. I suspect this is caused by HTTP connection failures of some kind. These can occur for any number of reasons. Sometimes it’s due to a hosting issue, sometimes it’s due to server load. Hard to tell for sure. The logs should tell us more :-)

Please see: http://www.s2member.com/kb/debugging-http-connections/

Thanks for the follow-up :-)

1. Once the user is logged in successfully, he/she must be redirected to payment page.

What you’re referring to is what s2Member would consider a Billing Modification.

If you’re using Pro Forms, you’ll want to use a Billing Modification Form, which upgrades an existing User/Member to Membership Level #1, 2, 3, 4 (whatever you like). A Pro Form for Billing Modifications will not work unless an existing User/Member is logged in, and that’s what you’re describing here. It’s fine if they’re not paying you yet, s2Member is still Modifying them, and we are not registering someone new in this case.

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Billing Modification Forms

2. Payment page will be accessible to only those who’re already a member of this site., not to everyone.

You would protect this Page using s2Member’s Page Restrictions, and require Membership Level #1, or whatever you require in order to access this Page that contains your Pro Form for Billing Modifications. This way it’s not available for public access, an existing User/Member must be logged in before they access it.

See: Dashboard -› s2Member® -› Restriction Options -› Page Access Restrictions

3. Also, please let me know that how can I create a payment/paypal page where I will take payment information from a user.

The instructions I provided above should get you there. As for the redirection itself, you will need to get creative, because you need to do this conditionally (i.e. only redirect if they are NOT a paying customer yet).

Here Is One Idea For You (Multiple Login Welcome Pages)

See: Dashboard -› s2Member® -› General Options -› Login Welcome Page
Use one of s2Member’s Replacement Codes here, and type your own Login Welcome Page URL.

Now create Login Welcome Pages for each Membership Level you’re selling (including Membership Level #0, for Free Subscribers). For instance, you might have the following Pages.

http://www.example.com/0-account-page

This Page would contain the Pro Form for Billing Modifications, along with any other details you’d like to publish on this Page. So this is the redirection page you were asking for. This is where a new Free Subscriber would be taken, upon logging into your site (if they are still at Membership Level #0, a Free Subscriber).

http://www.example.com/1-account-page

This is the Login Welcome Page for paying customers that are at Membership Level #1. Put whatever you like here. For instance, links to the content that is available them; now that they’re a paying customer.

Thanks for the follow-up :-)

I’m not aware of any incompatibilities between JW Player v5 or v6 and WordPress v3.5. We’ve tested these in our lab without issue. These two software applications don’t really need to be compatible with each other anyway, because one is a video player, and the other is a CMS, and the two apps don’t really share any code or framework together, other than a JavaScript file JW Player pulls in, which seems to work fine within WordPress.

Thanks Jason – I understand and I went through the set up again.
Unfortunately I end up with “Sorry, you do NOT have access to this file.”

Does this error come from the JW Player plugin for WordPress integration, or from the s2Member code sample? If it’s from the s2Member code sample, please paste your final code here and we’ll review it with you.

Please let us know if problems persist :-)

Thanks for your reply :-)

Right. It’s not that we don’t want to help, but we have to limit our scope of support in these forums so that we have time to assist site owners who are paying us for support services. I’ll try to answer this in the context of a Pre-Sale question (i.e. as a question about features or functionality), but I can’t offer debugging assistance here.

I am a newbie to S2member but have been using WP for some time. I have set up a site that requires areas to have limited access. So far everything is working well other than one page which I seem to be unable to protect. It is a kind of portfolio listing/thumbnail page. I have set this to be protected but it still shows if you aren’t logged in. I think the issue is because the page content is called in somehow by the theme as you have to set this page in the theme options as that for the portfolio. I hope that makes sense as I know it’s a little complicated.

s2Member (even the free version), comes with a feature called “URI Restrictons”. Any Post/Page (or some other type of content) that is declassified as a Post/Page/Category/Tag/etc (as you mentioned your theme is doing with a specific Page that it assigns to some other aspect of your site), you will need to protect that content using a URI Restriction with s2Member; because when it’s declassified by your theme and served up differently on-site, WordPress does not consider it a Post/Page any longer. That is, it’s not served as a Post/Page, it’s served as something slightly different, by your theme in this case.

See: Dashboard -› s2Member® -› Restriction Options -› URI Access Restrictions
See also: Video » s2Member (Content Restriction Trouble?)

Thanks for the heads up on this thread :-)

That’s really interesting. Thanks for reporting this important issue.

I was unable to reproduce this in our lab. s2Member® does NOT attempt to pass a phone number to Authorize.Net, and so long as you leave that field that you mentioned, unchecked, the Authorize.Net API does not require it either; which is good because many customers prefer not to provide a telephone number.

Since you’re reporting that Authorize.Net IS requiring you to provide that field (or, it actually appears to me that your installation is attempting to pass a phone number that is empty or invalid), I would contact Authorize.Net about this and ask them if your underlying merchant bank (i.e. Wells Fargo, or whoever you use), is forcing you to supply that information, regardless of your Authorize.Net configuration? Something like this?

Also, I know you’re working with some developers. You might check with them to be sure they’ve not modified s2Member in any way that would cause it to pass a phone number field, either via XML or via NVP? For instance, even if you attempt to pass an empty field (s2Member does NOT do this by default – it does not send a phone number field at all, by default), but if you attempted to pass an empty field, you might see this error.

Please let us know if problems persist :-)

Also, if problems continue, please submit a Dashboard login and we’ll run diagnostics for you.
Please do that privately: s2Member® » Private Contact Form