doconeill

Ah…I found the problem. MySQL 8 has a “sql_generate_invisible_primary_key” parameter…Azure’s MySQL service sets this to on by default. I needed to turn it off.

2.1.8 has completely broken my plugins control with a fatal error. I now need to manually remove w3-total-cache from multiple sites as I can no longer update any plugins.

FYI, I use ssh2 for updates.

Is anyone monitoring this? An update got pushed out, but these images are still missing.

I put 1.0 on my production sites yesterday via standard upgrade method – looks good so far. Response times look good.

So far so good…looks clean.

I edited afterwards, so you might not have seen it…do you want me to get the git version instead?

OK, that’s what I’ve checked out without any branch parameters…I’ll update that and get back to you this evening.

Wait, do you want me to get the git version now?

Sorry, I was working and couldn’t get to it yet.

I didn’t specify a branch when I checked it out, and I don’t use svn much – what branch specifically do you want me to check out?

OK, I was missing that it wanted to write a new file. Once I let it did, but it contains the same information, just declared differently.

I updated it one one of the sites to the latest code. Here is what it said…it appears it is checking the plugin’s own directory for the advanced-cache.php/writeability, instead of the wp-content directory:

WARNING: plugin settings are not yet saved for the site, please save settings!

Technical information: the configuration array is not present in the file /web/sitehome/wordpress/wp-content/plugins/wp-ffpc/wp-ffpc-config.php

WARNING: advanced cache configuration file is yet to be generated, please save settings!

Technical information: please check is location is writable: /web/sitehome/wordpress/wp-content/plugins/wp-ffpc/wp-ffpc-config.php

I make the directory writable and saved, and the messages went away, but it wrote the file where it was supposed to.

The 1.0 branch is working perfectly for me so far, aside from a few cosmetic things.

On the settings page, it always says that the settings haven’t been saved yet and that the config file hasn’t been written yet, and the “WARNING” for the invalidation method needs to update to match the options (which doesn’t say “all” any more).

I’ll let you know after if there are any issues.

I’ll give the svn tree a try tonight or this weekend.

The invalidation method is set to “full flush” (stored as “0” in the advanced-cache.php file.

Another data point – I did two edits to a couple posts on the third “normal” site, and the main page is not updating in the cache.

One further data point – it looks like editing an existing post clears the cache, but adding a new one doesn’t.

And this is what I got in the syslog:

Mar 14 22:16:58 sheen httpd: wp-ffpc: server 127.0.0.1:11211 added, persistent mode: 0; cache type:
Mar 14 22:17:05 sheen httpd: wp-ffpc: server 127.0.0.1:11211 added, persistent mode: 0; cache type:
Mar 14 22:17:06 sheen httpd: wp-ffpc: server 127.0.0.1:11211 added, persistent mode: 0; cache type:
Mar 14 22:17:12 sheen httpd: wp-ffpc: server 127.0.0.1:11211 added, persistent mode: 0; cache type:

I’ve looked at the code, and I’m looking at the line in wp-ffpc-common.php wp_ffpc_set(), where $exp gets set:

$exp = $wp_ffpc_config[‘user_logged_in’] ? $wp_ffpc_config[‘expire_member’] : $wp_ffpc_config[‘expire_visitor’];

Where do those wp_ffpc_config values get set? I see nothing anywhere else in the code with those strings. The only config value is called “expire”…but I may be misunderstanding the code.

I was never able to get nginx to use the cache directly. Since then I’ve had to abandon nginx due to a number of unrelated issues getting some sites to work, and have gone back to Apache. Still using it on the PHP side though.