I just updated to the 2009-01-31 version of the module, and when I did the DB update, there was one item that failed: the change that renamed the column "last_changed" in xmlsitemap_user to "changed." I figured that might be because an earlier update had changed that already, but that doesn't seem to be the case. When xmlsitemap runs, it creates lots of errors and there are no nodes in the sitemap. Here's one error message, it's obviously because of that missing change:
Unknown column 'xu.changed' in 'field list' query: SELECT u.uid, xu.changed, xu.previously_changed, xu.priority_override, SUM(xur.priority) as priority, COALESCE(ua.dst) AS alias FROM xmlsitemap_user xu INNER JOIN users u ON xu.uid = u.uid LEFT JOIN users_roles ur ON xu.uid = ur.uid LEFT JOIN xmlsitemap_user_role xur ON ur.rid = xur.rid LEFT JOIN url_alias ua ON ua.src = CONCAT('user/', u.uid) WHERE u.status <> 0 AND u.uid <> 0 GROUP BY u.uid, xu.changed, xu.previously_changed, xu.priority_override HAVING MIN(xur.priority) <> -1 OR SUM(xur.priority) IS NULL in [...]/sites/all/modules/xmlsitemap/xmlsitemap_user/xmlsitemap_user.module on line 198.
Comments
Comment #1
eagereyes commentedI just realized that the error message I copied is for xmlsitemap_user, but there is an almost identical one for xmlsitemap_node. There are also duplicate entry errors for the xmlsitemap table. Don't know if those are related, but I haven't seem them before.
Comment #2
fred0 commentedLine 72 of xmlsitemap_node.install has a typo.
It reads:
db_change_field($ret, 'xmlsitemap_node', 'last_change', 'changed',and should be:
db_change_field($ret, 'xmlsitemap_node', 'last_changed', 'changed',Note the missing d.
Comment #3
avpadernoThis has been already fixed in CVS; see the CVS repository for xmlsitemap_node.module, and CVS repository for xmlsitemap_user.module.
Comment #4
eagereyes commentedThat worked, thanks!