The admin checkbox labeled "Submit the sitemap when content changes" subhead "If enabled, the search engines will only be notified of changes to the sitemap whenever the sitemap content is changed." is unclear.

As I understand it, the functionality is such that when the checkbox is CHECKED, then changes are submitted IMMEDIATELY, and if unchecked, changes are submitted wheneven cron runs, then the checkbox label should say "Update and submit the sitemap immediately when content changes", and the subhead should say "If enabled, the sitemap will be updated and search engines will be notified immediately whenever content is changed. If not enabled, the sitemap will be updated and search engines will be notified when cron runs. Note that enabling immediate updates can have a significant performance impact."

Do I understand the functionality correctly? If so, I'll make a patch.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Component: Documentation » xmlsitemap_engines.module
Status: Needs review » Active

We've locked down the 6.x-1.x version and are basically only accepting issues for 6.x-2.x since we're now advising everyone to upgrade. You might want to take a look at 6.x-2.x and see if there are any changes that need to be made in the xmlsitemap_engines interface.

Anonymous’s picture

Anonymous (not verified) commented
Component: xmlsitemap_engines.module » Documentation

No, that isn't it. The sitemap is only submitted during a hook_cron regardless if content changed or not. The difference is the flagging of when to submit to the search engines which is either based on content change or some timed interval. The flag is only valid for sites whose content rarely changes and caution should be used to not submit to the search engine too often because they may consider you to be abusive and prevent your IP address from submitting to the engine.

gobinathm’s picture

gobinathm
he/him
Primary language English
Location Milton, Ontario
commented
Issue summary: View changes
Status: Active » Closed (outdated)

As D6 is in EOL, I believe there won't be any support / fix for a problem identified in 6x going forward. Given the fact that D6 is already EOL. Hence i guess this issue can be closed.

Changing the status, if incorrect pls revert the status.