Title: jonbeddoes's Replies | WordPress.org

---

# jonbeddoes

  [  ](https://wordpress.org/support/users/jonbeddoes/)

 *   [Profile](https://wordpress.org/support/users/jonbeddoes/)
 *   [Topics Started](https://wordpress.org/support/users/jonbeddoes/topics/)
 *   [Replies Created](https://wordpress.org/support/users/jonbeddoes/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/jonbeddoes/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/jonbeddoes/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/jonbeddoes/engagements/)
 *   [Favorites](https://wordpress.org/support/users/jonbeddoes/favorites/)

 Search replies:

## Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] domainname.ch/?wordfence_logHuman=1&hid not in HTTPS](https://wordpress.org/support/topic/domainnamechwordfence_loghuman1hid-not-in-https/)
 *  [jonbeddoes](https://wordpress.org/support/users/jonbeddoes/)
 * (@jonbeddoes)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/domainnamechwordfence_loghuman1hid-not-in-https/#post-6575896)
 * I am having the same problem with this on one of my sites. The site is HTTP but
   moves to HTTPS on the WooCommerce pages. I don’t really by the explanation that
   it can’t be avoided; any script can detect that the current page URL is HTTPS
   so there must be a way. In the meantime I will disable the “Live Traffic View”
   as suggested.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress MU Domain Mapping] Minor: get_current_site_name() Deprecated in 3.9](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/)
 *  [jonbeddoes](https://wordpress.org/support/users/jonbeddoes/)
 * (@jonbeddoes)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/#post-4815397)
 * @RonRennick – bit confused by your response;
    I wrote code to mimic the same 
   functionality as was there before, but your suggestion to remove the code implies
   it has no purpose and is never executed?
 * If that is the case, what change(a) did you make in the development version instead
   if it’s not my change and not deleting the code fragment? 🙂
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress MU Domain Mapping] Minor: get_current_site_name() Deprecated in 3.9](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/)
 *  [jonbeddoes](https://wordpress.org/support/users/jonbeddoes/)
 * (@jonbeddoes)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/#post-4815391)
 * [@khromov](https://wordpress.org/support/users/khromov/) I had that warning issue
   too but that change fixes it indeed. @RonRennick good to know that the official
   version fixes that too.
 * @RonRennick Out of interest, are you happy with the proposed fix I suggested 
   above for the other warning that spawned after the 3.9 update?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress MU Domain Mapping] Minor: get_current_site_name() Deprecated in 3.9](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/)
 *  [jonbeddoes](https://wordpress.org/support/users/jonbeddoes/)
 * (@jonbeddoes)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/#post-4815388)
 * Hi khromov,
 * I am sorry my solution didn’t help you. I must admit I didn’t consider the outcome
   if the function was never called. In my case I was simply trying to modify the
   sunrise.php file to keep it’s behavior the same as it was before. Because the
   get_current_site_name() function was deprecated I essentially achieve the same
   thing with those two lines. Once I made this update my warnings went away.
 * Are you running multiple sites through the domain mapping plugin? Do you have
   any warnings still? If not then you should probably assume everything is working
   as expected 🙂
 * JB
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress MU Domain Mapping] sunrise.php – get_current_site_name deprecated since WP v3.9](https://wordpress.org/support/topic/sunrisephp-get_current_site_name-deprecated-since-wp-v39/)
 *  [jonbeddoes](https://wordpress.org/support/users/jonbeddoes/)
 * (@jonbeddoes)
 * [11 years, 12 months ago](https://wordpress.org/support/topic/sunrisephp-get_current_site_name-deprecated-since-wp-v39/#post-4856946)
 * Here is a code fix for this issue. Update the reference at the end of sunrise.
   php:
 *     ```
       if( function_exists( 'get_current_site' ) )
       {
       	$current_site_obj = get_current_site( $current_site );
       	$current_site = $current_site_obj->site_name;
       }
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress MU Domain Mapping] Minor: get_current_site_name() Deprecated in 3.9](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/)
 *  [jonbeddoes](https://wordpress.org/support/users/jonbeddoes/)
 * (@jonbeddoes)
 * [11 years, 12 months ago](https://wordpress.org/support/topic/minor-get_current_site_name-deprecated-in-39/#post-4815379)
 * Here is a code fix for this issue. Update the reference at the end of sunrise.
   php:
 *     ```
       if( function_exists( 'get_current_site' ) )
       {
       	$current_site_obj = get_current_site( $current_site );
       	$current_site = $current_site_obj->site_name;
       }
       ```
   

Viewing 6 replies - 1 through 6 (of 6 total)