BugWP logo BugWP
Back to Community
Home / Community / Plugin → Spectra gutenberg blocks – website builder for the block editor

Fixing Common Spectra Plugin PHP Errors: Warnings and Fatal Issues Explained

28 threads Sep 16, 2025 Plugin → Spectra gutenberg blocks – website builder for the block editor

Content

Many WordPress site administrators using the Spectra plugin (formerly Ultimate Addons for Gutenberg) encounter PHP errors in their server logs. These errors, ranging from warnings to fatal crashes, can be alarming. This guide explains the most common causes and provides practical solutions based on community-reported issues and resolutions.

Understanding the Common PHP Errors

The error logs typically show a few repeating patterns:

  • PHP Warnings for Invalid foreach() Arguments: These frequently appear in class-uagb-front-assets.php on various line numbers (e.g., lines 121, 150, 151, 183). The warning states: Invalid argument supplied for foreach() or foreach() argument must be of type array|object, null given. These indicate the code is trying to loop through a variable that is not an array or object.
  • Fatal Errors from Null Values: Errors like Uncaught TypeError: array_merge(): Argument #1 must be of type array, null given in class-uagb-helper.php often occur after specific updates, such as version 2.6.4, and can be related to the Call-to-Action block.
  • Class Declaration Conflicts: Fatal errors such as Cannot declare class Nps_Survey, because the name is already in use point to a conflict, often with the companion Starter Templates plugin.
  • Missing Class Errors: Errors like Class 'Spectra_Block_Prioritization' not found or Class "ZipAIClassesZip_Ai_Helpers" not found suggest incomplete updates or missing files.

Why Do These Errors Happen?

These errors are typically not caused by something you did wrong. They often stem from:

  1. Plugin Update Glitches: An incomplete update or file conflict during the automatic update process can leave the plugin in an unstable state.
  2. Plugin Conflicts: Spectra may conflict with other plugins, especially other products from Brainstorm Force like Starter Templates, or object caching systems.
  3. Code Bugs: Like any complex software, Spectra can have occasional bugs introduced in new versions that trigger these warnings or errors under specific conditions.
  4. Cached Configurations: Sometimes, old, cached plugin data in your WordPress database or object cache conflicts with new plugin code.

Step-by-Step Troubleshooting Guide

Follow these steps to diagnose and resolve the issues. Always start by backing up your site and database.

Step 1: The Basic Fixes

These first steps resolve a significant number of reported issues.

  1. Update Everything: Ensure Spectra, any related Brainstorm Force plugins (especially Starter Templates), your theme, and WordPress itself are all updated to their latest versions. Many fatal errors, particularly class conflicts, are patched in subsequent releases.
  2. Reinstall Spectra: Completely uninstall the Spectra plugin and then install it fresh from the WordPress repository. This ensures all files are present and correct, fixing errors related to missing classes or files.

Step 2: Isolate the Problem

  1. Conflict Test: Temporarily disable all other plugins and switch to a default WordPress theme (like Twenty Twenty-Four). If the errors stop, reactivate your plugins and theme one by one to identify the conflict.
  2. Check Specific Blocks: For fatal errors mentioning specific blocks (like the Call-to-Action), try creating a new page with just that block to see if you can replicate the issue. If possible, avoid using that block until a fix is confirmed.

Step 3: Advanced Troubleshooting

  1. Manual Plugin Rollback: If a recent update broke your site and you cannot access the dashboard, manually roll back to a previous, stable version of Spectra.
    • Use FTP or your hosting file manager to access your site's wp-content/plugins/ directory.
    • Rename the ultimate-addons-for-gutenberg folder to something like ultimate-addons-for-gutenberg-deactivate. This will deactivate the plugin.
    • Download a previous version (e.g., 2.11.4) from the WordPress plugin advanced page.
    • Install the older version manually by uploading the ZIP file via your WordPress admin dashboard under Plugins > Add New > Upload Plugin.
    • Temporarily disable auto-updates for Spectra until a fix is released.
  2. Object Cache: If you use an object cache (like on WP Engine) and get 503 errors, try temporarily disabling it through your hosting dashboard to see if it resolves the immediate problem.
  3. Database Option (For Memory Errors): Some users reported a specific database entry causing memory exhaustion. The option spectra_blocks_count_stats in the wp_options table was the culprit. You can use a database tool like phpMyAdmin to find this option and either delete it or set its autoload value to no. Exercise extreme caution when modifying the database directly.

When to Seek More Help

If the errors persist after trying these steps, the issue might be more complex and specific to your server configuration. The next best step is to gather detailed information from your error logs and server environment to help pinpoint the cause.

Related Support Threads Support