Hi,

I am getting error message on my D6 Admin report even though I had a clean upgrade from the DEV version.

The error message is:

" Unknown column 'changed' in 'field list' query: INSERT INTO xmlsitemap_node (nid, changed, previously_changed, priority_override) VALUES (255120, 1242982484, 1242982484, -2) in /var/www/vhosts/website/httpdocs/includes/common.inc on line 3324."

Thanks

Comments

avpaderno’s picture

Status: Active » Postponed (maintainer needs more info)

From which version did you upgrade?

Froggie-2’s picture

This is what is written in the info file of the old version:

; $Id: xmlsitemap.info,v 1.2.2.3 2008/12/14 19:02:54 kiam Exp $
name = XML Sitemap
description = Creates an XML site map in accordance with sitemaps.org specifications.
package = XML Sitemap
core = 6.x

; Information added by drupal.org packaging script on 2008-12-15
version = "6.x-1.x-dev"
core = "6.x"
project = "xmlsitemap"
datestamp = "1229300725"

Thanks

avpaderno’s picture

Uninstall, and reinstall the module that is creating the problem.
This issue will be fixed in the next development snapshot, which would be the base for the next beta4.

avpaderno’s picture

Status: Postponed (maintainer needs more info) » Active
Froggie-2’s picture

I did it already. It did not help.

avpaderno’s picture

Be sure to remove any references to the module in the {system} table, and manually remove the xmlsitemap_node table. The module creates that database field in xmlsitemap_node_install(), and if the function is executed, that field is created.

Froggie-2’s picture

Thanks. I shall try this today at office and inform you tommorrow.

Anonymous’s picture

Please follow the instructions at #379854-128: The site map is not being populated for installing this. This is much like an intra-dev release.

avpaderno’s picture

Version: 6.x-1.0-beta3 » 6.x-1.x-dev
Status: Active » Fixed

This has been fixed from the last commits done for the development snapshot, which change the database fields used by the module.

Status: Fixed » Closed (fixed)

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