Hi!

I going to update my sites to xmlsitemap-6.x-1.0-beta5. I do a clean xmlsitemap install on every site. I running my sites with multiste installation. Every sites has got own database and own files directory. The first site everything works fine, but when I trying to install xmlsitemap on the second site I gave the following errors:

    * user warning: Table 'xmlsitemap_node' already exists query: CREATE TABLE xmlsitemap_node ( `mid` INT NOT NULL auto_increment, `pdata` INT unsigned NOT NULL DEFAULT 0, `sdata` INT unsigned NOT NULL DEFAULT 0, `language` VARCHAR(12) NOT NULL DEFAULT '', `status` INT NOT NULL DEFAULT 1, `previously_changed` INT unsigned NOT NULL DEFAULT 0, `changed` INT unsigned NOT NULL DEFAULT 0, `priority` FLOAT NOT NULL DEFAULT 0.5, `priority_override` FLOAT NOT NULL DEFAULT -2, PRIMARY KEY (mid), UNIQUE KEY link_pdata (pdata), INDEX link_language (language), INDEX link_status (status), INDEX link_changed (changed), INDEX link_priority (priority) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /adat/3w/drupalhat_multi/includes/database.inc on line 515.
    * user warning: Table 'kokastanya.xmlsitemap_taxonomy' doesn't exist query: SELECT COUNT(*) FROM xmlsitemap_taxonomy WHERE status = 1 AND (priority_override = -2 OR priority_override >= 0) in /adat/3w/drupalhat_multi/sites/all/modules/xmlsitemap/xmlsitemap_taxonomy/xmlsitemap_taxonomy.module on line 187.
    * user warning: Table 'kokastanya.xmlsitemap_taxonomy' doesn't exist query: SELECT COUNT(*) FROM xmlsitemap_taxonomy WHERE status = 1 AND (priority_override = -2 OR priority_override >= 0) in /adat/3w/drupalhat_multi/sites/all/modules/xmlsitemap/xmlsitemap_taxonomy/xmlsitemap_taxonomy.module on line 187.
    * user warning: Table 'kokastanya.xmlsitemap_taxonomy' doesn't exist query: SELECT COUNT(*) FROM xmlsitemap_taxonomy WHERE status = 1 AND (priority_override = -2 OR priority_override >= 0) in /adat/3w/drupalhat_multi/sites/all/modules/xmlsitemap/xmlsitemap_taxonomy/xmlsitemap_taxonomy.module on line 187.

Could you please help me? Is it a bug? Only the xmlsitemap gives me this errors, the other modules works fine - woopra, adsense, cck, views, etc...

Comments

avpaderno’s picture

About the problem of the xmlsitemap_node being reported to be already installed, I can only thing to two causes: the table is shared between all the sites, or the update process didn't conclude successfully.

The other problem you are talking of is already known, and it has been fixed in the 6.x-1.x-dev version that is the base for the next beta6.

xmarket’s picture

Thanks for your reply!

I do the following update process:
1. disable the xmlsitemap modul
2. remove the xmlsitemap modul
3. remove the old files
4. upload the new files
5. run update.php - I updated more modules too
6. enable the new xmlsitemap module

And one more thing: I installed the very first time xmlsitemap on this site which gave me the reported errors. So the xmlsitemap table never existed before in this database. I gave the same error on the other site too, expect which I installed first the xmlsitemap modul.

Is it a good idea if I run once the update.php?

avpaderno’s picture

To run update.php is always a good idea, and it avoids you any problems; even if most of the times it seems useless, it's the right thing to do to avoid any problems.

This is my opinion; feel free to accept it, or disagree with it.

Anonymous’s picture

RE: update.php - IMO

If installing a fresh installation there is no reason to execute update.php. If installing dev->dev or beta->dev or dev->release it may or may not be necessary but typically if you would follow the instructions found at #379854-128: The site map is not being populated it should be the same as a fresh install.

xmarket’s picture

I will wait for the tomorrow dev release, and I try it again. I will let you know what happening tomorrow.

xmarket’s picture

Status: Active » Fixed

Hi!

I installed the 6.x-1.x-dev (2009-May-27) release, and all of the problems disappeared. :D Thank for the good work! ;)

Status: Fixed » Closed (fixed)

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