Hi,

having upgraded from Drupal 6 to Drupal 7, I'm trying to wipe out my XML Sitemap installation and start from scratch. When I try to uninstall the XML Sitemap node part of it, though, (the last thing before it comes to the XML sitemap tables themselves), all I get is the error message

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'subtype' in 'where clause': DELETE FROM {xmlsitemap} WHERE (type = :db_condition_placeholder_0) AND (subtype = :db_condition_placeholder_1) ; Array ( [:db_condition_placeholder_0] => node [:db_condition_placeholder_1] => book ) in xmlsitemap_link_delete_multiple() (line 690 of /home/wins/toegw/nschloe/public_html/sites/all/modules/xmlsitemap/xmlsitemap.module).

Cheers,
Nico

Comments

ecksley’s picture

ecksley CreditAttribution: ecksley commented

same thing here. Did you ever figure it out?

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Category: bug » support

I'll give it this guess, you are updating from 6.x-1.x, upgraded to Drupal 7, then decided to upgrade to 7.x-2.x of xmlsitemap.

If this is what you did you need to manually reset the system.

  • In your favorite DB UI you need to drop all tables beginning with xmlsitemap.
  • In your favorite DB UI you need to find all rows in the system table whose name column contains values like 'xmlsitemap%' and delete them.
  • In your favorite DB UI you need to find all rows in the variable table whose name column contains values like 'xmlsitemap%' and delete them.
  • Go back to admin/modules, refresh the page if you're already in it, and select the xmlsitemap modules you want enabled.
robcarr’s picture

robcarr
Primary language English
Location Perthshire, Scotland
CreditAttribution: robcarr commented

Thanks @earnie - your reset manually uninstalled the module

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Component: xmlsitemap_node.module » Other
Status: Active » Postponed

I'm leaving this open in postponed status for the documentation of the issue. Hmm... maybe I'll request a new Category of documentation, it would be nice to use issues such as these as documentation without the need to copy the information elsewhere.