Statistics: Posted by dvpro — November 17th, 2011, 11:11 am

If you're using s2Member's Pro Forms, then yes. In order to comply with PayPal®, Authorize.Net® and PCI Compliance policies, as set forth by major credit card companies; you will need to host all of your Pro Forms on an SSL enabled site. Please check with your hosting provider to ask about obtaining an SSL certificate for your domain. Please note... when you create Pro Forms using the Form Generators provided by s2Member; you'll be supplied with WordPress® Shortcodes, which you'll insert into Posts/Pages of your choosing. These special Posts/Pages will need to be displayed in SSL mode, using links that start with ( https:// ). In other words, when you link to these Posts/Pages, you'll need to make sure your links start with https://.

You can skip the SSL certificate during Development/Sandbox testing. SSL is not required until you officially go live. Once you're live, you can add the Custom Field s2member_force_ssl -> yes to any Post/Page. s2Member will buffer output on those special Posts/Pages, converting everything over to https:// for you automatically, and forcing those specific Posts/Pages to be viewed over a secure SSL connection; so long as your server supports the https protocol. This will help you eliminate the dreaded Secure/Insecure errors in Internet Explorer®. If your server runs SSL over a special port number, or your server requires the port number to actually be in the URL ( i.e. HOST:port ), you can set s2member_force_ssl -> 443; or to whatever port you need.

Yes, WordPress® is indeed compatible with SSL enabled ( https:// ). However, not all themes/plugins are designed to behave properly with SSL enabled. For instance, some WordPress® themes/plugins embed links to images, scripts, and/or style sheets; all starting with http://, instead of https://, ( or just //: - which is cross-protocol compatible ). For this reason, you should be very careful when choosing a WordPress® theme/plugin to use with s2Member Pro. Otherwise, your visitors could see the famous "Secure/Insecure" warnings in Internet Explorer® browsers.

A good web developer can fix this minor issue with ease,
but novice site owners are advised to get help from a professional.

*Tip: All themes available at PriMoThemes.com include full support for SSL enabled Posts/Pages. Also, with s2Member installed, you can add the Custom Field s2member_force_ssl -> yes to any Post/Page. s2Member will buffer output on those special Posts/Pages, converting everything over to https:// for you automatically, and forcing those specific Posts/Pages to be viewed over a secure SSL connection; so long as your server supports the https protocol.

Statistics: Posted by Jason Caldwell — November 17th, 2011, 10:54 am

Statistics: Posted by dvpro — November 15th, 2011, 6:10 pm

dvpro wrote:
This is still a problem with Event Espresso 3.1. Has anyone at EE responded?

Statistics: Posted by Jason Caldwell — November 15th, 2011, 5:44 pm

Statistics: Posted by Jason Caldwell — July 22nd, 2011, 7:10 pm

Statistics: Posted by vonralls — July 21st, 2011, 8:29 pm

Statistics: Posted by vonralls — July 21st, 2011, 8:08 pm

Statistics: Posted by Jason Caldwell — July 21st, 2011, 5:15 pm

Statistics: Posted by vonralls — July 21st, 2011, 4:29 pm

Statistics: Posted by Jason Caldwell — July 21st, 2011, 4:22 pm

Code:


# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress




Statistics: Posted by vonralls — July 21st, 2011, 4:06 pm

Statistics: Posted by Jason Caldwell — July 21st, 2011, 4:03 pm

Code:

<?php
if(isset($_GET["s2-ssl"]))
    $_SERVER["HTTPS"] = "on"; 

Statistics: Posted by Jason Caldwell — July 21st, 2011, 3:18 pm

Code:

<?php

add_action('ws_plugin__s2member_config_hooks_loaded', 'https_plugin_dir_url');

function https_plugin_dir_url() {
    if (isset($_GET['s2-ssl']))
        $GLOBALS['WS_PLUGIN__']['s2member']['c']['dir_url'] = strtr($GLOBALS['WS_PLUGIN__']['s2member']['c']['dir_url'], array('http:' => 'https:'));
}

?>

Statistics: Posted by Cristián Lávaque — July 14th, 2011, 8:24 pm

Statistics: Posted by bethperkins — July 14th, 2011, 1:17 am

Code:

<?php
if(isset($_GET["s2-ssl"]))
    $_SERVER["HTTPS"] = "on"; 

I don’t think you understood my SSL problem. I can’t use the “force SSL” option because the customers hosting company is Network Solutions.

Code:

<?php
if(isset($_GET["s2-ssl"]))
    $_SERVER["HTTPS"] = "on";  

Statistics: Posted by Jason Caldwell — July 14th, 2011, 12:46 am

Statistics: Posted by bethperkins — July 14th, 2011, 12:36 am

Code:

<?php
if(isset($_GET["s2-ssl"]))
    $_SERVER["HTTPS"] = "on"; 

Statistics: Posted by Jason Caldwell — July 13th, 2011, 8:50 pm

Statistics: Posted by bethperkins — July 11th, 2011, 2:45 pm