I'm getting a user warning, and I cannot find a solution for it. I don't know where this schema is for me to edit and fix.
I upgraded from XML Sitemap 1.x dev, (removed the old xmlsitemap later), to XML Sitemap 1.0 rc1.
Assuming it would work fine, but now I get warning on every page, which is quite frankly silly because I ran update.php many many times.
"user warning: Unknown column 'xsm.changed' in 'where clause' query: xmlsitemap_link_count 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 /t/modules/xmlsitemap/xmlsitemap.module on line 283."
How do I solve it?
Comments
Comment #1
executex commentedThat's really odd, the warning seems to have disappeared when I fixed the "signature_format" varchar in users database (although I have no idea if it is going to erupt in new errors in the future because I don't know what it originally looks like). Must have been related to that.
These errors are what happens when the drupal team doesn't put in code to check the integrity and schematics of the database to ensure core modules are correct (and if not correcting them automatically).
Comment #2
Anonymous (not verified) commentedCould have been a result of not following the release notes directions (also found in INSTALL.txt). Don't know what caused your issue exactly but since you no longer have it marking as fixed.
Comment #3
executex commentedLike I said I deactivated all modules like the instructions say. I did do update.php.
So far I still get this warning in the "modules" under admin.
What step could I have possibly missed?
Comment #4
avpadernoIf the same error is still appearing, then the report needs to be re-open.
Comment #5
Anonymous (not verified) commented@executex: If you look at the db schema for xmlsitemap table do you see a column named lastmod or one named changed? If you see one named lastmod it means you didn't follow the instructions to do a clean install. You could then try executing update.php and choose the 6100 change; you'll have to manually select it from the drop down list for the xmlsitemap module.
Comment #6
executex commentedWhy 6100? Shouldn't it be the 6150?
Alright 6100 did fix it.
Comment #7
avpadernoI guess that this report should be considered fixed. Feel free to reopen it if you think it's the case.