Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi Hesadanza can you let us know what other plugins you have also installed and updated or upgraded recently?

    Please review the following questions.

    • Are all your plugins compatible with WordPress 4.0?
    • Is your theme compatible with WordPress 4.0?

    Thank you

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Hi Hesadanza,
    I just tried a test on WP4.0 specifically to observe the rename login feature and all seems to work fine on my site.
    It is probably not the rename login feature causing your issue.
    Which of the other AIOWPS features do you have enabled?

    Thread Starter Hesadanza

    (@hesadanza)

    Hmm.. yea, maybe it’s not the rename login feature that’s breaking my site… I have a bunch of other plugins. I’ll need to find which one is causing the problem.

    Plugin Contributor wpsolutions

    (@wpsolutions)

    You should also check your server logs because they can often reveal useful information.

    I had almost the same experience today. This upgrade seems to force a logout when it’s done.

    After upgrading to v4.0, both my custom admin-url and the regular /wp-admin/ gave 404. (as it should)

    Anyway, I solved it by logging into FTP, renaming the all in one-plugin folder, logging in via /wp-admin/ and then renaming the plugin-folder back to what it was earlier.

    After that, everything seems to work as before, I can once again login via the custom admin url.

    After WP4.0 upgrade, when it logs you out, simply manually type in your custom admin login URL in the browser’s address bar then log into the site.

    mra13: As I wrote, that didn’t work for me. I had to disable the all in one security-plugin to be able to log back in. (via the regular /wp-admin/ url)

    Then I enabled the plugin again and everything has worked since.

    Thread Starter Hesadanza

    (@hesadanza)

    I think I found what was causing the blank page after login. Users are reporting that if the php5-hash module is not installed on their server that this will happen. Apparently this hash() PHP function is a new requirement for WP 4.0. I’m pretty sure this is causing the issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Upgrading to WP 4.0 breaks renamed login’ is closed to new replies.