I find this setting a bit inane.
When we make/configure modules, we use different intervals of seconds. Like once every hour, once every day, every week, etc, and at which time of day you want the action to take place when the timer is up.

In this module you can choose between every time cron is run, for every 2 times cron is run, every 3 times, etc. Now, that is just arbitrary intervals with no real meaning. The admin is left with absolutely no control for when a sitemap is actually created/updated.
What if you have a site with cron run every 10 minutes or another site with cron run once a day? Or what if you run cron manually? I simply don't want a random cron run to propogate through the system changing/updating anything when it shouldn't - in this case updating the "sitemap cron counter" value.

Any special reason for doing it like this?

Also, the node "opt in" for sitemap inclusion is opposite of what I would have chosen to do. I would guess that there always will be more content (nodes, terms, and what-not) a site admin would want to include in a sitemap, than content he would want to exlude. For some of our sites we would have to "check off" 4-5 million nodes for inclusion in the sitemap with only a couple of hundres exluded...

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Since the administrator knows how much times the cron maintenance tasks are executed, he can decide when the site map is submitted to the search engines; i.e., if the cron tasks are executed every 12 hours, and he wants the site map to be submitted every day, he can select the site map to be submitted every 2 times the cron tasks are executed.

I can add more options for that setting, so it's still possible to submit the site map just once per day, in the case the cron tasks are executed every 10 minutes.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Settings: Frequency of cron and node opt in? » Frequency of site map submission
erlendstromsvik’s picture

erlendstromsvik commented

I really don't think you understood the problem here.
Having such arbitrary settings does not run well in larger systems or for any systems requiring a bit of consistency in their setups. If someone were to run cron manually a couple of times, they would suddenly initiate actions which should not be run at those times. If every module was configured this way, cron would be rendered rather useless... For larger sites this will just wreck havoc. Then again, this module does not seem to be built for large sites.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

As the support request has gotten an answer, I am setting the report as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.