jonbeddoes
Forum Replies Created
-
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.
@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? 🙂
@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?
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
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; }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; }