1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.2 1.1.2 to 1.2.1 - can't login to upgrade

Discussion in 'Installation, Upgrade, and Import Support' started by Jon W, Sep 5, 2013.

  1. Jon W

    Jon W Well-Known Member

    Anyone know of a reason why I wouldn't be able to upgrade from 1.1.2 to 1.2.1?

    I just get stuck on the login page when trying to upgrade.
     
  2. Mike

    Mike XenForo Developer Staff Member

    Not accepting cookies or an invalid cookie path? Only things I could think of.
     
  3. Jon W

    Jon W Well-Known Member

    The config.php file contains the following:
    Code:
    $config['cookie'] = array(
        'prefix' => 'gbwim_',
        'path' => '/',
        'domain' => '.gbw.im'
    );
    Is there some reason why the upgrade process wouldn't accept these settings?
     
  4. Mike

    Mike XenForo Developer Staff Member

    Well, assuming that the domain is correct, I don't see any reason in particular it wouldn't work. If you open up the developer/network tools when logging in, can you see the cookie being set after logging in and then being sent with the subsequent request?
     
  5. Jon W

    Jon W Well-Known Member

    No, there is no setCookie in the response headers.
     
  6. Jon W

    Jon W Well-Known Member

    If I am logged into the Admin Control Panel before I upload the 1.2.1 files, I can do the upgrade no problem. It is only if I try to log in as part of the upgrade process if I am not logged in already.
     
  7. Mike

    Mike XenForo Developer Staff Member

    It's probably worth double checking that all the new files are in place.
     
  8. Jon W

    Jon W Well-Known Member

    Problem solved. :oops:
     
  9. Jon W

    Jon W Well-Known Member

    Actually, might just be working now because I've completed the upgrade process. Might still be an issue.

    I'll try on a fresh install and see if I can replicate it again.
     
  10. Jon W

    Jon W Well-Known Member

    Finally realised that I was trying to upgrade from a different domain to where the cookie was being set. Oops. :oops:

    Thanks for your help @Mike.
     
    CyclingTribe likes this.

Share This Page