sissi

@tmmtechnology thanks!

@tmmtechnology this has acutally nothing to do with external urls – that was a bit misleading. but if I have the option on to “use sitemap” and I have a multisite installation, all xmls that are in the robots are crawled (by the one multisite I turn that on). Now I use different domains for my multisites, and I use them indepent from each other, everyone has its own cronjob and so on. So I would like the option to only crawl the sitemap.xml that is “correct” for that multisite, but not all sitemap.xmls that are in the robots.txt. Do you understand?

@tmmtechnology any idea on this thread when having a multsite with multiple sitemaps in the robots?

@tmmtechnology sadly, still happening

@tmmtechnology I do understand that this comes from the action scheduler but the deadlock is almost on all of my sites I am using because something with the fetch_notifications is not working ok. I get them often as “failed” actions so my solution for now is to remove the fetch notificiation from the action scheduler (because it causes either failed actions or issues with the deadlock)

also about the multisite – installation ok, but still an issue/question about the sitemap, see here

@tmmtechnology I think that had to do with the different sitemaps that were in the robots.txt. Now also for a multisite installation I only want that the sitemaps of the different sites will be crawled – there is one robots.txt with multiple sitemap entries – but the cache warmer is installed in every site. How could I do that? Can I add the sitemap als entry point (without the ceckbox) for every installation? I do combine cache clearing with hooks from the cache warmer, so every site can be warmed individually when the something happens on the site.

Any ideas on how to achieve a crawling in every site only for this site’s sitemap?

@tmmtechnology looks good! thank you.

@tmmtechnology sent you an email with all details for the staging site

@tmmtechnology

here a new case on activating the plugin on the second site on a multisite installation

[15-Apr-2024 09:31:40 UTC] WordPress database error Can't create table dbname.f1u7e_wp_2_cache_warmer_warm_ups_logs (errno: 121 "Duplicate key on write or update") for query
ALTER TABLE f1u7e_wp_2_cache_warmer_warm_ups_logs
ADD CONSTRAINT fk_warm_ups_list_id
FOREIGN KEY (list_id)
REFERENCES f1u7e_wp_2_cache_warmer_warm_ups_list(id) ON DELETE CASCADE
made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, Cache_Warmer\Cache_Warmer->Cache_Warmer{closure}, Cache_Warmer\Cache_Warmer->handle_version_update, Cache_Warmer\DB::do_migrations
[15-Apr-2024 09:31:41 UTC] WordPress database error Can't create table dbname.f1u7e_wp_2_cache_warmer_warm_ups_logs (errno: 121 "Duplicate key on write or update") for query
ALTER TABLE f1u7e_wp_2_cache_warmer_warm_ups_logs
ADD CONSTRAINT fk_warm_ups_list_id
FOREIGN KEY (list_id)
REFERENCES f1u7e_wp_2_cache_warmer_warm_ups_list(id) ON DELETE CASCADE
made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, Cache_Warmer\Cache_Warmer->Cache_Warmer{closure}, Cache_Warmer\Cache_Warmer->handle_version_update, Cache_Warmer\DB::do_migrations
[15-Apr-2024 09:31:42 UTC] WordPress database error Can't create table dbname.f1u7e_wp_2_cache_warmer_warm_ups_logs (errno: 121 "Duplicate key on write or update") for query
ALTER TABLE f1u7e_wp_2_cache_warmer_warm_ups_logs
ADD CONSTRAINT fk_warm_ups_list_id
FOREIGN KEY (list_id)
REFERENCES f1u7e_wp_2_cache_warmer_warm_ups_list(id) ON DELETE CASCADE
made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, Cache_Warmer\Cache_Warmer->Cache_Warmer{closure}, Cache_Warmer\Cache_Warmer->handle_version_update, Cache_Warmer\DB::do_migrations
[15-Apr-2024 09:31:43 UTC] WordPress database error Can't create table dbname.f1u7e_wp_2_cache_warmer_warm_ups_logs (errno: 121 "Duplicate key on write or update") for query
ALTER TABLE f1u7e_wp_2_cache_warmer_warm_ups_logs
ADD CONSTRAINT fk_warm_ups_list_id
FOREIGN KEY (list_id)
REFERENCES f1u7e_wp_2_cache_warmer_warm_ups_list(id) ON DELETE CASCADE
made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, Cache_Warmer\Cache_Warmer->Cache_Warmer{closure}, Cache_Warmer\Cache_Warmer->handle_version_update, Cache_Warmer\DB::do_migrations
[15-Apr-2024 09:31:44 UTC] WordPress database error Can't create table dbname.f1u7e_wp_2_cache_warmer_warm_ups_logs (errno: 121 "Duplicate key on write or update") for query
ALTER TABLE f1u7e_wp_2_cache_warmer_warm_ups_logs
ADD CONSTRAINT fk_warm_ups_list_id
FOREIGN KEY (list_id)
REFERENCES f1u7e_wp_2_cache_warmer_warm_ups_list(id) ON DELETE CASCADE
made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, Cache_Warmer\Cache_Warmer->Cache_Warmer{closure}, Cache_Warmer\Cache_Warmer->handle_version_update, Cache_Warmer\DB::do_migrations

@tmmtechnology I will try to set up a staging env for this, on the live site I cannot grant you access.

There are some tables missing and some tables were created but with no db fields (so table was there but no columns) … will get back to you with details.

@tmmtechnology

if i call the url directly it works too, but on some installations i will get this in the error pane quite often of the action scheduler. maybe there is some downtime … but when you call the url, you might can add a try/catch if the rsponse is not 200 so you skip it or something?

thank you.

great, thank you.

sent the images via mail to you at [email protected]

ok, I just found out, the plugin tries to find the entry in the robots.txt file for the sitemap and otherwise tries to use sitemap.xml – which might be a general default but not if you are using a seo plugin … then it is usually sitemap_index.xml

I had some sort of access wall / firewall active, so the requests could not be made… nothing to do with the plugin.