ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

2.5.2 Insists on Using exp_members.remember_me

August 16, 2012 12:19pm

Subscribe [0]
  • #1 / Aug 16, 2012 12:19pm

    Waldo Jaquith

    30 posts

    A couple of days ago I upgraded from 2.2.1 (IIRC) to 2.5.2. My site broke immediately, and turning on debug mode, I found that I was getting a MySQL error, complaining that exp_members.remember_me didn’t exist. A quick review of the upgrade scripts revealed that the column had been eliminated in favor of an exp_remember_me table. As an immediate fix, I created exp_members.remember_me, where ExpressionEngine is now happily storing what I assume is a session identifier.

    Where in Expression Engine were calls to exp_members.remember_me replaced with calls to exp_remember_me? I want to fix this properly, in part because I don’t want to have the same problem with my next upgrade, and in part because I’m hoping that the solution will help to reveal the cause behind a much bigger post-upgrade problem. If I know where this upgrade script failed, then I’ll know where to start investigating.

  • #2 / Aug 16, 2012 12:33pm

    Waldo Jaquith

    30 posts

    I just noticed something quite unusual in the footer of the admin section:

    ExpressionEngine v2.5.2 - Build: date 20110801 - © Copyright 2003 - 2011 EllisLab, Inc.

    Version 2.5.2, build date August 1, 2011? I’m pretty sure that one of these two things is not true. How could those be out of sync?

    FWIW, config.php has app_version set to 252.

  • #3 / Aug 16, 2012 5:31pm

    Waldo Jaquith

    30 posts

    In solving another problem, I suspect quite strong that I’ve solved this one. Core.php had somehow not been updated which, as you can imagine, makes all kinds of terrible things happen. Why my FTP client didn’t upload that or didn’t notify me of an error, I have no idea. Anyhow, it’s not y’all’s problem! 😊

  • #4 / Aug 17, 2012 3:23pm

    Kevin Smith

    4784 posts

    Just to be sure, Waldo, I’d recommend restoring your site to the backup you took before the update and trying the update again, this time being sure that you’ve got all the files uploaded before going through with the update. Having file or database version mismatch could cause lots of problems, and they might not all present themselves right away.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases