Topic RSS
2:11 pm
Hi,
The login and admin section of my WPMU-blog both use an SSL connection.
I can only modify/safe the settings of SPF if I'm NOT using SSL (~stop forcing the connection to run over https). Obviously I could just take SSL off, make the changes and then activate SSL again, but I want to avoid doing that.
No problem ACCESSING these settings using SSL, but when I tried to CHANGE them, well… nothing happens.
Any ideas would be greatly appreciated.
WPMU 2.8.1
SPF 4.1.2
We do know about this but am having a problem tracking it down. We make the correct calls to WP that is supposed to return either 'http' or 'https' but for some reason it seems to fail. We have an open ticket and it will get fixed just as soon as we trace it.
testing isn't easy of course.
Not sure what else I can say at the moment.
Are you by any chance able to tell me if the version of MU you are using includes the WP function 'site_url()' ?
In standard wordpress it s in the file link-template.php…
This function should return the site url with the correct http/https and it is what we use to determine ALL SPF URLs…
10:45 am
Yellow Swordfish said:
Are you by any chance able to tell me if the version of MU you are using includes the WP function 'site_url()' ?
In standard wordpress it s in the file link-template.php…
This function should return the site url with the correct http/https and it is what we use to determine ALL SPF URLs…
Hi,
Thanks for your reply…
I don't know much php but I guess my version of WP uses the WP function 'site_url()' .
I found the file you mentioned in the wp-includes subfolder.
This is the code:
/**
* Retrieve the site url.
*
* Returns the 'site_url' option with the appropriate protocol, 'https' if
* is_ssl() and 'http' otherwise. If $scheme is 'http' or 'https', is_ssl() is
* overridden.
*
* @package WordPress
* @since 2.6.0
*
* @param string $path Optional. Path relative to the site url.
* @param string $scheme Optional. Scheme to give the site url context. Currently 'http','https', 'login', 'login_post', or 'admin'.
* @return string Site url link with optional path appended.
*/
function site_url($path = '', $scheme = null) {
// should the list of allowed schemes be maintained elsewhere?
$orig_scheme = $scheme;
if ( !in_array($scheme, array('http', 'https')) ) {
if ( ( 'login_post' == $scheme || 'rpc' == $scheme ) && ( force_ssl_login() || force_ssl_admin() ) )
$scheme = 'https';
elseif ( ('login' == $scheme) && ( force_ssl_admin() ) )
$scheme = 'https';
elseif ( ('admin' == $scheme) && force_ssl_admin() )
$scheme = 'https';
else
$scheme = ( is_ssl() ? 'https' : 'http' );
}
$url = str_replace( 'http://', "{$scheme}://", get_option('siteurl') );
if ( !empty($path) && is_string($path) && strpos($path, '..') === false )
$url .= '/' . ltrim($path, '/');
return apply_filters('site_url', $url, $path, $orig_scheme);
}
And that is the function SPF uses to create it's URL's which is why I am puzzled yours are not being created as https even though they should be. When I get home from this short trip I will try and look deeper into that code.
I know this is an old post, but I'm hoping there's an anser to this problem somewhere as I'm having the same problem in WP 2.9.2 with SPF Version: 4.1.3 (Build: 2510 / Release).
Our blog resides on our eCommerce server so it has to adhere to the same security standards which means enabling SSL. Once it's enabled, the Admin panel for the forum no longer works and whenever I try to login from the forum, it redirects out of SPF to the Wordpress login screen. I'm guessing those are 2 spearate issues, but I thought I'd through it out there.
Any help would be appreciated. Or maybe I just need to upgrade SPF?
Anthony
we had one other user who had a similar problem and never did figure out what was going on and he never came back…
I know we have users that have used ssl in the admin before and it worked… possible that something has changed in WP since they love to do that to us! but would expect more cries if it was a general issue…
is there any more info you can provide? would be nice to upgrade to see if it matters, but we havent done anything outright for it…
Thanks for getting back with me. I just upgraded to 4.2.2 because we got a report that SPF might allow a MySQL injection hack and I don't have a clue about any of that. So I figured before I go spouting off about anything I'd get up to the latest version and have McAfee re-run their scan.
I'll try the SSL again on the new version when I get a chance and I'll post back if I still have issues. I'll start a new thread though since it's a defferent version.
Anthony
Most Users Ever Online: 444
Currently Online:
58 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
-Radio-: 1251
Lee H: 606
Luffer: 535
Conrad_Farlow: 502
jim: 478
neon: 263
ovizii: 240
Tal: 240
Member Stats:
Guest Posters: 2626
Members: 7363
Moderators: 1
Admins: 2
Forum Stats:
Groups: 5
Forums: 16
Topics: 10898
Posts: 79583
Newest Members: Rick Thomas, joelrob, ndc, MacBravO, irlandes1, triphop, betokan, Jonathan Yovani Muñoz, somosguatemala, ahcreate
Moderators: Brandon C (162)
Administrators: Yellow Swordfish (22240), Mr Papa (23688)
Log In
Register
Home
Add Reply
Add Topic
Quote
Offline



Visit 
Privacy Policy



