Cristián Lávaque

Got it. A coder for this should not be expensive, it’d be a simple rule from what I understand. I’m not familiar with rewrite rules, otherwise I’d be happy to help with it.

Could you show me what the Membership Options Page vars are when redirected there? [hilite path]Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars)[/hilite]

That way we’ll know what restriction is being applied, to help us identify what the problem is being.

Chris, you seem to be having a shortcode parsing problem, most likely caused by the theme or another plugin.

As a test, could you change the theme to the default one and reload the page with the buttons? Does the problem continue?

If that dosen’t fix it, could you deactivate other plugins and test the button after each until you don’t get the error again?

I hope it helps. :)

Thanks for the updates, Andrew. I wasn’t aware of the incompatibility between the auto-login hack and the [hilite mono]success[/hilite] attribute’s replacement codes. About how to tell if it’s a free user, you could [hilite code]print_r($vars)[/hilite] in the hack and see what else you could use do identify him. You could probably add a piped value to the [hilite mono]custom[/hilite] attribute for the free registrations to pick them up in the hack’s conditional.

The other questions – how to get the remaining shortcode attributes to be passed to my success page, and how to get hold of the custom fields still remain. I suspect that the answer to the second question is something to do with ‘cv pipes’

So, even after removing the s2hacks.php file, your [hilite mono]success[/hilite] attribute’s replacement codes are not working? Or some are and others not? Which exactly?

Cool. Thanks for the update. :)

That’s great! Thanks for the update. :)

Let us know if you need help with something else.

Hi Shaun.

After making some changes to the Membership Levels / Labels section in the S2member settings

What changes do you mean exactly? The labels for the levels?

What role are you giving the users you created manually and aren’t getting the proper access to the content?

I’ve been enjoying working with S2member and have found it to be a very clever solution which is well supported.

Thanks for the kudos! :)

Hi David.

Could you tell us what is that you’re trying to do that s2Member wasn’t able to do as advertised? We’ll be happy to help you sort it out, or suggest a hack if it’s something that could be done with a customization we know about. :)

Just wondering if there’s a way to remove “s2member_seeking” from the url….

You mean the Membership Options Page vars? [hilite path]Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars)[/hilite]

There isn’t a setting to remove them, but if you don’t use them and it really bothers you to see them, you could create a rewrite rule in your .htaccess file to remove the variables from the URL to your Membership Options page. You can Google how to do the mod_rewrite rules.

I hope that helps. :)

Elizabeth said:
Warning: Cannot modify header information – headers already sent by (output started at /nfs/c04/h01/mnt/62642/domains/laschoolreport.com/html/wp-content/mu-plugins/s2hacks.php:1)

Make sure you don’t have a space or line break before the opening PHP tag. The [hilite code]

Ah ok, didn’t know that.

I don’t know when/if s2Member will support it, but I’ll forward your request to Jason. :)

You say “get the date from that”. It means that the date of a specific transaction for a specific member IS stored somewhere? (any idea where?)

I meant getting it from the ccap, if you name them with the date in them. So if the ccap is [hilite mono]w201202[/hilite] (Feb ’12), you’d have to get the date from that string using one of the string PHP functions, probably substr. http://php.net/substr

I’m not sure what your code should be like, it’d have to be worked out for your needs. I’m afraid I can’t develop this customization for you, so if you really need it, you could post the job in jobs.wordpress.net.

Hi Kimberley.

Yeah, although the registration is free, the pro-form is part of PayPal’s pro-forms, so it does warn if the PayPal integration is not configured. If you won’t get payments, just enter fake information in the fields so the warning goes away and you can use the free registration pro-form.

I hope that helps. :)