Hi,

after running update.php I got the following message:

user warning: Unknown column 'max_filesize' in 'field list' query: INSERT INTO xmlsitemap_sitemap (smid, context, updated, links, chunks, max_filesize) VALUES ('NXhscRe0440PFpI5dSznEVgmauL25KojD7u4e9aZwOM', 'a:0:{}', 0, 0, 0, 0) in /var/www/vhosts/mysite.com/httpdocs/includes/common.inc on line 3538.

Best,
Tobias

CommentFileSizeAuthor
#1 1374888-1-updates-using-scheme-definition.patch5.93 KBhanoii

Comments

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Version: 6.x-2.0-rc1 » 6.x-2.x-dev
Priority: Normal » Critical
Status: Active » Needs review
StatusFileSize
new 1374888-1-updates-using-scheme-definition.patch5.93 KB

I also found this, and you end up without an actual sitemap after upgrade which is not great.

Attached is a patch that solves this. What I think that happened is that the max_filesize was added to the schema but not to the other place in which the table was recreated on the update procedures. Right now I am using an approach which uses the definition scheme everywhere so there this kind of errors are less likely to happen now or in the future.

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Title: Update from 6.x-1.2 to 6.x-2.0-rc1: user warning: Unknown column 'max_filesize' in 'field list' query » Update from 6.x-1.2 to 6.x-2.0-rc2: user warning: Unknown column 'max_filesize' in 'field list' query
Anonymous’s picture

Anonymous (not verified) commented
Priority: Critical » Normal
Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Needs work

We cannot do an update by grabbing the current schema. Each update must handle the newness as it applies to it.

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs work » Closed (duplicate)

#978398: Upgrade from 1.x to 2.x