Yep! (I was at 3.5 before)… no difference…
So to be on the same track: We are all talking about an unwanted output before the xml tags start, so the sitemap will fail to parse.
Possible problems as discussed so far:
1) WordPress 3.6
2) Plugin incompatibility
3) Size malfunction
4) Execution time malfunction
Lets rule some of these out.
1) and 2) might not be the problem – I got the error running 3.5. Transferring all the data to another webhoster couldnt reproduce the error (remember: Transferring ALL data – plugins, theme, database, etc).
So 3) wont be the problem neither – because the error would have come up on the other webhost aswell.
4) reducing the amount of data to process (and therefore reducing execution time) solved the case for me. For others it didnt – so this might be one trigger, but its very likely that there are others involved too.
Another guess: Did any of you manually import data into the wordpress database?
After I did, the error showed for the first time. After manually checking my database entries I found a strangely formatted entry, rewrote this – and got still an error (but a different output before the xml).
Perhaps its a combination of those two factors: Execution time, and wrongly formatted entries?
I have not done any data loads (unless you count uploading pictures into a picture gallery)… content is hand keyed.
I will disable all remaining plugings and renable one by one… but late tonight so not to mess up any clients.
Hmmmm… thinking out load… I added Jetpack not so long ago… but I really don’t want to disable that… ugh…
The error message is misleading. I had downloaded my DB with 76.000 entries and got the same message.
I have changed these values in the Apache php.ini file on my Xampp localhost installation and the sitemap was built:
max_execution_time = 3000
max_input_time = 120
memory_limit = 1000M
I am waiting for the reply of my hosting company. The server needs to be re-started.
@crashguru,
just now I also change these values as you, I restarted server and again there is no effect.
Hi guys! Now, I already fix the problem and I’m going to tell you how I did it.
Yoast Plugin – 1.4.13 v.
in /wp-content/plugins/wordpress-seo/inc/class-sitemaps.php
at line 750
/* Spit out the generated sitemap and relevant headers and encoding information. */
I set this code into comment
//header( 'HTTP/1.1 200 OK', true, 200 );
and now my all sitemaps working properly.
Check this and tell me if it work for you.
Have a nice day! 🙂
Anonymous User
(@anonymized-6417141)
Where did you put the code?
In file “class-sitemaps.php”
/wp-content/plugins/wordpress-seo/inc/class-sitemaps.php
This code is in the file
header( 'HTTP/1.1 200 OK', true, 200 );
just put it into comment
//header( 'HTTP/1.1 200 OK', true, 200 );
Anonymous User
(@anonymized-6417141)
Dont work for me. this is the error i get: Error loading stylesheet: A network error occurred while loading an XSLT stylesheet: http://www.myabdllife.com/sitemap.xsl
This is happening to me across 4 sites on striking/ udesign– about to give up on this plugin as I have been trying all of these suggestions for the last few days and have done everything BUT find the right solution— including taking down a few of them with 500 errors by following advice/ hacks to the hta. access file–
what is wrong with Yoast?
Additional insight time…
The problem is that a BLANK LINE is getting inserted at the beginning of all pages… html, xml… and google does not like that line.
I took one of the XML sitemaps generated (all gave me issues) saved it WITHOUT the blank line, submitted it to Google and it worked.
So… inspectors… what is putting in the freaking blanks line?
Anyone?
Anonymous User
(@anonymized-6417141)
I still have my problem.
this is the error i get: Error loading stylesheet: A network error occurred while loading an XSLT stylesheet: http://www.myabdllife.com/sitemap.xsl
Check your functions.php for blanks between <?php and ?>
You can also delete the last ?>
I am still getting the same problem. I love the Yoast plugin – but it seems there has been little initiative to fix this. Many others are still having the same problem as well. I’d really like to get back to using this plugin for my sitemap.
The errors I receive are all centered around not having a readable xsl file, or error loading xslt stylesheet. It just depends on which browser I use.
