I am trying to upgrade from Limesurvey 5.1.4 to 6.3.5. Not using comfort update. I replaced the Limesurvey web directory (old one) with the new one and migrated the config.php file.

When I then access my site I get the following error:
500: Internal Server Error CDbCommand failed to execute the SQL statement: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'expires' in 'where clause' I'm guessing...maybe...the upgrade is not quite as simple as I was hoping...? I found some similar, not quite the same, inquiries on the site here but none included replies that would point me in the right direction. Any advice and/or help will be much appreciated.

Jason

Details of my installation are:
​​​​

• LimeSurvey version
  5.1.4
• LimeSurvey build
  210824
• Operating system
  Linux (Ubuntu)
• PHP version
  7.4.33
• Web server software
  nginx/1.18.0
• Web server info
  HTTP/1.1
• Database driver
  mysql
• Database driver version
  mysqlnd 7.4.33
• Database server version
  MariaDB-1:10.5.22

Odd...not directly related to my inquiry but why can I not add a line break in my post? I tried to edit to add a line break and got a message saying my post was rejected because it was determined to be spam...huh!

Can you test with this patch : github.com/LimeSurvey/LimeSurvey/pull/3607/files

If it's OK : we can merge it finally …

Thanks, will do. First, however, I've just realized that my upgrade method was incorrect.

manual.limesurvey.org/upgrading_from_a_previous_version

I will follow these directions, try again, and then apply the patch if the error continues.

Thanks again for the quick reply.

jlhollowell wrote:

Thanks, will do. First, however, I've just realized that my upgrade method was incorrect.
 

Oh yes : you NEED security.php (or add it in your config.phh (i do that personnaly, then one file have all)

Else /upload can be done after

Thanks again. I guess the error was simply related to the fact that I did not upgrade properly. I copied over security.php and the upload directory and tried again and everything worked without issue.

Sorry for the false alarm and thanks for your help.

If you are not connected at admin part : the issue didn't appear.

It's maybe the reason here it work after.