Just updated to Version 2.5.2 and now can't login to admin area

So you know, I’ve also had troubles with logins using IE since updating to the new WooCommerce. I can login fine with Chrome but it just reloads the My-Account page when I try to login with IE. I’ve tried the code above just in case but no love.

Do you folks have caching rules in things like .htaccess perhaps? Not sure if that would affect it.

Do you folks have caching rules in things like .htaccess perhaps? Not sure if that would affect it.

@mike, yes I do use a caching plugin (W3TC Total Cache). There are a bunch of rules in the .htaccess file, if you want to see them all I can email them to you if you want. But most of it is standard settings of the plugin, you can see the plugin here: https://www.ads-software.com/plugins/w3-total-cache/

But just to reiterate, everything is working fine now in Chrome *after* I used the code in the functions.php file that you suggested.

However, it is *not* working in IE still.

In the plugin, it allows you to flush the cache which typically works to flush all settings. But it doesn’t seem to have any effect on IE with this issue.

Do you want me to try to deactivate the plugin and try logging in again using IE? Let me know, thanks.

Yes, but make sure you clear the custom caching rules from .htaccess too after doing so.

We have the same problem. The moment the that WooCommerce was updated, we got a white screen. Therefore we can’t run the WC update which creates the new sessions table.

So it appears we’re caught in limbo – to log in we need the sessions data in the new table, but we can’t log in to run the update that creates that table… this is if I understand correctly how the sessions are now handled in WooCommerce.

Switching on debug, here is the error on the WSOD:

WordPress database error: [Table 'my_database.wp_woocommerce_sessions' doesn't exist]
SELECT session_value FROM wp_woocommerce_sessions WHERE session_key = '693ae3...b85a27'

So while logged in as admin, doing the update pulls the rug from under its session, and it cannot create that table, because it no longer has a session.

This is what I did to create the sessions table to get the site back online:

CREATE TABLE IF NOT EXISTS wp_woocommerce_sessions (
  session_id bigint(20) NOT NULL AUTO_INCREMENT,
  session_key char(32) NOT NULL,
  session_value longtext NOT NULL,
  session_expiry bigint(20) NOT NULL,
  PRIMARY KEY (session_key),
  UNIQUE KEY session_id (session_id)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 ;

NOTE: I got this from a thread here which is two weeks old, so MAY NOT be the final table structure. It does work for me though.

The ENGINE and CHARSET are the default for my database, and I just made sure it was the same as the other WooCommerce tables. Your milage may vary.

I also needed to put this hack into the woocommerce-mailchimp-discount plugin:

if ( !function_exists('get_editable_roles') ) {
require_once( ABSPATH . '/wp-admin/includes/user.php' );
}
$roles = get_editable_roles();

The first three lines were added just in front of the forth line. I don’t know why, but I suspect WC 2.4 may have loaded that file early for its own reasons and woocommerce-mailchimp-discount just relied on that. I’m hoping for a patch for that plugin soon. The file FYI is:

wp-content/plugins/woocommerce-mailchimp-discount/includes/class-wc-settings-mailchimp-discount.php

I also expect there will be a patch release of WC that can be FTPed over the top of the existing one, that is able to handle the missing sessions table before it is created.

My problem may or may not be exactly what others are having. Just check whether the sessions table exists in the first instance. My symptoms were that the admin area immediately stopped working (WSOD) and the cart/basket pages also failed. Other pages that did not need a WC session carried on working fine.

Yes, but make sure you clear the custom caching rules from .htaccess too after doing so.

@mike, so I went ahead and deactivated the caching plugin. I confirmed that all the caching rules were removed from .htaccess. I then removed the code you had me place above add_filter( 'woocommerce_prevent_admin_access', '__return_false' ); and tried to login again in IE. The same behavior as before happened, where I could not login at all. Just go to login and it redirects back to the home page.

I went back and re-added the code add_filter( 'woocommerce_prevent_admin_access', '__return_false' ); and the same behavior in IE was experienced again. I can login with a regular user but NOT with an Admin user.

Final results seem to be that the caching plugin doesn’t appear to be effecting the anything.

What version of IE is it? I’ll have to have a colleague text as I’m on mac.

What version of IE is it? I’ll have to have a colleague text as I’m on mac.

I’m using IE-11