https://static.nrelate.com/common_wp/0.03.0/nrelate-panels-common.min.css
Statistics: Posted by Jason Caldwell — September 9th, 2011, 6:15 pm
Statistics: Posted by dskallman — September 7th, 2011, 8:39 am
Statistics: Posted by Cristián Lávaque — September 4th, 2011, 11:57 pm
Statistics: Posted by dskallman — September 4th, 2011, 8:52 am
Statistics: Posted by Jason Caldwell — August 31st, 2011, 12:44 pm
Statistics: Posted by dskallman — August 31st, 2011, 9:05 am
Statistics: Posted by Jason Caldwell — August 30th, 2011, 10:58 pm
Statistics: Posted by dskallman — August 30th, 2011, 7:48 pm
Statistics: Posted by Jason Caldwell — August 30th, 2011, 5:44 pm
# BEGIN MailPress
RewriteEngine on
RewriteRule ^mail/analytics/([l|o])-([0-9]+)-([h|p])-([0-9a-zA-Z]+).html wp-content/plugins/mailpress/mp-includes/action.php?tg=$1&mm=$2&co=$3&us=$4 [L]
# END MailPress
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
Statistics: Posted by dskallman — August 30th, 2011, 2:49 pm
Statistics: Posted by Jason Caldwell — August 30th, 2011, 2:21 pm
Cristián wrote:
If I try to load https://ynpn.org/sfba/join I get redirected to http://ynpn.org/sfba/sfba/join which gives a 404
Statistics: Posted by Jason Caldwell — August 30th, 2011, 2:19 pm
Statistics: Posted by dskallman — August 28th, 2011, 4:35 pm
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
Statistics: Posted by Cristián Lávaque — August 27th, 2011, 1:00 am
Statistics: Posted by dskallman — August 25th, 2011, 6:34 pm
Statistics: Posted by dskallman — August 25th, 2011, 7:29 am
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.
Statistics: Posted by Cristián Lávaque — August 25th, 2011, 3:00 am
<?php
if(isset($_GET["s2-ssl"]))
$_SERVER["HTTPS"] = "on";
Statistics: Posted by dskallman — August 24th, 2011, 7:13 pm