Cristián Lávaque

There isn’t an unencoded version. To change a var, like the level the user gets, you do it when generating the URL. E.g.

[hilite pre_code]
$link = c_ws_plugin__s2member_register_access::register_link_gen("none", "-", $_SERVER["HTTP_HOST"], $register_level, false);
[/hilite]

http://www.s2member.com/codex/stable/s2member/registrations/c_ws_plugin__s2member_register_access/#src_doc_register_link_gen%28%29

Rachel, this video may also be of interest to you: Video » s2Member (Client Portals?)

Thanks for your help, Randy! :)

Thanks for letting us know, Core! Looking forward to your update. :)

Hi Randy.

This article may be helpful: Knowledge Base » Changing Roles/Capabilities via PHP

The s2Member capabilities are independent of roles, and are prefixed with [hilite mono]access_s2member_ccap_[/hilite].

You can use the User Role Editor to look at the roles and capabilities and familiarize yourself with what you’ll be working with. http://wordpress.org/extend/plugins/user-role-editor/

If you go to the Users menu, you’ll see the User Role Editor’s entry at the bottom. If you go to the Users list, for each user you’ll have a new link to edit his capabilities.

I hope that helps!

Great! Thanks for the update.

Sorry I had forgotten about that thread. I’ll try to remember it next time someone asks about WP Security. :)

lol

Well, you can pick the files for one of the other gateways (e.g. ClickBank) and see how it’s done there, changing the code to work with your gateway.

It is advanced, though, so you may want to get help from a developer. You can try jobs.wordpress.net.

No, I’m not sure I know what thread you are referring to. But the documentation there tells you what you need to know, although it’s not a tutorial.

No problem. :)

Hi Giancarlo.

Thanks for the kudos! :)

There’s a hack to login automatically after registration: http://www.s2member.com/forums/topic/auto-login-after-successful-payment/#post-16660

I hope that helps.

This is part of a conversation I had with Jason some months ago regarding JavaScript conflicts.

Cristián: I still don’t understand how the JS conflicts work… If the library is the same in both plugins, why is there a conflict? Same var names?

Jason Caldwell: Well, I call it a conflict. Sometimes it’s a conflict in jQuery because of a bad plugin, which attempts to load jQuery on it’s own, instead of doing it the WP way. Or sometimes, it just a bad plugin that causes a JavaScript error, which may result in all JavaScript failing (the nature of JavaScript). Not really a “conflict” in that case, really an error due to a bad plugin/theme.

Jason Caldwell: I’ve also see some conflicts between frameworks. That’s rare, but there are some plugins that use the ProtoType framework, and combined with another framework like MooTools, there is a possibility for a conflict to arise. Rare though, and it’s usually attributed to the way their loaded (i.e. by a bad plugin/theme).

Cristián: Does WP load JQuery already? If so, why do plugins load it too?

Jason Caldwell: Yea, WP already loads it. But some plugin authors don’t know that, or they just hard code it into their plugin not realizing that. Other times they’ll try to include a dependency on jQuery, but they name it wrong, and WordPress gets confused.

Cristián: Does s2Member load it again or uses WP’s?

Jason Caldwell: Hmm, not really, because in the Dashboard, it’s already loaded by WordPress. s2Member enques scripts that is uses, which rely on jQuery being present. In the call to wp_enqueue_script(), s2Member will list jQuery as a dependency, which forces WP to load it, though it’s already loaded in the Dashboard anyway. That’s the proper way to handle it.

On the front-end of a site, s2Member will load jQuery if it’s not already loaded, but again, using the same technique. A call to wp_enqueue_script() with a dependency on jQuery forces WP to load jQuery. If 10 plugins all do it this way (i.e. the right way), WordPress loads jQuery in the proper order and only one time.

Cristián: Ah, got it. I understand WP has a QC team, don’t they check this?

Jason Caldwell: Not in my experience. They look mostly for security issues and really bad code. They usually don’t catch minute details like this.

Cristián: I see. Well, they do look at how the db is used, iirc.

Cristián: I see, but these details do cause trouble for the users. Maybe it’d be good to write an article about JS conflicts as you explained above and post it in the forums, and then show it to the QC guys for consideration to include in their quality checklist.

Jason Caldwell: Yea, that’s a good idea. On the WP side though, they’re aware of this problem, and that’s why they created the wp_enqueue_script() wp_enqueue_style() functions. Although, I wish this were more prominent in this article: http://codex.wordpress.org/Writing_a_Plugin#Plugin_Development_Suggestions

It is mentioned, but it’s all the way at the bottom:

Try not to echo [hilite code]