Sleneau

Here’s the refactor. It simply takes the name of the fee you want to delete as the argument, and removes it from the Woocommerce session. Drop it into your functions.php, and then call it whenever you want to delete a fee.

It’d probably be best employed in an action hook, though.

function delete_fee ($fee_name) {
$fees = WC()->cart->get_fees;
$newfees = array();

foreach ($fees as $fee) {
if ($fee->name == $fee_name) {} //Don't add Shipping Insurance
else {$newfees[] = $fee;}
}

WC()->session->set('fees',$newfees);
}

One other thing that needs to be mentioned–WordPress HTTPS has an option under it’s settings labeled, “SSL Host”, into which you put the domain name that you have your SSL certificate tied to. Not surprisingly, I still had my old domain name in that field. Because of that, the plugin kept trying to apply SSL form a certificate that didn’t exist anymore. Needless to say, this caused a number of problems.

Man, this has really been an onion of a problem–stinky and multi-layered.

I discovered that this error message is found in wp-login.php in the root directory of wordpress. Apparently, it shows up when you are being showed as having been logged out (for whatever reason).

I am still trying to work my way through the whys of how the user gets logged out, but I haven’t had any luck so far.

Ok, my site is still doing the annoying you-have-to-login-every-fifteen-seconds thing. What on earth is causing this?

Ok, new developments. No, I haven’t figured out why WordPress is swapping one URL out for another yet. I still suspect it has something to do with the database, but my searches haven’t proven very fruitful thus far.

What I HAVE figured out is how to make my pages appear. Evidently, there has been a major issue at my hosting provider concerning SSL certificates. See, I swapped domain names, and didn’t have an SSL certificate that covered subdomains. Because there isn’t any option to upgrade or transfer SSL certificates, I wound up deleting one certificate, and purchasing a different one for my new domain. That, apparently, has caused mass confusion on bluehost’s end, and they have instructed me to contact their Senior technicians who have actually programmed their system to get an answer.

While that gets handled, I don’t have SSL on my site. Which isn’t a happy situation. But it explains why so many of my pages are now white screens of death. See, the culprit in this case is WordPress HTTPS, which has an option to force SSL on a page that I use all over the place. This is what is causing the pages to disappear.

Now if only I understood the thing where the domain names were getting rewritten.