Cristián Lávaque

I’m not familiar with that variable, but you can, instead of using the shortcode for the button, use the HTML that the button shortcode generator outputs, and add your hidden input there for it. Remember that the HTML includes some PHP, so you’ll need a PHP execution plugin and use the text editor (not the visual editor) for your WordPress page.

Of course, they shouldn’t be shared here without editing out private info, and they can be quite extensive anyway. The way we review logs is having the site info sent to us so we can login there to access the logs.

If logging wasn’t enabled when the problem transactions happened, then they would not have been logged. Make sure you have log entries for the transactions you want us to take a look at.

You can submit the site info using the secure contact form. s2Member® » Private Contact Form

Please leave me a reply here after you sent it, and also tell me what transactions to look for (e.g. the person’s name, subscr. ID). Thanks!

You could do something like this:

Create this dir/file: /wp-content/mu-plugins/s2-hacks.php
See: Knowledge Base » Hacking s2Member® Via Hooks/Filters

[hilite pre_code]
Please click this link to login.';
}
return $translated;
}
[/hilite]

Yeah, odd, migrating the database would normally work if you update the domain name for the WP settings like you said.

I’m glad you sorted it out with the s2Member settings export/import tool. Thanks for the update.

This is what Jason replied:

I suggest doing this client-side with the help of jQuery. The description in a Pro Form is in an HTML tag you can reference via jQuery, analyze and then modify however you like. s2Member does not support HTML in the desc=”” attribute.

var $div  = jQuery('div.s2member-pro-paypal-form-description-div'), html = $div.html();
html = html.replace('$9.99', '<strong>$9.99</strong>');
$div.html(html);

Jason says that the limit was raised to 365 for days, so he’ll update the generator’s limit, but you can already use the 10 days editing your shortcode manually. The one in your post will work without an error for the 10 days trial.

It sounds like a problem on PayPal’s side. If you had everything working fine for so long and you now have that issue with the message saying “We are sorry, we are experiencing temporary difficulties. Please try again later.” it seems like a temporary issue on their end. Check with them to find out what’s going on.

You can also enable logging to gather more info until it’s solved. [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration[/hilite]

If you sell something for lifetime access, no EOT time will be set, so no demotion will happen. The masterclass can have it’s EOT and it won’t interfere with the seasons without EOT.

To drip the seasons over the months, see: [hilite path]Dashboard -› s2Member® -› API / Scripting -› Content Dripping[/hilite]

If you set up 6 payments for the season, though, the only way is with the [hilite mono]rrt[/hilite] attribute, which lets you set the number of payments for the subscription, but at the end of the end of the subscription an EOT time would be set. See: [hilite path]Dashboard -› s2Member® -› PayPal® Buttons -› Shortcode Attributes -> rrt[/hilite]

Since you need the EOT engine active so it demotes the Masterclass at the end, it’d be a problem. You’d need to monitor the seasons so that after the last payment, when the EOT time is set, you remove that EOT time. Or disable the EOT engine and you set EOT times manually for the Masterclass.

Or, disable the EOT engine and remove access to the masterclass using conditionals similar to dripping the content, only you remove access instead of giving it after a certain time.

Or sell the Masterclass as a specific post/page access/restriction, then the access link would have its own expiration, independent of the EOT engine, which would allow you to disable the EOT engine for the seasons. See: Video » s2Member (Specific Posts/Pages)

What Bruce is saying that you’d require a customization to have that feature you asked about, and pointed you to a couple of resources that will help achieve it. If you don’t know how to code it yourself, you can hire a freelancer to do it for you instead, just post the job in a site like jobs.wordpress.net, odesk.com or elance.com.

No, the URL I wrote above for the thank-you was /thank-you/ not /thanks/ because I was basing it on the URL you showed me before, just fixed the format. If it’s /thanks/, then the thank-you URL for your product 2 would be:

http://how2gainmusclefast.com/?s2member_pro_clickbank_return=1&s2member_pro_clickbank_return_success=http%3A%2F%2Fhow2gainmusclefast.com%2Fthanks%2F

The first thing you should do, if you haven’t already, is enable logging so you can then review the logs looking for the transactions that didn’t add the access to the profile, so we see if there are any errors mentioned for them. [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration[/hilite]

No, you being logged in as the administrator would not affect anybody else’s purchase. I’m guessing Bruce didn’t understand your question and thought it was a test purchase you made while logged in to your admin account.

If your customers are getting that message in the transaction log entries, then it’s likely that you’re using a button that was generated while you were logged in as the admin, then you copied the HTML and used that instead of keep using the shortcode for it. Could this be the case?

If that’s not it, please show us the shortcode you’re usign for the form/button your customer used to make the payment.