Raam Dev

Hi Will,

I have sent Jason a message to see if he has any further details on this. Thank you for your patience.

Hi Simon,

Unfortunately it’s going to be easier to edit the custom fields from within s2Member; the database tables are not designed in such a way that would make the process any easier. (Also, if you didn’t assign any custom classes to them in the first place, there wouldn’t be anything to “search” for to replace.)

Hi Daniel,

I think what Cristian is suggesting is that you add PHP code directly to the page where you display the user profile. From there, you can use the Advanced PHP Conditionals (Dashboard -› s2Member® -› API / Scripting -› Advanced PHP Conditionals) to check the level of the current user and then display the necessary HTML.

You could even store the iFrame information in a custom profile field and then extract that with PHP and use it when outputting the necessary HTML.

However, looking at your site, it appears that you’re using BuddyPress, which means the profile pages are generated automatically by BuddyPress. In that case, you’ll need to dig into the BuddyPress code and figure out how to modify that.

Hi Laurent,

For a Pro-Form example, please see this thread:
http://www.s2member.com/forums/topic/make-username-field-optional-and-hide-it/#post-7797

Hello,

It sounds like you’ll want to use S2MEMBER_CURRENT_USER_PAID_REGISTRATION_TIME:

This will always be an (int); in the form of a Unix timestamp. However, this will be 0 if they’re not logged in; or if they’ve never paid you at all ( i.e. if they’re still a Free Subscriber ). This holds the recorded time at which the Member originally registered their Username (or upgraded for) any type of “paid” access to your site. This value is preserved for the lifetime of their account, even if they upgrade, and even if they’re demoted at some point. Once this value is recorded, it never changes under any circumstance. This is useful if you want to drip content over an extended period of time, based on how long someone has been a “paying” Member (period); regardless of their original or existing Membership Level.

You can see examples of its usage at Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants.

That will really be up to SagePay. You may want to check their website.

Hi Sherri,

You can use a Free Registration form (Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms) and limit the access to a specific timeframe. Please see the note in the inline documentation:

[You can] limit this access to a certain timeframe with tp=”30″ tt=”D” ( i.e. 30 Days ).

When someone uses that form to signup, their account will expire after the given amount of time and they will be demoted or deleted depending on what you’ve configured for the Automatic EOT Behavior (see Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior).

It is something we will consider for a future version of s2Member, but at this time there are no details on what features will or will not be included in the next version.

Ric,

The email that gets sent to Aweber includes the subscribers address (so that Aweber knows which email address should be subscribed to the list), but that email doesn’t come from the subscriber; it comes from WordPress/s2Member. (see below). That means it will be sent using whatever from address WordPress/s2Member is configured with and it will use the SMTP settings defined (if none are defined, which is the default, WordPress will attempt to use the mail transfer agent on the web server to send the email and sometimes that causes problems).

• This reply was modified 4 years, 9 months ago by  Raam Dev.

Could please you try the following steps:

– Make sure Deactivation Safeguards are enabled (Dashboard -› s2Member® -› General Options -› Deactivation Safeguards) and then disable and re-enable the s2Member plugin
– Clear your browser cache
– Restart all open browsers
– Try generating the button again

Hello,

Are you running the latest versions of s2Member and WordPress?

Also, to help with further debugging, please enable logging (Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details -› Logging), conduct another test, and then share the details for that transaction from the log files in wp-content/plugins/s2member-logs/ (be sure to X-out any private information).