ariesbeck

@jreade and I were looking at this today and seem to have discovered the problem. For some reason when Super Cache is trying to write a new wp-cache-config.php it tries to create the new file in the same directory (wp-content) rather than creating it in the system registered temp directory. We have our site locked down so we don’t allow writing except in places its required. We allow writing to the actual caching directory as well as to the wp-cache-config.php file itself.

The fix is simple, change line 1072 from:

$tmp_file = dirname( $my_file ) . '/' . mt_rand() . '.php';

to:

$tmp_file = sys_get_temp_dir() . '/' . mt_rand() . '.php';

Aaron

Just wanted to add that we experienced the same issue. After upgrading our multi-site to 1.6.0 of Simple LDAP Login our preferences were cleared and all logins were failing.

Also, an upgrade of a non-multi-site installation occurred without issue.

Wanted to provide an update. I decided to do some digging on this issue this morning and discovered that the JavaScript console was reporting a syntax error on the checkout page. Turned out that our Avada theme was out of date and not compatible with the latest jQuery package that the newest WordPress upgraded to.

Check your browser for any JavaScript console errors to see if you are experiencing anything similar. I guess the token call is performed via JavaScript and its result is then passed to the backend (PHP) where it makes the “charges” call.

If you happen to be landing on this page and you are running Avada and are unable to update look in the main.js file for a line with contents similar to(mine was on line 2151):

jQuery('.fusion-navbar-nav a:not([href=#], .fusion-megamenu-widgets-container a, .search-link), .top-menu .menu a:not([href=#]), .mobile-nav-item a:not([href=#], .search-link), a.fusion-button:not([href=#]), a.fusion-one-page-text-link:not([href=#])').click(function() {

and add quotes surrounding the # symbol like this:

jQuery('.fusion-navbar-nav a:not([href="#"], .fusion-megamenu-widgets-container a, .search-link), .top-menu .menu a:not([href="#"]), .mobile-nav-item a:not([href="#"], .search-link), a.fusion-button:not([href="#"]), a.fusion-one-page-text-link:not([href="#"])').click(function() {

We are experiencing the same issue with this plugin, started around the same time as tmartinez posted his issue.

I did notice in the stripe panel that before yesterday they were seeing a call to POST /v1/tokens followed by a call to POST /v1/charges. Now it is no longer showing a call to /v1/tokens at all and is receiving a 400 error for /v1/charges.

Any ideas? Obviously management is not very happy with a site that cannot collect revenue ??