We are actually using custom capabilities to differentiate among the membership levels, so they are all technically level-1 members, but they have custom capabilities like "Alpha", "Bravo", etc.
I was building this:
At the top of the page we display a list of the 'levels': Alpha, Bravo, etc
Clicking on one of them would display the corresponding s2Member-Pro form to 'renew'.
However, it seems that the s2Member forms get thrown off if I include multiple ones in the same page.
So, when I have a single
- Code: Select all
<?php echo do_shortcode('[s2Member-Pro-PayPal-Form level="1" ccaps="+alpha" desc="ALPHA" ps="paypal" cc="USD" ns="1" custom="localhost" ta="0" tp="0" tt="D" ra="4242" rp="1" rt="Y" rr="BN" modify="1" accept="paypal" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]'); ?>
The page brings up the update form with the user info pre-populated (great)
But if my template includes that shortcode, AND a second one such as this one:
- Code: Select all
<?php echo do_shortcode('[s2Member-Pro-PayPal-Form level="1" ccaps="+beta" desc="BETA" ps="paypal" cc="USD" ns="1" custom="localhost" ta="0" tp="0" tt="D" ra="4242" rp="1" rt="Y" rr="BN" modify="1" accept="paypal" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]'); ?>
Then both forms think that this is a new user (so they display the whole form, with no pre-populated data, as if it was a new membership application).
Is this indeed a (current) limitation of s2Member (ie: only one s2Member form shortcode per page is allowed), or am I doing something wrong that may be triggering this?
('cause, of course, if this is a limitation I'll revert to using multiple pages - no biggie)
Thanks in advance,
F