dropkickpdx

Technically, I’ve solved the problem. However, I’d still like to know if anyone can shed some light on what might actually be the specific cause of the behavior I’ve been tangling with here.

The issue doesn’t present itself when PHP files are ignored by mod_expires. Which makes me suspect it’s a suboptimal configuration rather than something actually broken.

Here’s the chunk I added to the htaccess file to nip it in the bud:

<filesMatch "\.(php)$">
ExpiresActive Off
Header set Cache-Control "private, no-cache, no-store, proxy-revalidate, no-transform"
Header set Pragma "no-cache"
</filesMatch>

Right. I’ve been looking at the request and response headers all day.

The request goes out for the correct URL, then the response returns OK (200) without pushing any new HTML.

The URLs change from the current page to the next page being requested. Which is the correct behavior. We’re just not getting the content to go with it. ??

If you download a fresh copy of WordPress, then delete and replace just the wp-admin directory on your host with the one in your fresh copy, it’ll probably do the trick.

I don’t know the cause, but this has happened to me a couple of times when using the built-in updater and replacing the wp-admin directory did the trick.

It looks like there’s no styling added back in after your reset in your CSS for <em> or <strong>. That’d do it.