Viewing 8 replies - 1 through 8 (of 8 total)
  • chrisc01

    (@chrisc01)

    Yes, got the same here – can’t login and just redirects to the home page with a 404. Oops.

    Thread Starter satish_ev

    (@satish_ev)

    The URLs are:
    http://blog.severeanomaly.org/wp-login.php
    http://lifezlikethat.severeanomaly.org

    I think there is a typo in the URLs I posted earlier.

    I know it is impossible to reproduce the issue without a login, however, I cannot add a new user to the database without logging in. If anyone can tell me how to set it up from the backend, I could set up a test login to debug the issue.

    chrisc01

    (@chrisc01)

    Satish, I think the problem here is generic rather than specific to your bog.

    I was also asked to upgrade the database but that should have rung the alarm bells anyway as to why it was asking. Surely going from 2.5.0 to 2.5.1 shouldn’t require a DB update.

    Teach me to actually jump in on an update when first announced.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Surely going from 2.5.0 to 2.5.1 shouldn’t require a DB update.

    It does for a security enhancement. The size of the database’s secret key was increased from 8 to 64 characters.

    Thread Starter satish_ev

    (@satish_ev)

    It appears to have cleared up. I’m not sure what happened. I re-upgraded via WPAU and everything went off without a hitch. The plugins were not automatically re-enabled, and k2 broke, but otherwise everything seems fine.

    chrisc01

    (@chrisc01)

    To access WPAU you’d have had to have logged in Satish so did you go the SQL route to establish new users?

    My login issue has been sorted. Confirm that WPAU does not reactivate plugins after the DB upgrade – or rather the option does not reappear after – but other than that, fine. WP-Cloner is broken, but that’s it on the downside so far.

    Satish, how did you run the upgrade again without logging in? I am having the exact same problem.

    s.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘2.5.1 upgrade – MAJOR problems’ is closed to new replies.