In the SQL queries involving the priority_override database field, the queries cause an error similar to the following ones:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE uid = 1009' at line 3 query: UPDATE xmlsitemap_user SET previously_changed = last_changed, last_changed = 1230336242, priority_override = WHERE uid = 1009 in /home/local/public_html/beta/includes/database.mysql.inc on line 174.

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE tid = 24' at line 3 query: UPDATE bms_idigir.xmlsitemap_term SET pid = 91, last_changed = 1215015770, previously_changed = last_changed, priority_override = WHERE tid = 24 in /home/bms/bms/includes/database.mysql.inc on line 172.

Comments

iamwhoiam’s picture

iamwhoiam commented

How's the development of this?

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE nid = 253'; at line 3 query: UPDATE xmlsitemap_node SET previously_changed = last_changed, last_changed = 1236506988, priority_override = WHERE nid = 253 in /.../includes/database.mysql.inc on line 174.

It's happening on nodes too

brianbrown’s picture

brianbrown commented

I have this issue also!

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

#503010: Close the 5.x-2.x-dev branch as unsupported

avpaderno’s picture

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

As in another thread Dave reported that only the critical bugs should be fixed, is not this a critical bug?

Reporting a bug as fixed, without to explain anything about the reason, just means that the bug has been really fixed; it would be better to set the issue as "won't fix".

sashomi’s picture

sashomi commented

Here is how I fixed this:
inside the case 'update' in xmlsitemap_node_nodeapi() function (line 160):

if (!isset($node->priority_override)) {
$priority_override = db_result(db_query("SELECT priority_override FROM {xmlsitemap_node} WHERE nid = %d", $node->nid));
$node->priority_override = $priority_override !== FALSE ? $priority_override : 'NULL';

// I put this if:
if (trim($node->priority_override) == "") {
$node->priority_override = 'NULL';
}
}

this fixes the empty string in $node->priority_override

Hope this helps and want to ask will there be development of 2.0 version, for there is no more dev for XML sitemap 5.x-2.x?

Status: Fixed » Closed (fixed)
Issue tags: -SQL queries

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

Issue tags: +SQL queries

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.