XF 2.2 Does a CLI Sitemap Rebuild also submit to Search Engines?

[Mouth]

If rebuilding a sitemap via CLI, php cmd.php xf-rebuild:sitemap, does it also auto submit to search engines, admin.php?options/groups/sitemap/#sitemapAutoSubmit

 

[Jeremy P]

Yeah.

 

[Mouth]

Yeah.

Thanks.

Further related to this question, the CLI rebuild console output suggests only Threads are being rebuilt ...

#php cmd.php xf-rebuild:sitemap

Rebuilding... Sitemap (Threads 68991)
Rebuilding... Sitemap (Threads 93143)
Rebuilding... Sitemap (Threads 120047)
Rebuilding... Sitemap (Threads 167802)
Rebuilding... Sitemap (Threads 227561)
Rebuilding... Sitemap (Threads 257926)

#

I have lots of other content types included/selected at admin.php?options/groups/sitemap/#sitemapExclude (including XFRM), and would think the console output should also represent that those content types are being rebuilt too. (They are, they're within the XML files).

 

[Jeremy P]

Is that the totality of the output? Content types are rebuilt one at a time, so after finishing up with threads it will move on to the others. The output is only meant to report the current status every few seconds, and it is not written a final time when the job completes. So if all of the other content types were rebuilt in the last few seconds, there would be no output indicating it.

As long as the sitemaps contain the expected contents, I wouldn't sweat it. The CLI rebuilder is exactly the same as the one which runs automatically (or the one which you can also run manually from the control panel).

 

[Mouth]

Is that the totality of the output?

Yes.

so after finishing up with threads it will move on to the others.

Could it be the other way around? There's approx. a 5sec. 'lag' from launching the rebuild until the console output with Threads appears.

As long as the sitemaps contain the expected contents, I wouldn't sweat it.

 

[Jeremy P]

Could it be the other way around? There's approx. a 5sec. 'lag' from launching the rebuild until the console output with Threads appears.

Other content types could be rebuilt before threads, yes.

In any case, the output only reports the current status of the rebuild at the time it is printed, rather than a comprehensive report of which content has been processed since the last output. That is to say that anything that occurred between the outputs is not indicated at all, if that makes sense.