Back to Community
Home / Community / Plugin → Elementskit elementor addons and templates

Troubleshooting Common ElementsKit PHP Errors and Warnings

31 threads Sep 16, 2025 Plugin → Elementskit elementor addons and templates

Content

If you use the ElementsKit Elementor addon, you might occasionally encounter PHP errors, warnings, or notices. These can range from simple deprecation messages that appear in debug logs to fatal errors that crash your site. This guide will help you understand the most common issues and how to resolve them.

Common ElementsKit Errors and Their Causes

Based on community reports, here are some frequent problems:

  • Fatal Error: Cannot declare class... because the name is already in use: This often occurs due to a plugin conflict, especially if another plugin or theme uses a class with the same name. It was a known issue in older versions of ElementsKit but has been reportedly fixed in newer releases (e.g., version 3.4.2).
  • PHP Warnings: Undefined index (e.g., margin_tablet, margin_mobile): This warning often points to a compatibility issue between ElementsKit and a specific Elementor version. The error message originates from Elementor's core files but can be triggered by ElementsKit's One Page Scroll module.
  • Deprecated function warnings (e.g., get_page_by_title): As WordPress evolves, it deprecates old functions. The ElementsKit team has historically addressed these by releasing patches that replace deprecated functions with modern equivalents.
  • PHP Notices in error logs (e.g., undefined array key, attempt to read property on string): These are often non-critical notices that appear when debug mode is enabled. They indicate places in the code where variables are being used before their existence is checked, but they may not affect front-end functionality.

General Troubleshooting Steps

Before diving into specific fixes, always follow these foundational steps:

  1. Update Everything: Ensure WordPress, your theme, Elementor, and ElementsKit are all updated to their latest versions. Many conflicts are resolved in updates.
  2. Clear All Caches: Clear your browser cache, any WordPress caching plugins, server-level cache (e.g., Varnish), and CDN caches (e.g., Cloudflare).
  3. Conflict Test: The most reliable way to identify a conflict is to:
    1. Switch your theme to a default WordPress theme like Twenty Twenty-Four or Hello Elementor.
    2. Deactivate all plugins except for Elementor and ElementsKit.
    3. If the error disappears, reactivate your plugins one-by-one to identify the culprit.
    4. If the error remains, it is likely a conflict between Elementor and ElementsKit.

Solutions for Specific Errors

For "Undefined index" Warnings (margin_tablet, padding_mobile, etc.)

This is a common compatibility warning. A workaround suggested by the ElementsKit team is to disable the module that often triggers it.

  1. Go to WordPress Dashboard > ElementsKit > Modules.
  2. Find the "One Page Scroll" module.
  3. If you are not using it, disable it and check if the warnings stop.
This issue is often resolved in subsequent Elementor or ElementsKit updates.

For "Cannot declare class" Fatal Errors

  1. First, update ElementsKit to the very latest version. This specific error was addressed in an update.
  2. If updating is not possible or the error persists, perform a conflict test as described above. The conflict is often with another plugin or the theme.

For Deprecation Warnings

These warnings are common when using older PHP versions or when plugins need to catch up to WordPress core changes. While they don't usually break your site, they clutter logs.

  1. Check the ElementsKit changelog or support forums to see if a fix has been released.
  2. If a fixed version is available, update the plugin.
  3. If no fix is available yet, you can suppress deprecation notices by ensuring WP_DEBUG_DISPLAY is set to false in your wp-config.php file, though this does not fix the underlying cause.

When to Seek Further Help

If the steps above do not resolve your issue, the problem might be more specific to your setup. When seeking help in community forums, be prepared to provide:

  • The exact and complete error message from your logs.
  • Your System Info from Elementor (Elementor > System Info).
  • The steps you took to reproduce the error.
  • The steps you have already taken to try to resolve it (e.g., conflict test results).

Most issues can be resolved through careful troubleshooting, keeping software updated, and temporarily disabling conflicting plugins or modules.

Related Support Threads Support