Hi there,

I've recently started getting this error on just about every page... I can't say what set it off or exactly when it started. I've copied the error here, replacing my database name and path to Drupal root with and
.

user warning: Table '_xmlsitemap' doesn't exist query: SELECT COUNT(xsm.loc) FROM _xmlsitemap xsm INNER JOIN vdrupal_system s ON s.name = xsm.module WHERE s.type = 'module' AND s.status = 1 AND xsm.changefreq <> 0 AND xsm.changed <> 0 AND (xsm.priority >= 0 AND xsm.priority <= 1) in
/sites/all/modules/xmlsitemap/xmlsitemap.module on line 283.

Can anyone tell me what this is?

Comments

jessia’s picture

jessia commented

Okay, let's try that again:

user warning: Table '<database>_xmlsitemap' doesn't exist query: SELECT COUNT(xsm.loc) FROM <database>_xmlsitemap xsm INNER JOIN vdrupal_system s ON s.name = xsm.module WHERE s.type = 'module' AND s.status = 1 AND xsm.changefreq <> 0 AND xsm.changed <> 0 AND (xsm.priority >= 0 AND xsm.priority <= 1) in <path to Drupal root>/sites/all/modules/xmlsitemap/xmlsitemap.module on line 283.

Anonymous’s picture

Anonymous (not verified) commented
Category: bug » support

How did your vdrupal_xmlsitemap table become missing? Only you (or someone with access to your system) can answer that question by looking in log files and such.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Error "Table <xx> doesn't exist query: SELECT COUNT(xsm.loc)" » Table doesn't exist query error
jessia’s picture

jessia commented
Status: Postponed (maintainer needs more info) » Active

I don't know... I didn't delete it or change the path or do anything with XML Sitemap except set it up and then perhaps upgrade it (I can't remember).

There's another error I'm getting. I'm not sure if it's related or not, but I'll post it here:

user warning: Unknown column 'nid' in 'field list' query: INSERT INTO vdrupal_xmlsitemap_node (nid, changed, previously_changed, comment_ratio, priority_override) VALUES (317, 1246458935, 1246458935, 0, -2) in <path>/includes/common.inc on line 3423.

Can you suggest where in the logs to look?

Anonymous’s picture

Anonymous (not verified) commented

With the extra information it sounds to me as if you've mixed versions somehow. All I can suggest is you follow the instructions at http://drupal.org/node/501912 and reinstall.

The log files you would need would be more at the system level.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)
9svn6’s picture

9svn6 commented

I also got the same error when updating from beta5 to beta6:

I got these errors when running the update script:

* user warning: Multiple primary key defined query: ALTER TABLE xmlsitemap_node ADD `nid` INT unsigned NOT NULL DEFAULT 0, ADD PRIMARY KEY (nid) in /home/<username>/public_html/includes/database.mysql-common.inc on line 298.

* user warning: Table '<database>_drupal.xmlsitemap' doesn't exist query: SELECT COUNT(xsm.loc) FROM xmlsitemap xsm INNER JOIN system s ON s.name = xsm.module WHERE s.type = 'module' AND s.status = 1 AND xsm.changefreq <> 0 AND xsm.changed <> 0 AND (xsm.priority >= 0 AND xsm.priority <= 1) in /home/<username>/public_html/sites/all/modules/xmlsitemap/xmlsitemap.module on line 283.

And this error on the top of admin pages:

user warning: Table '<database>_drupal.xmlsitemap' doesn't exist query: SELECT COUNT(xsm.loc) FROM xmlsitemap xsm INNER JOIN system s ON s.name = xsm.module WHERE s.type = 'module' AND s.status = 1 AND xsm.changefreq <> 0 AND xsm.changed <> 0 AND (xsm.priority >= 0 AND xsm.priority <= 1) in /home/<username>/public_html/sites/all/modules/xmlsitemap/xmlsitemap.module on line 283.
9svn6’s picture

9svn6 commented

I reinstalled it with the link above and it works now not sure why the update messed it up.

Anonymous’s picture

Anonymous (not verified) commented

@9svn6: The reason is that you can't get a working version by upgrading from beta5 (or any other previous 6.x version) to beta6 other than doing a complete reinstall.

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Fixed

Since I've just released RC1 and I haven't heard a response from the OP to the questions I'm closing this issue as fixed.

jessia’s picture

jessia commented

I completely removed the old version and switched to RC1. No problems. Thanks!

Status: Fixed » Closed (fixed)

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