Cristián Lávaque

Try changing the hack file to s2member-o.php. See the article I linked to earlier, the section on s2Member-only Mode, the tab on how it impacts hacks. Knowledge Base » Hacking s2Member® Via Hooks/Filters

Is that the license you have with this account or did you have your own license before and now purchased an upgrade for your client? If the license you have with this account is your client’s, then you can change the profile details and make the account theirs.

I had not seen this problem before, that I remember. I’m guessing, since wp-login.php is working for you, that you had the problem using the s2Member Pro login widget, is that correct? Do you have the same error if you try other login widgets?

We don’t know our widget to have a problem that’d cause that error, and I can’t reproduce it in my site, so I agree with you that it seems to be specific to WP Engine. If they try logging in using the widget and get the 324, maybe their server logs show what the problem is before the error is returned.

You can also try these in case it helps: Knowledge Base » Common Troubleshooting Tips

So you’re importing with a database tool?

If you have the new WordPress running, you can export s2Member’s options and the WordPress users from the old one, and import them into the new one using these tools: [hilite path]Dashboard -› s2Member® -› Import/Export[/hilite]

Those tools don’t migrate WordPress, though.

Great, I’m glad you figured it out. Thanks for the update. :)

There are already quite a few plugins that allow a user to join a website with their FB/Tw/G+ account, but if using s2Member, those plugins create new user accounts on top of the registered s2Member user.

The way I understand it, WordPress still needs the person to have an account in the blog, those services may provide credentials, but they don’t replace the WP account.

If the user already has an account in WP, can he then login with one of those services to get to the previously existing account or is a new one created? Try this with s2Member inactive too, can you reproduce that problem without s2 or does it go away?

A user who doesn’t have an account yet, logs in for the first time using one of those services, logs out, can he then login back in with those services without having yet another WP account created? Try this with s2Member active too, please.

I know that other site owners have successfully implemented these single sign-on plugins in the same site they have s2Member, so it’s either a misunderstanding on how they’re supposed to work, or that particular plugin implements it in a way that isn’t compatible and you can try other plugins of the same kind.

If you have each chapter at a different level with s2Member, then you can assign each to a different MailChimp list. [hilite path]Dashboard -› s2Member® -› API / List Servers -› MailChimp®[/hilite]

If the chapters are specified with a custom capability, you may want to use MailChimp’s merge fields, you can try this hack: http://www.primothemes.com/forums/viewtopic.php?f=4&t=15676&p=50550#p50550

If you’re specifying the chapter in a custom profile field, you can modify the hack above. See also: http://www.s2member.com/codex/stable/s2member/api_functions/package-functions/#src_doc_get_user_field%28%29

Jason didn’t mention this, but I’m guessing it’d work, if you use buttons created over at PayPal.com following the instructions to integrate with s2Member, you may also be able to add the cancel_return URL there. These buttons only works for new WordPress signups, not upgrades of existing users. See: Knowledge Base » Using Buttons Generated @ PayPal.com

This is what Jason said:

I never received a definitive reply from PayPal on this. I get a big run around everytime I get specific about something and need real tech support. However, my research online and my experience with other vendors integrated this way with PayPal; is that this IS by design.

When s2Member integrates via Payflow Express Checkout and it goes through as a Billing Agreement, there is no description provided by PayPal during checkout; even if we supply one. Nothing we can do about this.

On the PayPal side of things, the site owner is creating an agreement w/ the buyer; and with a Billing Agreement, we can charge anything we want to, and at anytime we like. Thus, PayPal chooses NOT to display a description; they simply state “Future Payment” (e.g. they are VERY vague intentionally).

Here’s what Jason said:

There is no shortcode attribute for this presently.

See: s2member/includes/classes/sc-paypal-button-in.inc.php
Specifically this template replacement code: [hilite mono]%%cancel_return%%.[/hilite]

See also: s2member/includes/templates/buttons/paypal/ for all templates that use this replacement code.

What this does? Currently, s2Member simply sets this to the home page of the current site that is implementing the PayPal Button. It’s really NOT an important setting in my view. It’s often excluded completely by many site owners.

If a customer clicks the “Cancel Checkout” link during their checkout experience at PayPal.com, they are returned back to the site where they started from; based on the value of this setting. s2Member returns them back to the home page of the site (e.g. [hilite mono]%%cancel_return%%[/hilite] defaults to [hilite mono]home_url('/')[/hilite]).

With s2Member Pro Forms, this value is established dynamically, and s2Member will return any customer that cancels an Express Checkout transaction; back to the original Pro Form page they started from.

There isn’t a hook for it, though, so you’d have to edit the files directly.

Found the problem, it’s because those entries have the “fuzzy” attribute, so they’re being ignored and the original string used instead. http://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html

Jason updated the documentation in s2Member to warn about these. /s2member/includes/translations/translators.txt

FUZZY translation entries: If you’re updating an existing PO file (e.g. recompiling your MO file after changes in a new release of s2Member); please be sure to manually review any “fuzzy” entries. A fuzzy entry can occur as a result of changes from one release of s2Member (or s2Member Pro) to the next; where small changes in text might render your translation invalid (e.g. fuzzy).

Depending on your PO file editor, fuzzy entries may need to be reviewed and changes committed BEFORE you recompile; otherwise fuzzy entries will revert to their default state in your final MO file. Translations that are fuzzy, are NOT compiled into your final MO file. This can lead to much confusion. Please review any fuzzy entries carefully.

This is what Jason said:

Authorize.Net does not allow us to configure a Silent Post URL (aka: IPN URL) for each transaction. Like PayPal Pro, you will need a central IPN processor that forks to each of your installations if you intend to use a single Authorize.Net account with multiple installations of s2Member Pro; or other software apps.

There is an example in the s2m-pro-extras.zip file.
See: /s2m-pro-extras/authnet-central-ipn.php for instructions on how to do this.

You can find the extras zip file in your account page: http://www.s2member.com/account/

A new version of s2Member was released earlier today, and it includes some improvements to the IP restriction. Please try updating s2Member to benefit from this and let us know if you see the problem happening again. Thanks! :)