Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter ccook10

    (@ccook10)

    Hi Paul – Just checking in to see if you were able to recreate the issue we are experiencing. WP Engine has marked version 3.15.1 as a “Security Risk” which makes us a little uncomfortable to continue to use it. We would like to know if there is an update coming or if we should start seeking a workaround for this issue. Thanks!

    Thread Starter ccook10

    (@ccook10)

    Sounds good. Hopefully it is nothing major. Thanks!

    Thread Starter ccook10

    (@ccook10)

    Hi Paul – thanks for your response.

    I did a little more testing and investigating.

    All of our sites are configured to “Only approved users (Approved external users and all WordPress users)” at the network level, so we have always made sure the users for every site were in the Authorizer Approved list – because if they were not, they would get the “not allowed” message when they tried to log in.

    What I found recently is that we have some sandbox sites that are set at the network level to “Only logged in users can see the site” – and when that is the case, there are no login issues with 3.15.2.

    The issue arises when the network level configuration is set to “Everyone can see the site” but an individual subsite is configured to “Only logged in users can see the site”. This has been working fine up until the 3.15.2 release.

    So for now, we are having to roll back to version 3.15.1 on the networks that have some individual sites set to “Only logged in users can see the site”.

    Let me know if you need additional information. We appreciate your attention to this issue.

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