Community Support Forums

Hi,

I am running my test site with s2members installed on my local machine (i.e. localhost); I tried to generate button code through the button generator, for both level 1 access and for upgrading to level 1. When clicking on the "generate button code" button, the new shortcode shows up ok, but the textarea for the code snippet becomes empty. I am also in Paypal Sandbox mode. Did I miss to give some input somewhere?

Thanks, best regards,
Steffen

Hi Steffen.

Try adding this line to your /wp-config.php file:

Code: Select all

define('LOCALHOST', true); 

s2Member has a special routine, which we refer to as the Systematics Routine. It sees your IP address is the same as the server's IP; which is sometimes an issue on a WAMP/MAMP installation.

It's fine so long as your domain is http://localhost/. However, if it's something other than that, you'll need to add that line in your /wp-config.phpfile so s2Member realizes it's running on a localhost installation.

Let me know if that helps.

I added that line and restarted WAMP but it still does the same thing, once I click on the generate button all markup disappears.

Could you share a screenshot?

I wonder if it's a JavaScript conflict with another plugin's. Have you looked at your Firefox' Error Console? Try disabling other plugins one by one and see if one solves that problem.

It gets stranger now. When using Firefox to check on JS errors, the button markup was generated properly, no errors were shown. After that I tried again to do the same thing with Safari and IE9, and each time the button markup disappears

I restarted my computer and WAMP, and checked again on all my browsers; conclusion: button markup code generation works ok for Firefox 4 and Chrome 11, but markup simply disappears from the textarea when doing the same with IE9 and Safari.
One of those mysteries I think. Anyway, I can live with 2 browsers that do it

LOL yeah, I wonder why a problem may come from an Internet Explorer browser, mystery.

Well, I'm still guessing that it may be a JS conflict with something else. If you're very curious you could try disabling other plugins to find what is causing it.

I'm glad you have two browsers that'll work properly with it, though. Thanks for reporting back!