Fix “Class Elementor\Core\Schemes\Color not found” Fatal Error in Elementor + ColorMag

If you are wondering what is actually broken: ColorMag’s Elementor widget base is trying to use Elementor\Core\Schemes\Color. In recent Elementor versions that class file was removed, so PHP crashes before the page can load.

Why this error shows up

Elementor used to provide a “Schemes” system for global colors and typography. In newer releases, that system was replaced with “Global” styles and the old color scheme class was removed from core.

ColorMag has extra Elementor widgets and a base class at:

/wp-content/themes/colormag/inc/compatibility/elementor/widgets/class-colormag-elementor-widget-base.php

That file still tries to access Elementor\Core\Schemes\Color. When you update Elementor to a version that no longer ships that class, you see a fatal error like the one in your log.

Most of the time this happens after:

• Updating Elementor to a major version (for example 3.26 and above) while ColorMag is still on an older build.
• Running an old child theme or custom copy of ColorMag’s Elementor files.
• Having other Elementor add ons that also rely on the removed Schemes API.

Step 1: Get your site loading again

First priority: get back into the dashboard so you can update things.

1.1 Use WordPress recovery mode if you can

• If your site shows “There has been a critical error on this website”, WordPress usually emails the admin address a special Recovery Mode link.
• Click that link. It loads the dashboard with the failing theme or plugin paused.
• Once you are in, go to Appearance → Themes and Plugins → Installed Plugins so you can update or disable items.

1.2 If you are locked out completely

If you cannot reach wp admin at all:

1. Log in to your hosting control panel and open File Manager or connect with SFTP.
2. Browse to wp-content/themes/.
3. Rename the colormag folder to something like colormag-temp.
4. Visit your site again. WordPress will fall back to a default theme so the fatal error disappears.
5. Log in to wp-admin.

Once you are in the dashboard, you can update ColorMag and Elementor safely.

Step 2: Update ColorMag and Elementor

The clean fix is to run a combination of ColorMag and Elementor that are built to work together.

2.1 Update ColorMag

1. In WordPress, go to Appearance → Themes.
2. Check for an update notice on ColorMag. If you see one, click Update.
3. If you use ColorMag Pro, make sure your license is active so you receive theme updates, then update it too.

The ColorMag team has already shipped updates to fix Elementor compatibility issues like missing Elementor\Core\Schemes\Color. Updating the theme is the main fix.

2.2 Update Elementor and add ons

1. Go to Plugins → Installed Plugins.
2. Update Elementor and, if you use it, Elementor Pro to the latest stable version.
3. Update any ColorMag companion plugins or Elementor add ons that came from your theme provider.

After all updates, clear any cache (hosting cache, caching plugin, CDN), then reload your homepage.

If the fatal error is gone and your home page loads, you can skip down to Verification. If it is still there, keep going.

Step 3: Confirm the error is theme specific

Before we dig deeper, make sure the crash really comes from ColorMag’s Elementor integration and not another add on.

3.1 Switch theme as a test

1. Go to Appearance → Themes.
2. Activate a default theme such as Twenty Twenty Four.
3. Visit the front end.

If the fatal error disappears with a default theme active, then ColorMag’s Elementor compatibility code is the culprit.

If the fatal error still mentions Elementor\Core\Schemes\Color but the file path is in a plugins/ folder instead of themes/colormag/, then another Elementor add on is also using the removed class. In that case:

• Go to Plugins → Installed Plugins.
• Deactivate Elementor add ons one by one.
• Reload the site after each deactivation until the fatal error disappears.

When you find the plugin that triggers the error, you will need to update or replace it as well.

Step 4: Emergency workaround if you cannot update ColorMag yet

If you rely on heavy ColorMag customizations and cannot update the theme immediately, you can use a temporary workaround to get the site back online while you plan a proper upgrade.

4.1 Use Elementor’s rollback feature

Elementor includes a “Rollback” tool that lets you return to a previous version.

1. In the dashboard, go to Elementor → Tools → Version Control.
2. Under Rollback Version, select a slightly older Elementor release that still included the Schemes classes (for example, the last 3.25 build).
3. Click Reinstall.
4. Clear caches and reload your site.

If the site loads and the fatal error disappears, you have confirmed the issue is the combination of “new Elementor + older integration code”.

Important: this is only a short term fix. Staying on an old Elementor version long term is a security and compatibility risk. Plan to update ColorMag and move back to a current Elementor release.

4.2 Optional: developer level shim

If you have a developer, they can add a small “shim” plugin that defines a stub Elementor\Core\Schemes\Color class for older integration code to call. That avoids the immediate fatal error, but it is a band aid and does not use the new Global Colors system.

Any such shim should live in wp-content/mu-plugins/ and be clearly marked as temporary. The long term fix is to update the theme’s Elementor integration to use Elementor’s Global Colors API instead of Schemes.

Step 5: Long term fix for custom or child themes

If you or your developer maintain a child theme or custom ColorMag based theme, you may need a permanent code level update.

5.1 Check for copied compatibility files

• Look inside your wp-content/themes/ directory for a child theme that copies inc/compatibility/elementor/ from ColorMag.
• If those files exist in the child theme, they will override the updated parent files and keep calling the removed Schemes class.

In that case, either:

• Delete the copied compatibility folder so the child theme uses the updated parent code, or
• Manually update the child’s Elementor integration to use Elementor’s Global Colors API as described in Elementor’s developer docs.

5.2 Move from Schemes to Globals (developer only)

Elementor provides a migration guide for moving from Schemes to the new Global styles system. A developer can follow that to update any custom widgets or theme code that still reference Elementor\Core\Schemes\Color and related classes.

Once that refactor is done, your theme code will be compatible with current and future Elementor releases without needing shims or rollbacks.

If you cannot tell what is wrong

If you are not sure whether the problem is ColorMag, Elementor, or a third party add on, gather a bit of context and I can help you sort it out.

Scroll down, click Continue Chat, and send me:

1. The full fatal error line you see (copy and paste it).
2. Your current versions of WordPress, ColorMag (and Pro, if used), and Elementor.
3. Whether you can access the dashboard or only see the error on the front end.
4. A quick list of any Elementor add on plugins you have installed.

Verification: how to know it is fixed

You are in good shape when:

• The fatal error no longer appears on the homepage or in the Elementor editor.
• Your site loads with ColorMag active and Elementor enabled.
• Your PHP error log no longer shows entries containing class-colormag-elementor-widget-base.php and Elementor\Core\Schemes\Color.
• You are running supported, current versions of both ColorMag and Elementor.

Still stuck?

For AI help

Hit Continue Chat below and I will help you read the fatal error, check theme and plugin versions, and choose the safest path between updating, rolling back, or patching so your ColorMag homepage loads again.

For expert human help

Scroll down to the contact form below. Enter your name, email, and WordPress needs. Atiba will get back to you as soon as possible.