Tom Goering

The following is a reply I received from my Web host as to why issues are occurring with WP Super Cache.

I hope this helps:

Hello there!

Sorry for the delay in response. Support queues are higher than we’d like right now, but let’s cut to the chase:

WP Super Cache is active, configured to HostGator’s specifications, and working.

For some unknown reason, despite extensive investigation, WP Super Cache’s own testing system fails because it is unable to resolve its own domain. The plugin is not making a DNS request to identify where www.navycs.com goes. I’ve never seen this error before, and it would be too time-consuming to go into the plugin and pinpoint the code that seems to be problematic. If this is concerning to you, I would recommend that you contact the developer of the plugin with the information I mentioned in this email.

The probable explanation for why you received the “Served super cache file from PHP” header is that the page that you read the headers from was already cached. Flushing your browser cache and the WP Super Cache cache would force your site to resend the page, which should not have that header value anymore.

I hope this information has been helpful to you. Please don’t hesitate to follow up if you have any more questions or concerns.

Sincerely,

Nick L.
Linux Systems Administrator
HostGator.com, LLC

Interestingly, when I check the “Disable the visual editor when writing.” I get the HTML mode with the buttons, but of course, I don’t get the VISUAL mode option.

Thank you, but I don’t use that plug-in. As a matter of fact, I don’t use any plugin that affects how I edit a post/page.