Error message when I create a new taxonomy term after installing XML Sitemap 5.x-1.3:

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 (160, NULL, 1197660304, ) in /xxx/yyy/public_html/zzz/includes/database.mysql.inc on line 172.

Drupal 5.1

Comments

d_hall’s picture

A posssibly related issue (one that did not exist before we installed XML Sitemap) is the logging of numerous Page Not Found errors, where the "Location" URL of the page not found is a nine-digit string of numbers, with an existing page on the site as the referrer:

For example:

http://www.drupalsite.com/513947937

darren oh’s picture

Status: Active » Postponed (maintainer needs more info)

5.x-1.3 is no longer supported. Please try the latest version.

d_hall’s picture

Version: 5.x-1.3 » 5.x-1.4

Just installed 5.x-1.4 and ran the database upgrade script. Then added a taxonomy term. Same problem:

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 (161, NULL, 1198023037, ) in /includes/database.mysql.inc on line 172.

MySQL client version 4.1.22

budda’s picture

Priority: Normal » Critical

Same problem here. Happens everytime I add a new term to a vocabulary.

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 (82, NULL, 1209396308, ) in /var/www/html/drupal-5.0/includes/database.mysql.inc on line 172.

seems like 'priority_override' is not being defined/picked up during the insert. The field doesn't even appear on the taxonomy add term forms - like it does on other forms.

This bug is preventing taxonomy terms being stored in totally - rendering the taxonomy system broken in Drupal!

pnlnl’s picture

Confirming on this one... I am getting this error message, and I am getting another saying something about duplicate, sorry but i don't have the full message now because i removed the module, and i remember that i got this message right after enabling the module, if it helps, i can re-install the module, and give you the full message.
I am speculating here that it has something to do with multiple url aliases and the pathauto module, I had and still have enabled the option in the pathauto module to leave the old alias working if a new one is created for the same node. If budda or d_hall can confirm that he has the same configuration, maybe we'll have something under our hands.

darren oh’s picture

The only thing I can imagine is that the default priority for your vocabulary is an empty string. See if re-saving your vocabulary fixes it.

darren oh’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Please re-open if you have more information.

edvanleeuwen’s picture

Version: 5.x-1.4 » 5.x-1.6
Status: Closed (fixed) » Active

I have re-opened this issue and changed the version. I got this message when I added a taxonomy term. The term itself is properly added to the taxonomy.

Changing the weight and resavind does not fix it:

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 = 23' at line 3 query: UPDATE xmlsitemap_term SET pid = NULL, last_changed = 1219701313, previously_changed = last_changed, priority_override = WHERE tid = 23 in /mnt/web4/40/03/51694503/htdocs/includes/database.mysql.inc on line 172.

Please help.

edvanleeuwen’s picture

Status: Active » Fixed

Just did a de-install and install of the component and everything seems fine now.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

jenlampton’s picture

Component: xmlsitemap_term » xmlsitemap.module
Priority: Critical » Minor
Status: Closed (fixed) » Active

@Darren Oh,

You were exactly right, the term priority was not set correctly. It seems that setting the priority value in that query is restricted by the permission "override term priority" and users who do not have that permission get this SQL error when adding new terms.

Jen

edvanleeuwen’s picture

Status: Active » Closed (fixed)