Thread Starter
mrppp
(@mrppp)
does anyone ever read or reply to this plugin? To release an error relating to a sitemap with a seo plugin really should have been tested prior to release
No. Joost is famous for not replying. Update takes 6 months.
Thread Starter
mrppp
(@mrppp)
well time to back date the plugin then no good as it is
I got the same issue, I think last update introduced a bug where author-sitemap.xml remains in the index even if the option is disabled. Maybe next update will fix this?
as a fast fix, I commented lines 359-362 from inc/class-sitemaps.php
//$this->sitemap .= '<sitemap>' . "\n";
//$this->sitemap .= '<loc>' . home_url( $base . 'author-sitemap' . $count . '.xml' ) . '</loc>' . "\n";
//$this->sitemap .= '<lastmod>' . htmlspecialchars( $date ) . '</lastmod>' . "\n";
//$this->sitemap .= '</sitemap>' . "\n";
Thread Starter
mrppp
(@mrppp)
i,ve also noticed using the duplicator plugin i now (but never did before) get
SERIALIZATION ERRORS (1)
I run SQL SELECT option_value, autoload FROMwp_optionsWHERE option_id = “2671”;
I then see
This table does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available.
SELECT option_value, autoload
FROM wp_options
WHERE option_id = “2671”
LIMIT 0 , 30
Option Value
a:11:{s:9:"opengraph";s:2:"on";s:9:"fb_admins";a:1...
yes
I’m finding that my sitemap is not even showing up. I’ve enabled/disabled the Sitemap feature, but when I go to the URL, all I get is the homepage of my site. I see no errors in the error log.
Anyone else experiencing this?
It was working fairly recently. Not sure if this last update is what broke it though.
I caught this because I was seeing the Sitemap is HTML error on the Google Webmasters dashboard.
Rich
I posted the bug on their Github page over here https://github.com/Yoast/wordpress-seo/issues/477 and notified Joost via twitter, so he should be aware of the issue now.
@awhig I just did a blank install of wordpress 3.8 and yoast seo, the xml sitemap doesn’t work, it throws a 404. Joost commented on my issue on Github, you can go read it yourself. He seems to think it’s related to my theme, but this stopped working when WordPress released 3.8 and I’m sure it’s a bug in his plugin.
Of course it’s a bug otherwise it would be related to all the themes we are using.
@joost Always the others, right Joost?
Thread Starter
mrppp
(@mrppp)
well i get same error on 5 sites all with different themes so my money is firmly on a bug
According to Joost it’s (all) the themes… 😉
Thread Starter
mrppp
(@mrppp)
Yeah well no doubt we will see an update that corrects it, funny how last version was ok then.
Thread Starter
mrppp
(@mrppp)
For what it is worth using theme Twenty Thirteen , Twenty Eleven, Twenty 14 al have the “bug” i mean issue
