Closed (duplicate)
Project:
XML sitemap
Version:
5.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Apr 2009 at 09:46 UTC
Updated:
24 Apr 2009 at 12:47 UTC
Jump to comment: Most recent
Comments
Comment #1
munroe_richard commentedIn: xmlsitemap_node.module
I "fixed" the problem by changing the UPDATE query to check explicitly for NULL and do the right thing by emitting a NULL in that event. The real problem is that the check for !== FALSE will be TRUE if $node->priority_override is NULL, so the fix should probably be for FALSE to change to NULL (or the operation changed to != instead of !==).
Here's what I did as a work around:
Here's probably what should happen...
Best,
Dick Munroe
Comment #2
Anonymous (not verified) commentedActually !== FALSE is correct since the check is for the existence of a DB row. The bug was in the store of NULL in priority_override in xmlsitemap_node to begin with.
Comment #3
Anonymous (not verified) commentedI was wrong the bug is the lack of '' around the %s.
This
should read
Comment #4
Anonymous (not verified) commentedComment #5
avpadernopriority_override is a number, not a string; the placeholder used is different because a trick implemented.
This report is a duplicate of #373621: $priority_override doesn't get any value.