Closed (fixed)
Project:
XML sitemap
Version:
6.x-1.0-rc2
Component:
xmlsitemap.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Oct 2009 at 20:41 UTC
Updated:
2 Nov 2009 at 16:10 UTC
Jump to comment: Most recent
Comments
Comment #1
modulist commentedComment #2
dave reidIt's not likely that we will ever put a list of content types and their xml sitemap setting options in one place. Because when those changes are made there is the possibility of some large SQL updates on the existing data need to be made. You might be interested in the 6.x-2.x version which at least puts all the information in one place and directly links to the node/menu/taxonomy edit pages. See sandbox.davereid.net for a demo site with access to administer xmlsitemap.
Comment #3
Anonymous (not verified) commentedAre the module weights of these modules after xmlsitemap? Use the Utility module to adjust xmlsitemap modules after these.
Comment #4
modulist commentedThanks for addressing this issue quickly. We are concerned about having to exclude nodes of a certain content type node by node, particularly when they're ads or other content that's not managed through CCK.
Is there a patch or a function that we could run on our end?
Comment #5
Anonymous (not verified) commentedOn the content type edit page you can select the default for the xmlsitemap to be "Not in sitemap" and any new nodes created automatically would not be included. You may need to adjust the module weights for programmatic node content. Is this what you are looking for?
Comment #6
dave reidThe ability to exclude or include by node type (on admin/content/my-type/edit) or individual nodes (on node/nid/edit) is already in the module.