3

I wondered if you could help.

I updated my local site to new ee 2.7 and that went swell. I pushed up my files to the server and I can get the /admin.php login page but when I press login i get this error:

A Database Error Occurred
Error Number: 1054

Unknown column 'used' in 'where clause'

UPDATE `exp_security_hashes` SET `used` = 1 WHERE `used` = 0 AND `hash` = '04ec7161468a13c61c984f39f646a76073bdab56' AND `session_id` = 0 AND `date` > 1381249552

Filename: core/EE_Security.php

Line Number: 169

Has anyone ever come across this from updating the ee cms before?

Cheers

3

When you upgraded to 2.7, do you recall the first time you accessed admin.php seeing the upgrade screen? And once the upgrade was complete, removing the installer directory?

It sounds like your db has not been upgraded. For example, open your db and check exp_security_hashes table for the 'used' column. Sounds like it is missing. Could be others things missing too if upgrade wasnt completed.

Did you follow these instructions

| improve this answer | |
  • Hey, Yeah I deleted the install directory. Should I push that back up to my live site version and update from there again or should I just add a new column 'used' in the db? – M dunbavan Oct 8 '13 at 19:15
  • dadonbike, do you think thats the best route then? – M dunbavan Oct 8 '13 at 19:42
  • I asked you four questions...1) When you upgraded to 2.7, do you recall the first time you accessed admin.php seeing the upgrade screen? - Oh and did you run it successfully? 2) And once the upgrade was complete, remove the installer directory? 3) is the used column missing 4) did you follow the upgrade instructions. I only see two answers from you. – Lloyd Hill Oct 8 '13 at 20:06
  • okay 1) yes on my local version but not on live 2) yes 3) in my db it was missing yes so I added it myself 4) yes I followed them by the book – M dunbavan Oct 8 '13 at 20:08
  • You need to run the upgrade on the live site as well, unless you have copied your db from local to live. – Lloyd Hill Oct 8 '13 at 20:12
3

Since your files transferred just fine, it's the database export/import process that failed you.

If you are transferring a database from one server to another it is ideal to do one or both of the following:

  1. Export the database you are duplicating with DROP TABLES syntax and gzipped. If you don't add DROP tables syntax, you'll just merge the tables possibly leaving unnecessary tables and columns in the replaced database.
  2. Before importing the above gzipped database to the second server, delete the second server database's tables completely. The DROP TABLES syntax will remove tables if they already exist before re-adding them, but you may have other tables that are not in the new database.
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.