Download & Extend
XML sitemap » Issues

Individual node priority/exclusion

Posted by kiamlaluno on May 23, 2009 at 1:26pm
Project:XML sitemap
Version:6.x-2.x-dev
Component:xmlsitemap_node.module
Category:feature request
Priority:normal
Assigned:Dave Reid
Status:closed (fixed)
Issue tags:6.x-2.0-alpha blocker

Issue Summary

There is not the possibility to set a priority for a node that override the default priority set for the content types.
This means that to avoid a node appears in the sitemap, its content type must be set to not appear in the sitemap.

There are cases where it's desirable to be able to avoid single nodes are included in the sitemap.

Login or register to post comments

Comments

#1

Posted by Dave Reid on May 23, 2009 at 1:29pm
Status:active» postponed

It's planned but postponed to finish the basic features first. Then I'm moving to the 'advanced' features.

#2

Posted by Dave Reid on May 23, 2009 at 3:40pm
Title:Possibility to set a different priority for specific nodes» Individual node priority/exclusion

#3

Posted by kiamlaluno on May 23, 2009 at 3:54pm
Title:Individual node priority/exclusion» Individual node/user priority/exclusion
Component:xmlsitemap_node.module» Code

The same is true for the users.

#4

Posted by Dave Reid on May 23, 2009 at 3:55pm
Title:Individual node/user priority/exclusion» Individual node priority/exclusion
Component:Code» xmlsitemap_node.module

Please keep these separate per module.

#5

Posted by Dave Reid on May 30, 2009 at 10:49pm

Marked #477588: Exclude URLs from the sitemap.... as a duplicate of this issue.

#6

Posted by Dave Reid on June 2, 2009 at 1:34am

Thinking about how best to implement this is to have a separate {xmlsitemap}.priority_override column which is a NULL-able float, just like the {xmlsitemap}.priority column. That way, we can change the default priority for a node type, and then if a node with a custom priority is set back to 'default', it still gets the proper priority value. Then, when we select the data for sitemap output, all we need to do is use COALESCE(priority_override, priority) to get the proper priority value.

#7

Posted by Dave Reid on June 11, 2009 at 3:49am
Assigned to:Anonymous» Dave Reid
Status:postponed» active

Individual node priority has been added. I'm still working on tests and individual node status.

#8

Posted by Dave Reid on July 7, 2009 at 4:57am

I could really use some input and feedback on the one last remaining architectural problem in the 6.x-2.x version: #512216: Last architectural problem: override a link's status in the sitemap (inclusion/exclusion).

#9

Posted by Dave Reid on July 13, 2009 at 10:46pm

Tagging as alpha blocker.

#10

Posted by Dave Reid on July 13, 2009 at 11:04pm

Marking #518336: Include "Not In Sitemap" as priority option as a duplicate of this issue.

#11

Posted by Dave Reid on August 19, 2009 at 11:13pm
Status:active» fixed

Finally finished with #512216: Last architectural problem: override a link's status in the sitemap (inclusion/exclusion) and can marking this as fixed now.

#12

Posted by System Message on September 2, 2009 at 11:20pm
Status:fixed» closed (fixed)

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

nobody click here