Title: WordPress 7
Last modified: June 4, 2026

---

# WordPress 7

 *  [Marco](https://wordpress.org/support/users/chefspuntozero/)
 * (@chefspuntozero)
 * [1 week, 3 days ago](https://wordpress.org/support/topic/wordpress-7-4/)
 * Hey there!
   Can we soon expect **support for WP 7** for the whole Complianz suite?
 * ![:grin:](https://i0.wp.com/codecanyon.net/images/smileys/grin.png?ssl=1)
    -  This topic was modified 1 week, 3 days ago by [Marco](https://wordpress.org/support/users/chefspuntozero/).

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

 *  [nmcjosh](https://wordpress.org/support/users/nmcjosh/)
 * (@nmcjosh)
 * [5 days, 21 hours ago](https://wordpress.org/support/topic/wordpress-7-4/#post-18933674)
 * Confirming we are also having issues with WordPress 7.0. We installed the premium
   plugin, and got the error below.
 *     ```wp-block-code
       2026/06/09 14:47:32 [error] 2827305#2827305: *5977777 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /wp-includes/script-loader.php:3570Stack trace:#0 /wp-includes/class-wp-hook.php(341): wp_enqueue_command_palette_assets()#1 /wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()#2 /wp-includes/plugin.php(522): WP_Hook->do_action()#3 /wp-admin/admin-header.php(123): do_action()#4 /wp-admin/includes/plugin.php(924): require_once('...')#5 /wp-content/plugins/complianz-gdpr-premium/pro/filters-actions.php(266): delete_plugins()#6 /wp-includes/class-wp-hook.php(341): cmplz_check_upgrade_from_free()#7 /wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()#8 /wp-includes/plugin.php(522): WP_Hook->do_action()
       ```
   
 * For what it’s worth, we asked Claude to investigate and it came to this conclusion
   which seems reasonable after reviewing its findings:
 *     ```wp-block-code
       The Complianz GDPR Premium plugin fails to activate on WordPress 7.0 due to a bug in the plugin code.When the plugin is activated, it unconditionally runs a routine designed to remove the free version of Complianz if it happens to be installed. This routine calls a WordPress function (delete_plugins()) that was not designed to be used in this context — it is meant to be triggered by an explicit admin action, not run automatically during plugin activation. In WordPress 7.0, calling it this way triggers a crash deep in WordPress core before the plugin ever finishes loading.The fix is a one-line guard in the plugin source: only attempt to delete the free version if the free version is actually present. This is a bug the plugin vendor (Really Simple Plugins) needs to fix in a future release. We have identified the exact file and line number and can apply a local patch in the meantime if needed.**Impact:** The plugin cannot be activated on this WordPress 7.0 installation without either the vendor releasing a compatibility update or us applying a local patch.**Next steps:**- Apply the local patch now to unblock activation, or- Wait for an updated plugin release from Really Simple Plugins (worth filing a support ticket with them referencing WordPress 7.0 compatibility)
       ```
   
 * This error happened with and without the free version already installed.
 *  Plugin Support [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * (@antoiub)
 * [5 days, 8 hours ago](https://wordpress.org/support/topic/wordpress-7-4/#post-18934075)
 * Hi [@chefspuntozero](https://wordpress.org/support/users/chefspuntozero/) and
   [@nmcjosh](https://wordpress.org/support/users/nmcjosh/),
 * Thanks for reaching out!
 * Quick clarification on WordPress 7 support: **Complianz is already compatible
   with WordPress 7**. There are still some Compatibility API refinements we’re 
   working on internally, but the plugin itself is fully functional on this version.
 * [@nmcjosh](https://wordpress.org/support/users/nmcjosh/) , regarding the specific
   fatal error you’ve shared, this is actually the first time we’ve received a report
   of this kind, so it’s not a known issue on our end. To investigate it properly
   and roll out a fix, could you please open a dedicated support ticket at [https://complianz.io/support](https://complianz.io/support)
   using the following subject line so we can prioritize and track it correctly:
 * **Subject:** `Fatal error on plugin activation - WordPress 7.0 compatibility (
   array_key_exists on null)`
 * In the email, please include:
    - The full stack trace you posted here
    - Your PHP version
    - Whether the free version of Complianz was previously installed on the site
    - Any other active plugins that might be relevant
 * With that information, we’ll be able to look into it directly and ship a fix 
   in the next plugin release.
 * Thanks a lot for the detailed report, it really helps!
 * Best regards, 
   Antonio
 *  Thread Starter [Marco](https://wordpress.org/support/users/chefspuntozero/)
 * (@chefspuntozero)
 * [4 days, 21 hours ago](https://wordpress.org/support/topic/wordpress-7-4/#post-18934811)
 * Great! Thanks for your reply!

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwordpress-7-4%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064)
 * [Complianz - GDPR/CCPA Cookie Consent](https://wordpress.org/plugins/complianz-gdpr/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/complianz-gdpr/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/complianz-gdpr/)
 * [Active Topics](https://wordpress.org/support/plugin/complianz-gdpr/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/complianz-gdpr/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/complianz-gdpr/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [Marco](https://wordpress.org/support/users/chefspuntozero/)
 * Last activity: [4 days, 21 hours ago](https://wordpress.org/support/topic/wordpress-7-4/#post-18934811)
 * Status: not a support question