Cristián Lávaque

Very cool, Kenny, thanks for sharing that! :)

Hi Johnny.

You could try the free registration form, it lets you set an access and EOT time. So the person could register at Level 1 and be demoted after a day to Level 0.

[hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms[/hilite]
[hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior[/hilite]

I hope that helps. :)

The functions are documented there, and they are also linked to the code so you can inspect it closer if you need to. ;)

Ah, got ya. Yeah, that’s in the usermeta table.

A simple way to migrate that would be, if you have s2Member Pro in both blogs, to export the users in one and then import/update them in the other. [hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member[/hilite]

I hope that helps. :)

Thanks Jyotisha.

It looks like a parsing problem in your WordPress. It could be cause by the theme or one of the other plugins.

Could you test it changing to the default theme first and refreshing the page to see if that fixes it?

If not, then deactivate other plugins one by one and refresh the page after each to see if the problem’s gone.

Once you spot what’s causing it, it’ll be easier to find a solution.

I hope that helps. :)

Hi Waide.

This post by Jason will help you get an idea to query the custom fields from the database, but you’ll need to customize your directory plugin to use this and display the info. http://www.primothemes.com/forums/viewtopic.php?t=15658&p=53767#p48878

I hope it helps.

Oh, the Options Export, I thought you were talking about the Users one.

I just downloaded an export file and then imported it back in, and it worked fine.

Operation complete. Options imported.

Could you try once more? Export the file and the import it right then. Please let me know if that works.

I see. From the replacement codes you mentioned, I assumed the Spec. Post Tracking.

I suggest that you watch this video, it may be helpful for what you want:

I hope it helps. :)

Hi Eddie.

If you go back to the default theme, does the problem go away? If so, then it is the theme. You can tell the developer to look into it and improve it. Or you can try doing it yourself if you know how to do it.

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]