Closed (fixed)
Project:
XML sitemap
Version:
5.x-1.2
Component:
xmlsitemap_node
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 Nov 2007 at 06:24 UTC
Updated:
23 Aug 2008 at 08:05 UTC
I am getting this error when updating or deleting a node. I have PHP 5.2, mysql 5.x, Drupal 5.3. I don't see no error when it submits to the search engines.
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 = 442' at line 3 query: UPDATE xmlsitemap_node SET pid = NULL, previously_changed = last_changed, priority_override = WHERE nid = 442 in /../../database.mysql.inc on line 172.
Comments
Comment #1
jomtois commentedI am also getting a similar error:
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 ')' at line 1 query: INSERT INTO xmlsitemap_term (tid, pid, last_changed, priority_override) VALUES (13, 0, 1194957616, ) in /.../database.mysql.inc on line 172.
Comment #2
darren ohFixed in CVS commit 87942.
Comment #3
jomtois commentedComment #4
jomtois commentedComment #5
jomtois commentedCan you do a similar fix for the xmlsitemap_term.module as well? That is the one that is causing me error whenever I create a new taxonomy term in "free-tagging". I applied your fix to the xmlsitemap_node.module but that did not fix my errors:
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 ')' at line 1 query: INSERT INTO xmlsitemap_term (tid, pid, last_changed, priority_override) VALUES (15, 0, 1195045014, ) in /.../database.mysql.inc on line 172.
Thanks,
Jon
Comment #6
darren ohFixed in CVS commit 87998. Next time, please open separate a separate issue for xmlsitemap_term.
Comment #7
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #8
BLOFISTIS commentedComment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.