You need to support them asap.
Both images sitemaps and AMP support are currently on the roadmap and/or actively being worked on. I could be mistaken, but I don’t think Jetpack sitemaps include AMP pages.
have you thought about what this action might have done for the 100’s of thousands of sites using AIOSEO but not your sitemap
Absolutely; though those numbers are probably a bit off, there was immediately an issue created, and is already a patch ready to go in the next version.
damaging their Search Results
This most likely won’t have any negative effect on most sites. Temporarily removing your sitemap doesn’t deindex URLs.
I find it particularly frustrating it’s doing this even with the Sitemap Module disabled. Frankly I kinda expect this kind of thing from Yoast, but not you guys. It’s part of the reason I started switching all my sites from Yoast over to AIOSEO. Hoping this gets fixed within days – not weeks.
I agree 100%. 2.3.6.1 will be out within days.
In the meantime, you can bring back Jetpack’s sitemap by replacing the function remote_jetpack_sitemap() in /inc/compatability/compat-init.php with the following code:
public function remove_jetpack_sitemap( $modules ) {
global $aioseop_options;
// Check if AIOSEOP's sitemap exists.
if ( isset( $aioseop_options['modules']['aiosp_feature_manager_options']['aiosp_feature_manager_enable_sitemap'] ) && $aioseop_options['modules']['aiosp_feature_manager_options']['aiosp_feature_manager_enable_sitemap'] === 'on' ) {
unset( $modules['sitemaps'] ); // Remove Jetpack's sitemap.
}
return $modules;
}
If you aren’t sure how to edit the plugin files, you can download the latest development version here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/archive/development.zip