PluginProbe
ThinkRank AI SEO – AI SEO Plugin for WordPress: Schema, XML Sitemaps, Meta Tags, Search Console & Local SEO / 2.10.0
ThinkRank AI SEO – AI SEO Plugin for WordPress: Schema, XML Sitemaps, Meta Tags, Search Console & Local SEO v2.10.0
2.10.0 2.9.0 2.8.0 2.7.0 2.6.0 2.5.0 2.4.0 2.3.0 2.2.0 2.1.1 2.1.0 2.0.2 2.0.1 2.0.0 1.32.0 1.31.0 1.30.0 1.29.0 1.28.0 1.27.0 1.26.0 1.25.0 trunk 1.0.0 1.0.1 All 51 releases
← All changes | includes/api/class-sitemap-endpoint.php +123 -4 2.0.2 → 2.10.0 View file →
@@ -14,8 +14,13 @@
14 14 declare(strict_types=1);
15 15
16 16 namespace ThinkRank\API;
17 17
18 +// Prevent direct access
19 +if (!defined('ABSPATH')) {
20 + exit;
21 +}
22 +
18 23 use ThinkRank\SEO\Sitemap_Generator;
19 24 use ThinkRank\API\Traits\CSRF_Protection;
20 25 use ThinkRank\API\Traits\Context_Authorization;
21 26 use WP_REST_Controller;
@@ -22,8 +27,13 @@
22 27 use WP_REST_Request;
23 28 use WP_REST_Response;
24 29 use WP_Error;
25 30
31 +// Prevent direct access
32 +if (!defined('ABSPATH')) {
33 + exit;
34 +}
35 +
26 36 // Load CSRF Protection trait
27 37 require_once THINKRANK_PLUGIN_DIR . 'includes/api/traits/trait-csrf-protection.php';
28 38 require_once THINKRANK_PLUGIN_DIR . 'includes/api/traits/trait-context-authorization.php';
29 39
@@ -254,8 +264,14 @@
254 264 $timestamp = gmdate('c');
255 265 $settings = $this->sitemap_generator->get_settings('site');
256 266 $settings['last_generated'] = $timestamp;
257 267 $this->sitemap_generator->save_settings('site', null, $settings);
268 +
269 + // This generation wrote the same files the outstanding automatic rebuild
270 + // was queued to write, so clear its marker (and any recorded failure)
271 + // instead of leaving a request-time takeover to repeat the work.
272 + $this->sitemap_generator->mark_regeneration_complete();
273 +
258 274 return $timestamp;
259 275 }
260 276
261 277 /**
@@ -278,8 +294,24 @@
278 294 $this->sitemap_generator->save_settings('site', null, $settings);
279 295 }
280 296
281 297 /**
298 + * Stored sitemap settings with this request's options laid over them.
299 + *
300 + * The generate payload is partial — the admin screen posts the sitemap
301 + * shape, not the whole settings record — so reading `delivery_mode` straight
302 + * off it would resolve to `auto` on every ordinary request and defeat an
303 + * explicit choice. Merging keeps a mode sent in the payload authoritative
304 + * while falling back to what is saved.
305 + *
306 + * @param array $options Request options.
307 + * @return array Effective settings for this generation.
308 + */
309 + private function effective_settings(array $options): array {
310 + return array_merge($this->sitemap_generator->get_settings('site'), $options);
311 + }
312 +
313 + /**
282 314 * Persist a manual-generation auto-promotion into the stored settings.
283 315 *
284 316 * maybe_promote_to_index() may flip use_sitemap_index on and synthesize the
285 317 * segmented sitemap_urls for the current generation. On the automatic path
@@ -351,8 +383,17 @@
351 383 }
352 384
353 385 $sitemap_url = $this->sitemap_generator->get_primary_sitemap_url($settings);
354 386
387 + // Dynamic delivery publishes no file, so there is nothing to ensure and
388 + // nothing to look for on disk. Dropping the rendered documents is what
389 + // makes the saved settings take effect on the next request (#752).
390 + if ('dynamic' === $this->sitemap_generator->resolve_delivery_mode($settings)) {
391 + $this->sitemap_generator->flush_dynamic_cache();
392 +
393 + return $sitemap_url;
394 + }
395 +
355 396 if ($this->sitemap_generator->primary_sitemap_file_exists($settings)) {
356 397 return $sitemap_url;
357 398 }
358 399
@@ -421,8 +462,59 @@
421 462 // generate_and_save() already does this on the automatic path; the
422 463 // manual generate route must match it.
423 464 $this->persist_promoted_mode($options);
424 465
466 + // Dynamic delivery answers the sitemap URLs from PHP, so there is
467 + // nothing to write. Every other sitemap write path already returns
468 + // early here (class-sitemap-generator.php:2189 and :2313); this one
469 + // did not, which broke the feature from both directions: on a
470 + // read-only root — the case dynamic delivery exists for — the button
471 + // reported 500 "Failed to save sitemap: sitemap.xml" while the URL
472 + // was serving correctly, and on a writable root with dynamic chosen
473 + // explicitly it wrote files the web server then served in place of
474 + // the dynamic route.
475 + //
476 + // Regenerating here means dropping the rendered documents so the
477 + // next request rebuilds them, and clearing any file left behind by
478 + // an earlier static generation for the same reason.
479 + if ('dynamic' === $this->sitemap_generator->resolve_delivery_mode($this->effective_settings($options))) {
480 + $this->sitemap_generator->flush_dynamic_cache();
481 +
482 + $removal = $this->sitemap_generator->delete_published_sitemaps();
483 + $stuck = is_array($removal['failed'] ?? null) ? $removal['failed'] : [];
484 +
485 + // A stale file shadows the dynamic route, so this is a real
486 + // failure rather than a tidy-up that did not matter. Worded by
487 + // the generator so this and its own rebuild paths cannot
488 + // describe the same stuck files differently (#764).
489 + if (!empty($stuck)) {
490 + return new WP_Error(
491 + 'sitemap_stale_files',
492 + $this->sitemap_generator->stuck_files_message($stuck),
493 + ['status' => 500]
494 + );
495 + }
496 +
497 + // last_generated deliberately stays untouched: it means "these
498 + // files are on disk", and primary_sitemap_file_exists() callers
499 + // rely on that. clear_generation_record() drops a value left
500 + // over from a previous static generation, so the admin stops
501 + // linking to files that no longer exist.
502 + $this->clear_generation_record();
503 + $this->sitemap_generator->mark_regeneration_complete();
504 +
505 + return new WP_REST_Response([
506 + 'success' => true,
507 + 'data' => [
508 + 'delivery_mode' => 'dynamic',
509 + 'sitemap_url' => $this->sitemap_generator->get_primary_sitemap_url(),
510 + 'generated_at' => gmdate('c'),
511 + 'last_generated' => '',
512 + ],
513 + 'message' => __('Sitemap refreshed. WordPress serves it directly, so no files were written.', 'thinkrank'),
514 + ]);
515 + }
516 +
425 517 // Check if an index (multiple sitemaps) is configured
426 518 if (!empty($options['use_sitemap_index']) || (!empty($options['sitemap_urls']) && count($options['sitemap_urls']) > 1)) {
427 519 // Generate multiple sitemaps
428 520 $results = $this->sitemap_generator->generate_multiple_sitemaps($options);
@@ -456,9 +548,21 @@
456 548 $filename = 'sitemap.xml';
457 549 if (!empty($options['sitemap_urls'][0]['url'])) {
458 550 $filename = basename(wp_parse_url($options['sitemap_urls'][0]['url'], PHP_URL_PATH));
459 551 }
460 - $this->save_sitemap_file($sitemap_xml, $filename);
552 + // A failed write has to surface here the way the index
553 + // branch surfaces one. Discarding it let record_generation()
554 + // advance last_generated and clear the pending marker and
555 + // the recorded failure, so an unwritable site root — the
556 + // exact case this endpoint reports health for — came back
557 + // as a healthy "Generated successfully".
558 + if (!$this->save_sitemap_file($sitemap_xml, $filename)) {
559 + return new WP_Error(
560 + 'sitemap_generation_failed',
561 + 'Failed to save sitemap: ' . $filename,
562 + ['status' => 500]
563 + );
564 + }
461 565
462 566 // Regenerate the standalone local business sitemap on the
463 567 // single-sitemap path too (parity with Rank Math).
464 568 $this->sitemap_generator->regenerate_local_sitemap($options);
@@ -902,9 +1006,24 @@
902 1006 'success' => true,
903 1007 'data' => [
904 1008 'settings' => $settings,
905 1009 'context_type' => $context_type,
906 - 'context_id' => $context_id
1010 + 'context_id' => $context_id,
1011 + // Kept out of `settings` on purpose: this is generator state,
1012 + // not something the settings POST round-trips.
1013 + 'health' => $context_type === 'site'
1014 + ? $this->sitemap_generator->get_regeneration_health()
1015 + : null,
1016 + // `delivery_mode` in `settings` may still be 'auto', which
1017 + // only the server can resolve (it depends on whether the web
1018 + // root is writable). The admin screen needs the answer, not
1019 + // the question: a dynamic site publishes no file, so gating
1020 + // its sitemap links on `last_generated` — which dynamic
1021 + // delivery deliberately never sets — left every link
1022 + // permanently disabled.
1023 + 'resolved_delivery_mode' => $context_type === 'site'
1024 + ? $this->sitemap_generator->resolve_delivery_mode($settings)
1025 + : null
907 1026 ],
908 1027 'message' => 'Sitemap settings retrieved successfully'
909 1028 ], 200);
910 1029
@@ -1294,9 +1413,9 @@
1294 1413 * @since 1.0.0
1295 1414 * @return bool True if lock acquired
1296 1415 */
1297 1416 private function acquire_generation_lock(): bool {
1298 - $lock_key = 'thinkrank_sitemap_generation_lock';
1417 + $lock_key = Sitemap_Generator::GENERATION_LOCK_TRANSIENT;
1299 1418
1300 1419 if (get_transient($lock_key)) {
1301 1420 return false; // Generation already in progress
1302 1421 }
@@ -1311,7 +1430,7 @@
1311 1430 * @since 1.0.0
1312 1431 * @return void
1313 1432 */
1314 1433 private function release_generation_lock(): void {
1315 - delete_transient('thinkrank_sitemap_generation_lock');
1434 + delete_transient(Sitemap_Generator::GENERATION_LOCK_TRANSIENT);
1316 1435 }
1317 1436 }