Cristián Lávaque

Hi Hari.

I have an update on this question – I restricted the Free Videos using “Page Restrictions”. So for 12 free videos, I restricted 12 pages because each free video is on its own page. But now, if itry to access one page, I have to login, and then if try to access another page, its asking to login again. This seems like its a cookie issue, but my browser is et for cookies. My cookies are working correctly on all other sites. How do we fix this ? It seems silly that a user has to login 12 times to see 12 free videos.

Let me know if this article helps with that: Knowledge Base » Logged in but am considered logged out

The second question still remains – how do we ensure login / register before a Buy transaction. Just to clarify – the Buy operation is being done a Specific Post/Page access product. This by default allows purchases without registration. But we want to force a login or registration.

The Specific Post/Page restriction is not compatible with the Levels restriction. What do you want to force login for, viewing the pages protected with Spec Page restriction? Or to purchase access to those pages?

If you’re going to require registration, then you can sell those individual pages with custom capabilities instead of Spec Page restrictions. Video » s2Member (Custom Capabilities)

To create a free registration form in a page, you can use the free registration pro-form: [hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms[/hilite].

To add a login form, as an option for those already registered, you could use the s2Member Pro Login Widget. [hilite path]Dashboard -› s2Member® -› API / Scripting -› Pro Login Widget (via PHP)[/hilite]

I hope that helps. :)

Jennifer, your form with the payment plan selection doesn’t include a [hilite mono]desc[/hilite] or [hilite mono]ra[/hilite] input tag, so they won’t be in the [hilite mono]$_POST[/hilite] array.

Your hack code is adding those to the [hilite mono]$attr[/hilite] array for the [hilite mono]ws_plugin__s2member_pro_paypal_checkout_post_attr[/hilite] hook, which is something else. That hook is at the point of processing the pro-form for checkout.

If what you want is to reload the page with the pro-form, now updated with the payment plan’s description and amount, you need to use a different thing.

Here’s what you could try in the page itself, without an s2hacks file:

[hilite pre_code]
array('ra' => '20', 'desc' => 'Student/Senior $20 USD yearly'),
2 => array('ra' => '35', 'desc' => 'Basic $35 USD yearly'),
3 => array('ra' => '50', 'desc' => 'Not-For-Profits $50 USD yearly'),
4 => array('ra' => '75', 'desc' => 'Business $75 USD yearly'),
5 => array('ra' => '100', 'desc' => 'Patron $100 USD yearly'),
6 => array('ra' => '500', 'desc' => 'Benefactor $500 USD yearly'),
);

echo '

';
foreach ($mlevels as $k => $v)
echo '' . $v['desc'] . '';
echo '

';

if (isset($_POST['mlevel'])) {
$mlevel = (int) $_POST['mlevel'];
echo '['.'s2Member-Pro-PayPal-Form level="1" ccaps="" desc="' . $mlevels[$mlevel]['desc'] . '" ps="paypal" lc="" cc="USD" dg="0" ns="1" custom="www.jdaviswebdesign.com" ta="0" tp="0" tt="D" ra="' . $mlevels[$mlevel]['ra'] . '" rp="1" rt="Y" rr="1" rrt="" rra="2" accept="paypal" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]';
}
?>
[/hilite]

(Had to do the [hilite mono]['.'[/hilite] at the beginning of the shortcode to avoid having it parsed here, sorry.)

I haven’t tested this, so you may need to fix it a bit, but it should give you an idea of what to try.

I hope it helps.

• This reply was modified 4 years, 5 months ago by  Cristián Lávaque.

Hi Tom.

First off I want to thank Jason and all those who are responsible for this incredible product. I have been amazed at the functionality and the versatility of the free version and am sure I will feel even more happy with the pro version.

Thanks for the kudos! :)

“Error Message: Unable to delete existing Amazon® CloudFront Origin Access Identity. Unable to delete existing Amazon® CloudFront Origin Access Identity. Bad Request”

Here’s a tip to fully reset your Amazon S3/CloudFront integration, to then start from scratch: http://www.s2member.com/forums/topic/cloudfront-err-400-unable-to-del-existing/#post-15884

Let me know if that helps!

Hi TJ.

I emailed Jason asking him if this is possible. He may reply in a few days because he’s not opening his email every day lately, but I’ll let you know as soon as I hear back from him. :)

Hi Adam.

Are these products in separate sites? If so, then yes, you could probably try doing a user export from one to import into the other one.

Password migration would not be possible, though. They’d have to be given one by you or required to create their own again.

[hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Exportation[/hilite]
[hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Importation[/hilite]

I hope that helps. :)

Hi George.

I don’t have BuddyPress installed to check this, so could you post here examples of the URLs that’d be used to post this content? If you can pick from them a part that is unique to them, you could use the URI restriction on them. [hilite path]Dashboard -› s2Member® -› Restriction Options -› URI Access Restrictions[/hilite]

I hope that helps. :)

Hi Lisa.

Could you verify that you don’t have an extra folder there? Sometimes it happens when unzipping the contents of the plugin. s2Member® » Pro » Install/Upgrade Instructions

You should end up with /wp-content/plugins/s2member-pro/pro-module.php, along with several other files and sub-directories. Make sure you don’t accidentally nest two
/s2member-pro/s2member-pro directories together. For example, this is NOT correct:
/wp-content/plugins/s2member-pro/s2member-pro/pro-module.php.

Also, make sure that the version of the s2Member Pro matches the one of the s2Member Framework.

I hope that helps. :)

Hi Philly.

Not sure if it’s specific to you or general. s2Member is just using the wp_lostpassword_url WP function, so if it’s general then it’d be a bug in WP itself. http://codex.wordpress.org/Function_Reference/wp_lostpassword_url

s2member-pro\includes\classes\login-widget.inc.php
[hilite pre_code]
echo '' . _x ("forgot password?", "s2member-front", "s2member") . '' . "\n";
[/hilite]

If you do [hilite code][/hilite] in one of your posts, do you get the correct URL?

Maybe another plugin is causing this in your installation? You could test deactivating other plugins one by one, checking that URL after each to see if changes.

I hope it helps. :)

Great. Glad you found the reason behind it. :)

I don’t know if that’s how PayPal calculates terms and s2Member is just following their standard.

When it’s a month or a year, it should be probably calculated with a calendar instead of a set number of days.

Ooooh, it’s just going to be very awesome. Too much for words, you’ll need to see it and play with it to see all the possibilities. :)

Can’t say too much about it, though, since it’s not finished. I don’t want to say something that doesn’t end up in the release.

Jason is very advanced in the development, the core is finished, he’s working on some missing classes. After that we’ll work on the UI and release a private beta to zap bugs and polish rough spots before the first public release.

Yes, essentially I would love to know who downloads things and when. For icing on the cake it would be great to know if there were people trying to download who didnt have permission yet.

Got ya. If I’m not mistaken, this may be possible. It’ll have plenty of logging, so this may be covered already. I can’t confirm it because I haven’t see it yet, but there’s hope.

Hi Ralph.

So, is it possible to allow registration without using Paypal and still require admin approval before allowing access “behind the curtain”?

Yes, you can let users register for free leaving registrations open, and they’ll be given s2Member Level 0 (free). [hilite path]Dashboard -› s2Member® -› General Options -› Open Registration[/hilite]

s2Member doesn’t have an account approval feature, but what you can do is protect the content at a higher level than the one they’ll get when they register. So protecting the content at Level 1, for example, will hide the content from new registrations. Then, you’d review new registrations and your account approval would consist of manually upgrading their account from level 0 to 1.

I am wondering if there is a way to create these fields in s2member Pro? If the Pro version allows for unlimited additional fields, I believe I could use PhpMyAdmin to view your table names, change the field names in my exported sql file to match those of s2member Pro and then import the data, right?

You can, even in the free version of s2Member, create custom profile fields to add these to their profiles. [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields[/hilite]

and then displaying them on a “friends” page based on specific restriction fields in order to protect privacy.

What s2Member doesn’t provide are public profiles, so that one user could see the profile of another. You’d need to add this yourself in a WP page, querying user data to display it to others. There are WordPress functions you can use for this.

s2Member also has a couple of functions that can help:
http://www.s2member.com/codex/stable/s2member/api_functions/package-functions/#src_doc_get_s2member_custom_fields()
http://www.s2member.com/codex/stable/s2member/api_functions/package-functions/#src_doc_get_user_field()

If that were the case, then I would think there might be a way for previous users to be “already registered” even if it meant ticking a box or whatever in PhpMyAdmin.

s2Member Pro has a User Import tool that you can use to create all their accounts from a CSV file, including the custom profile fields. After creating their accounts, you can email them letting them know about it. [hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Importation[/hilite]

---

Let me know if that helps and if you have other questions! :)

Hi Darren.

Did the user pay a few days before Aug 1st? If so, it seems that the year was calculated from the date it was paid, disregarding the days he had left from his last payment.

That’s the behavior with subscriptions, if the user starts the subscription again, then the days left from the previous one will be lost. If you’re using subscriptions, then you’ll need to add some PHP code to your button to calculate the time he has left and add it to the new time he’s paying for.

With buy-now transactions, though, you can have the new paid time be added after the time he had left. You’ll find the setting at the bottom of the EOT panel. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior[/hilite]

Fixed-Term Extensions ( auto-extend )?
This setting will only affect Buy Now transactions for fixed-term lengths. By default, s2Member will automatically extend any existing EOT Time that a Customer may have.

We’re working to improve this in the new s2Member.

Hi JB.

Those fields you say are not populated, are stored in the usermeta table. Maybe you missed it when you migrated the users?