Major AAM 7 Release

# Overview

We are excited to launch the official Advanced Access Manager (AAM) version 7!

This major AAM release introduces the unique access management framework specifically designed for developers. We've received numerous inquiries from users asking how to utilize the AAM API to implement use cases not currently supported. These requests have driven us to create a groundbreaking PHP framework that simplifies the management of access to WordPress website resources.

Our existing AAM system already saves developers an average of 80 hours of development work by utilizing the AAM API. Now, with version 7, we're streamlining this process even further by making the framework more user-friendly, cohesive, and backed by official documentation. This step is crucial in positioning AAM as the go-to tool for WordPress access control management.

Through our testing we also observed that AAM 7 is approximately 10% faster and requires less memory, which is a huge improvements for websites that operate at scale.

# Breaking Changes

AAM 7 represents a total backend rewrite, with many features either restructured or removed. The most significant internal change involves how the plugin's settings are stored in the database, making thorough regression testing highly recommended after upgrading to ensure everything functions as expected. Below is an overview of the key breaking changes:

• Database Changes: The structure of data for access controls and configurations in the database has been completely overhauled. An automated migration script will be provided to convert settings from AAM 6 to the new AAM 7 format. However, not all settings will be covered by this script.
• JSON Access Policies: Significant changes have been made to JSON access policies, simplifying the format and removing unsupported resources such as Plugin, Site, and UserLevel. Please refer to the JSON documentation for detailed information about these updates.
• Core Changes: Support for WordPress core level_x capabilities has been removed, as it is no longer supported by WordPress. Consequently, the "User Levels" service has been replaced by the "Users & Roles Governance" service.
• Premium Add-On Compatibility: Free Advanced Access Manager 7 is not compatible with premium add-on version 6. Both the free and premium plugins must be upgraded to version 7 for proper functionality.

# Troubleshooting

AAM 7 is a complete backend rewrite. While we’ve tested extensively, unexpected bugs may still occur due to AAM’s complexity. We’re committed to addressing all issues promptly.

If AAM 7 caused problems on your production site, please:

1. Document the issue (notes, screenshots, or video). Export your AAM settings (go to the AAM page → "Settings" tab → Export AAM Settings).
2. Check your server’s PHP error log for any AAM-related errors.
3. Email all details to support@aamplugin.com.
4. To stabilize your site, you can downgrade to version 6.9.51 via the "Advanced Options" section on this page.

# Common Issues

Below are common issues observed after major upgrades and how to address them:

• Fatal error: Class "XYZ" not found. This usually means the AAM plugin was corrupted during the upgrade (some files weren’t properly replaced). To fix it, sFTP into your server, delete the /wp-content/plugins/advanced-access-manager folder, and reinstall AAM from the official WordPress plugin repositoryopen in new window.

• White screen or HTTP 500 error. This suggests a fatal error - likely due to a corrupted plugin or compatibility issue. Check your PHP error log and email us the details. You can also downgrade to the previous stable versionopen in new window in the meantime.

• Memory allocation fatal error. This may indicate an infinite loop in the code that causes crash. sFTP into your server, delete the AAM plugin folder, and contact us right away. We’ll help diagnose and fix the issue promptly.

• Previously restricted resources are no longer protected. Export your AAM settings (AAM → Settings → Export AAM Settings) and email them to us with a description of what’s not working. We’ll review your setup and offer a fix.

# Issues Priority

While we are committed to resolving all reported issues in a timely manner, we want to set clear expectations about how we prioritize them. Below is a list of issue types in order of priority:

1. Fatal errors, warnings, and notices – Any PHP errors caused by the AAM plugin are our highest priority. These are typically addressed within 24 hours.
2. Security concerns – Any potential vulnerabilities or behavior that could lead to a security issue are treated with top urgency. We aim to review and respond within 24 hours.
3. Feature behavior differences between AAM 6 and AAM 7 – If you notice that certain features behave differently in AAM 7 compared to AAM 6, please provide detailed documentation along with your exported AAM settings. We will review the information and respond within 3 business days with our findings and recommendations.