ittone

Hi again Raul.

Windows? What is that?

UNIX/Linux rules.
Permissions should never be set to 777 for any directory, and the owner:group names are correct. Directory locations as shown in the settings tab are fine.

As stated the FVM settings are as set on the non-working site are exactly the same as on the three other sites that FVM 3.08 works.

When I re-installed v2.8.9 that site works fine.
Upgrading or even installing from scratch v3.x does not create minified files.

The only place that could be preventing this now, is the MariaDB SQL database.
I have scoured wp-options and deleted all dormant FVM entries. (All….I think)

Anything else in the database that could be causing this frustrating problem?

Hi Marko

No problem, we got there in the end.

I am not in a position to recommend that documentation needs ammending to include ‘Handle XML mime-type’ is to be enabled when using cached sitemaps when utilising the enhanced mode cache.

Perhaps this should be enabled on releases as default upon installation and update time.

Thanks for your time.
Kind Regards
IT Tone

Hi Marco

This original ticket was raised for my domain of backtothemovies.com which was migrated from siteground to WPX.
Following this migration I noticed the sitemap error on google webmaster.

The domain of lifthillsandthrills.com which we have been looking at since you told me to exclude the sitemap from backtothemovies.com (which no longer uses W3TC) is on my own LINUX server here at home, as stated above, has the sitemap error.

This domain has the same issue and so does another domain hosted on another hosting company. (tonesworld.co.uk/sitemap_index.xml)

You told me yesterday: “Thank you for the info. Well now at the moment those sitemaps are no longer valid.”

I am now swapping all my five domains caching programs from W3TC which I have been using for numerous years.
I know you only took over W3TC in 2019 but please remember that I highlighted this cache bug in W3TC enhanced cache mode during November 2020.

Thanks for your assistance.

IT Tone
Linux Technical Support Manager.

Hi again Marko

The site is still in disk:enhanced mode. (For your test purposes)
The sitemap is STILL in cache.

Once again, the sitemap reports as passed when the sitemap_index\.xml is added as per your advice. (ie: url to exclude), but this is a workaround, not a solution.

Yes, I am using Yoast……But it does not matter, the html errors are also reported for Rank Math SEO sitemap.xml and also for Google XML Sitemaps sitemap.xml.

Thanks

Hi Marko

The sitemap reports as passed when the sitemap_index\.xml is added as per your advice. However, this is a workaround as the real issue appears to be how a PHP7.4
module is interacting with the cached sitemap.

As I said, when my .htaccess W3TC entries are removed then all is OK.

I have just this minute cleared the cache from my Firefox, Edge and Chrome browsers…I have just cleared my server’s W3TC cache for lifthillsandthrills, tried the xml validation tests using the url:
https://www.lifthillsandthrills.com/sitemap_index.xml

and received this:

XML Validation Results
error Problem detected, please check details below
Sitemap URL https://www.lifthillsandthrills.com/sitemap_index.xml
Character Set
Sitemap is valid No
Warnings –
Errors
Incorrect http header content-type: “text/html; charset=UTF-8” (expected: “application/xml”)
————————————————————

When the headers were examined, I recieved this:

HTTP Headers Viewer
Webpage URL
https://www.lifthillsandthrills.com/sitemap_index.xml
Response details
Content size: 1,133 bytes
Download time: 0.084s
HTML Title: –
——————————————————-
HTTP Headers found in response
Response Code HTTP/1.1 200 OK
Date Thu, 05 Nov 2020 14:31:37 GMT
Server Apache
X-Powered-By PHP/7.4.6
Cache-Control max-age=0
Expires Thu, 05 Nov 2020 14:31:37 GMT
Vary Accept-Encoding
Content-Length 1133
Connection close
Content-Type text/html; charset=UTF-8
—————————————————–
HTTP Headers Received
HTTP/1.1 200 OK
Date: Thu, 05 Nov 2020 14:31:37 GMT
Server: Apache
X-Powered-By: PHP/7.4.6
Cache-Control: max-age=0
Expires: Thu, 05 Nov 2020 14:31:37 GMT
Vary: Accept-Encoding
Content-Length: 1133
Connection: close
Content-Type: text/html; charset=UTF-8
————————————————————
HTTP Request Sent
GET /sitemap_index.xml HTTP/1.1
Host: http://www.lifthillsandthrills.com
User-Agent: Mozilla/5.0 (compatible; XML Sitemaps Generator; http://www.xml-sitemaps.com) Gecko XML-Sitemaps/1.0
Accept: */*
Connection: Close

So how you are receiving a pass, I do not know.

Can another reader of this thread please try the above sitemap.xml in the validator to confirm/not confirm my results please.

IT Tone.

A little further information.

When the sitemap_index.xml is tested from:
https://freetools.webmasterworld.com/tools/site-validator/ I get the following output:

XML Sitemap Validator
<html><head><META HTTP-EQUIV=”Cache-control” CONTENT=”no-cache”><META HTTP-EQUIV=”refresh” CONTENT=”0;URL=/cgi-sys/defaultwebpage.cgi”></head><body></body></html> ———————————————————————————————————————————————–^ Fatal Error 76: Opening and ending tag mismatch: META line 1 and head on line: 1 column: 143 <html><head><META HTTP-EQUIV=”Cache-control” CONTENT=”no-cache”><META HTTP-EQUIV=”refresh” CONTENT=”0;URL=/cgi-sys/defaultwebpage.cgi”></head><body></body></html> ——————————————————————————————————————————————————————-^ Fatal Error 76: Opening and ending tag mismatch: META line 1 and html on line: 1 column: 163 -^ Fatal Error 77: Premature end of data in tag head line 1 on line: 2 column: 1 -^ Fatal Error 77: Premature end of data in tag html line 1 on line: 2 column: 1 <html><head><META HTTP-EQUIV=”Cache-control” CONTENT=”no-cache”><META HTTP-EQUIV=”refresh” CONTENT=”0;URL=/cgi-sys/defaultwebpage.cgi”></head><body></body></html> ———————————————————————————————————————————————–^ Fatal Error 76: Opening and ending tag mismatch: META line 1 and head on line: 1 column: 143 <html><head><META HTTP-EQUIV=”Cache-control” CONTENT=”no-cache”><META HTTP-EQUIV=”refresh” CONTENT=”0;URL=/cgi-sys/defaultwebpage.cgi”></head><body></body></html> ——————————————————————————————————————————————————————-^ Fatal Error 76: Opening and ending tag mismatch: META line 1 and html on line: 1 column: 163 -^ Fatal Error 77: Premature end of data in tag head line 1 on line: 2 column: 1 -^ Fatal Error 77: Premature end of data in tag html line 1 on line: 2 column: 1
Validate sitemap from URL

Test carried out on: https://www.lifthillsandthrills.com/sitemap_index.xml
which is still currently in disk:enhanced mode

Thanks
IT Tone

Hi Marko

Thanks for the quick response.

No server side caching but using WPX CDN service and not using w3tc browser cache only the cache module.

If I exclude sitemap from caching would that not add extra processer utilisation etc?

For the other recommendations would you also advise the same for basic disk caching, because that as I said works with no problem.

Thanks