• Resolved hmclean

    (@hmclean)


    After updating to v. 1.2.0 my website uptime manager sent a message that my website was status 500. Since I was still logged in to my site, I could continue to work on it and could see the front end. But from another browser, not logged in to the site, the message was “you do not have permission to access that page”.

    I had updated quite a few plugins, so I deactivated all and the reactivated one-by-one. The only plugin that affected permissions was Comment Blacklist Updater.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter hmclean

    (@hmclean)

    For the record, I re-installed v 1.1.0 from a backup. But the latest v 1.2.0 has a security fix, so it would be good to get the latest security update in a working version.

    Thread Starter hmclean

    (@hmclean)

    I checked the plugin author’s activity on this site to see if he noticed the questions and there is a pending v 1.2.1 addressing the permissions problem win WordPress trac.

    https://plugins.trac.ww.wp.xz.cn/changeset/2971173

    Plugin Author apasionados

    (@apasionados)

    This was fixed in version 1.2.1 after Mike Martin helped us to trace the problem.

    Login as an admin should always been available. Sorry for the inconvenience but on our test sites we didn’t have this problem.

    Best regards from Spain.

    Plugin Author apasionados

    (@apasionados)

    If you can’t login as some of the webmasters informed us, you have to delete the plugin via FTP and then reinstall version 1.2.1. Sorry for the inconvenience.

    Best regards from Spain.

    Thread Starter hmclean

    (@hmclean)

    the repository still has v 1.2.0 as latest version. Where can we get 1.2.1?

    Plugin Author apasionados

    (@apasionados)

    We just uploaded version 1.2.2 and now eveything appears to be correct.

    Best regards from Spain.

    Thread Starter hmclean

    (@hmclean)

    Thanks for your efforts. Just updated with 1.2.2 and all looks good.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘v 1.2.0 permissions problem’ is closed to new replies.