About: Sam Lee

Thanks a lot Raam, for bringing up the option of capabilities, that might actually provide an alternative.

Not wanting to generate buttons for each premium post, we could probably create PP form buttons in the template and target everything based on IDs, to differentiate between conditionals.

The issues that I’m foreseeing are:

1. If using capability buy-now buttons, it doesn’t seem possible to limit the access time, rather it would grant perpetual access to that capability/premium content
2. It would require membership, so each time a previous capability customer wants to purchase again, they need to login as otherwise they’ll probably add same account details again and it wont work in WP/S2Member as an account with those details already exists

To get around the first issue, I guess one could set an account limit, so that the account expires within a certain time, but that would get messy if they want to buy more capability access to other content within this timeframe.

But it’s a step forward, although I’m still not sure it’ll completely solve our issues.

On a different note, I’ve not had a chance to look into how capabilities are displayed in the member admin, but can one output a list of all the capabilities they have access to? Since we’ll use post IDs for those, we could then use the ID to get the permalink and be able to display a list of all their premium post access.

In terms of the other issue, of where the confirmation email links point to, that’ll be relevant to us later, as we’ll use buttons instead of pro forms (since we need to use AliPay as well).

If it’s not possible to send customers slightly different URLs (with a language variable) in the confirmation email, then we’ll have to work around it by setting up custom payment gateway return pages.

The interest in having s2Member fully and conveniently multilingual (compatible with WPML, qTranslate etc) is probably not something a lot of people would use, but it’d be a great addition to your excellent plugin!

I should perhaps add that the above is for Pro Forms, when users sign up for free. Level 1 is used for English, and level 2 for Chinese users. On the whole it works fine, apart from the above issues.

In the near future, we’ll require paid membership however, and will use both PayPal and AliPay. Since AliPay is buy-now-button only, we’ll set things up to use buy-now-buttons for PayPal as well.

This throws up a couple of other translation issues – some of these might be due to WPML, we’re investigating these.

But I’m also trying to translate the return-pages when coming back to the site (those grey s2Member pages) and finding that I can’t translate many of them. Looking in the plugin code, I’m seeing a lot of:

_x ("Continue", "s2member-front", "s2member");

I don’t know gettext all that well, but wondering if these aren’t wrong? Will it still work with a space between _x and ( ? Shouldn’t it be:

_x("Continue", "s2member-front", "s2member");

If I can’t translate these return pages, I might bypass them altogether with the success shortcode. What I’m not sure about though, is how it works with registration access links that are sent out by email – do these point to the s2Member return pages, or to the success-URL? If bypassing the return pages, I’d like to send people straight from PayPal/AliPay to the account creation pages (that are otherwise disabled), but I don’t know if that works for the email links as well..