PHP Error in AAM: array_key_exists()

  • Resolved nhwp

    (@nhwp)


    6 years, 10 months ago

    An error being triggered by AAM (Advanced Access Manager) seems to be solved by deactivating Monster Insights. See the conversation on the AAM support forum. Several people have found the same solution: deactivating Monster Insights.

    The plugin developer reports there’s an issue with the array of capabilities being provided?

    Can you help?

    Thanks.

    • This topic was modified 6 years, 10 months ago by nhwp.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author chriscct7

    (@chriscct7)

    Hi there,
    We’re working on providing a pull request for them. Their plugin isn’t handling the conversion of meta capabilities to an empty requirement set of primitive capabilities correctly.

    -Chris

    Same issue here. Any help would be greatly appreciated.

    Kind Regards

    Javier

    Plugin Author chriscct7

    (@chriscct7)

    There’s 2 bugs that cause this as it turns out. One is in MonsterInsights, which is patched in 6.2.8 (just released). Another is in their plugin that they haven’t yet accepted our pull request for, but is more of an edge case

    -Chris

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP Error in AAM: array_key_exists()’ is closed to new replies.

Tags