2.0.16 update broke login

[Kestryll]

I updated my 2.0.15 install to 2.0.16 and now I can not log in, it either tells me there is a problem with my cookies or that Session verification failed.

Any ideas on what is going on?

[Illori]

maybe related to https://wiki.simplemachines.org/smf/Login_error_2.0.14 ?

[Deaks]

also how did you update?  Was it through package manager or did you make changes manually?  Did you get any errors when updating?

[Kestryll]

This was an update from 2.0.15 to 2.0.16.

I did the update through the Package manager.

[Deaks]

what theme are you using?

[Kestryll]

I'm running the standard theme right now.

A couple odd things though, at the bottom of the forum (I can see it just not log in to it) it says it's running 2.0.15 but the update said it completed.
Also when I look as Guest at the Staff it shows me as having logged in just now but also as offline.

[Deaks]

do you have a link to your forum?

[Kestryll]

http://www.calguns.org/forum/index.php

[Deaks]

it seems you are running a mixed version between 2.0.15 and 2.0.16 so something went wrong in the update.  The only thing I can suggest is manually going through the changes and seeing what ones need to be added.

https://custom.simplemachines.org/upgrades/index.php?action=upgrade;file=smf_patch_2.0.16.tar.gz;smf_version=2.0.15

This is all the file changes.  If it helps you wont need to make changes to Who.php

[Kestryll]

Oh that looks like fun...

Would it likely fix the issue to use the server file manager to 'reinstall' all the 2.0.15 files replacing any of the 2.0.16 one with the originals?
Kind of redoing the 2.0.15 update manually?

[Deaks]

yeh just download the Large Upgrade and overwrite them all, this will move you to smf 2.0.17 so the newest version and will save you needing to do a further update.  You will have to re-install the mods and any manual changes.  Also remember delete the upgrade.php you dont need it.  And PLEASE make a backup before you do anything

[Sir Osis of Liver]

Package manager makes a backup before installing a mod, it's in /Packages/backups/.  Download, unzip, upload to forum root.  It will restore the install to state it was in before update.  Uploading a complete set of files will remove all mods and customizations.  If that's not a problem, clean files is best way to go.

[Deaks]

Osis that is not good idea as he needs to upgrade, if he did that he will be back where he started and likleyhood is that the error will occur if he tries it again.  Fresh 2.0.17 files will fix the issues and patch the issues found on 2.0.16, the mods he has installed will re-install no problem

[Sir Osis of Liver]

Uploading a complete set of files will remove all mods and customizations.  If that's not a problem, clean files is best way to go.

[Deaks]

clean files is best way to go.

my words exactly clean files is the way to go and thats what my suggestion is doing, its also moving the OP forward not backwards.  You are suggesting he moves backwards and tries again backwards to an outdated software that  has known bugs, so he will go backwards to go forward with more steps specially as  the issue is likley to continue.  My suggestion is to move forward and spend the few minutes it takes to re-install the few mods that are installed.

[Kindred]

well, if you are going to replace the files with clean ones --  then go straight to the 2.0.17 files and don't bother with patches.

[Sir Osis of Liver]

Would be interesting to,know what causes this glitch.  It's been reported several times, but I've never seen it on any of the forums I've upgraded.

[Deaks]

Kestryll, its been over 2 weeks did you get this sorted?  If so what helped?  If not what have you tried since?  I have marked this as solved for now.