pimg

@djennez @pcosta88 Now that this is hopefully resolved would yall mind editing my messages are removing the URL’s please?

Hello,
Good to hear this has been fixed. Yes our site and home URL’s are set to 2 different values for security reasons.

I have already fully cleared and disabled the cache and the issue persist. It appears this is a widespread issue as I count 5+ reports in this forum alone in the past couple of weeks for this same exact error.

Chrome console outputs the following error, not sure if this is something yall can
investigate as well:

Resource interpreted as Stylesheet but transferred with MIME type text/xml: “https://www.michigantmjandsleep.com/main-sitemap.xsl”.

https://www.michigantmjandsleep.com/x/lc-content/plugins/wordpress-seo/css/main-sitemap.xsl appears to be working although no contents are shown.

1. Yes this is on WP 5.4.2

2. Yes all other plugins and themes are updated.

3. Yes the server exceeds all requirements and has several other sites on the same server that work but arent as up to date with WP and Yoast as mentioned in the original post.

4. This server does not run Apache as it is running Litespeed so neither of those seem to apply and again sitemaps work on this server already with other sites not as up to date with no other rules needed.

5. This server already serves other sitemaps correctly so it is not a server limitation.

• This reply was modified 4 years, 7 months ago by pimg.

This plugin version of the main-sitemap.xsl link for our site works as well with no 403 error but shows no links.

@mikes41720

Hello, just to chime in we are now experiencing this same issue as well with blank sitemaps on multiple websites. We can see them in the source code though just never loads on the front end / shows white. It seems like something deeper is going on. We have already tested with the cache off and confirmed nothing was in the .htaccess as well.

@hailite

I just wanted to add in our support for this feature, it is the one thing holding our sites back from getting higher that 60’s on mobile (unused CSS and JS). The Amp for WP plugin seems to have implemented something similar for CSS tree shaking and has a few functions for overcoming the relative path issues above. Might be worth looking into. class-amp-tree-style-sanitizer.php

• This reply was modified 4 years, 8 months ago by pimg.

@renathoc is this something that can be looked into?

I too don’t like to publicly voice concerns unless absolutely needed but would just like to chime in that this same exact scenario played out for us as well. We purchased the AmpforWP Gravity forms addon but decided to not use AMP and ultimately not the AmpforWP addon. We canceled the renewal and too were sent various emails asking us to re-sign up confirming it was canceled (as well as it said canceled on the site). Then magically on the date of renewal we were sent a completely blank email and then after we were charged for another year of renewal / our subscription changed back to active. After contacting support, we too were then given a refund that was “approved and initiated by the billing department” but this did not come for over a month. Finally after contacting them again after a month, the refund was pushed through their payment processor.

I dont want to accuse AmpForWP of financial malfeasance with credit cards since I am no legal expert but seeing this exact scenario above played out for multiple people tells me typically where there is smoke there is fire. Is there anyone higher up at Automattic or the plugin repo who could be brought into the loop on this?

• This reply was modified 4 years, 9 months ago by pimg.
• This reply was modified 4 years, 9 months ago by pimg.

Can someone look into ticket/report FYFHMJAB please? You should be able to login to the site as well with details in the ticket.

Hi,
I tried the “Disable All Features” in Toolbox -> Debug Settings and the issue persist.