Rethink how "msm_sitemap_update_last_run" works

[automattic]

Rethink how "msm_sitemap_update_last_run" works

[pkevan]

If we do switch to a cli driven initial generation as per #76 then it makes sense to indicate a level of progress perhaps per year completed in the dashboard.

It probably makes sense to keep the two process (update and initial generation) separate otherwise we could be in a situation where an initial generation fails and the update process then creates the large amount of cron events that we were trying to avoid.

@tollmanz is there a reason you use the script in 3 rather than wp msm-sitemap generate-sitemap

Was just thinking that this could be used to track the progress of initial generation even if it's only on each year completed

[tollmanz]

It probably makes sense to keep the two process (update and initial generation) separate otherwise we could be in a situation where an initial generation fails and the update process then creates the large amount of cron events that we were trying to avoid.

This makes sense. This is mostly a note to self that this will become and issue if we move forward with something like #76. We would need to make sure that the UX makes all of this clear.

@tollmanz is there a reason you use the script in 3 rather than wp msm-sitemap generate-sitemap

This was a @mjangda suggestion. It seems safe to complete smaller chunks of work at a time and if I need to stop the process, I can then manipulate the loop when starting again to ignore certain month/year combinations. Additionally, I was thinking I might put in some timeouts in the loop in order to reduce server load if needed.

[pkevan]

Probably a valid suggestion if @mjangda said so 😄 - I've never run it on large data set other than locally so can't really comment.

@mjangda do you think there is a way to achieve a complete set through CLI, maybe a stepped approach which prompts the user?