Cristián Lávaque

That removes the box to opt into the email list when they register the WP account. It doesn’t remove MailChimp’s confirmation email when they choose to opt in.

Hi Kevin.

You can use the User Role Editor. Once activated, go to your users list and when hovering the user’s name, you’ll see a link named “Capabilities”. Click it and you’ll be taken to an editor to enable the WP capability for that particular user instead of the role. http://wordpress.org/extend/plugins/user-role-editor/

I hope that helps. :)

Hi Ganaxi.

The widget doesn’t have an editable template, but if you know PHP you can try hacking the code to achieve it.

No, using another widget should not jeopardize the access restriction, it’d just log the user into his account. Access is checked against the user’s account or whether he’s logged in or not, not how he logged in.

I hope that helps. :)

Thanks for the tests.

I see that when you remove s2Member, times drop to almost half. Remember that s2Member is loading it’s CSS and JS dynamically, through WP, so it’s basically loading WP again. If WP is not fast, then that is reflected when loading those files. If you improve the speed of the BuddyPress only version, it’d most probably improve the other one twice as much.

If you disable s2Member’s CSS and JS and not load them, but keep the plugin enabled, do you see a drop in speed in your tests? Try this must-use plugin hack (the first part lets you keep the JS/CSS for certain pages):

/wp-content/mu-plugins/s2hacks.php
[hilite pre_code]

Hi Charles.

No, sorry. s2Member manages access to the blog it’s installed in. It doesn’t do cross site access management.

You could create a hack to sell the access from another site, like having a button in another site pointing to the one you have s2Member in, but you’re still selling it through the site that’ll be managing the access to the content it hosts.

But you posed an interesting question that made me look at this from a different angle and will think about how it could be done.

If you had the two sites connected in some way, maybe… But the sale and EOT and that would probably need to be in the same installation, while access to content could probably be done in another site if you synch the access permissions between them in some way, probably using the notifications API would be a way.

This is definitely something you’d need to hack in some way, not something s2Member does normally.

I hope that answers the question, and I’m sorry I couldn’t help you more with it.

I’m sorry, we’re not taking customization jobs, Jason’s hands are full at the moment. :/

Ok – I love the challenge, tho im on a tight time schedule.

Yeah, I know how that is.

And you need to have two subscriptions in a single blog? Wouldn’t it work to have a separate blog for each?

p.s. I did hack this line just to check if there were any other issues. Then the server stated it was going to ignore this IPN. I’m presuming this is because the item_number and possibly other fields didn’t match. Does this mean I have to rewrite the packet completely to match a new subscriber profile? If so could you tell me which fields would need fixing?

I don’t know how to answer this one. I don’t know what your change the code was, or what exactly should happen in the code there for s2Member to work. I’m emailing Jason and will have to wait for his input.

Got it, thanks. I already emailed him. I’ll let you know as soon as I have news, or he’ll just post a reply here. :)

Hi Ray.

You may want to ask PayPal about that one. Do you have the DPRP service? That’s for recurring payments.

I’m glad you solved it! Thanks for the update. :)

Yes, it’s not ideal, but it’s very secure to validate the user before serving it, and not making it possible for someone to share the URL to the actual file later. We’re looking at how to improve it in the new s2Member.

Hi Jay.

ALso …Not sure why I can’t make the “Membership Options” page my Sales page?

I tried and I get this..

s2Member: Your Membership Options Page is currently configured as your Home Page ( i.e. static page ) for WordPress®. This causes internal conflicts with s2Member. Your Membership Options Page MUST stand alone. Please correct this. See: WordPress® -> Reading Options. Or change: s2Member -> General Options -> Membership Options Page.

Yeah, there can be problems if the page you choose for the Membership Options is also set as the static home page for WordPress. You can have two separate pages with the same content (sales copy) or protect the Home one so people will be sent to the Membership Options one.

Squeeze >> Option to AWeber >> Thank You Page (that I will monetize) …and then receive access info to the Members Area by email.

But going through the instructions it look like I have to do something like this…

Squeeze >> Option to AWeber >> Membership Registration Page >> Thank You Page (that I will monetize)

I think either one is possible. Another you could try is:

Squeeze -> Registration/optin -> Thank-you

If you integrate s2Member with AWeber, then new registrations can be added to your AWeber list automatically. Then the opt-in would really be a registration form. Video » s2Member (API List Servers)

If you want to have few fields, you can not require the first and last names and not allow custom password. Then you’d be left with just the username and email address fields. [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields[/hilite]

And if you want to use the email address as the username, you can try this hack: http://www.primothemes.com/forums/viewtopic.php?f=4&t=15672&p=49082#p49082

You can then copy the registration form’s code from the default registration page and paste it in the HTML tab of your squeeze page.

I hope that helps. :)

I see. Please remove all the lines before the code I provided, you should just have the lines I posted earlier. And don’t use Dreamweaver, probably better if you just open it in Notepad.

Cool. :)