• hi

    im getting error on my first page when using template and i think its for slider widget

    Warning: Trying to access array offset on value of type bool in C:\Users\mehdi-pc\Local Sites\elementor-new\app\public\wp-content\plugins\elementor\includes\base\widget-base.php on line 223

    Warning: Undefined array key -1 in C:\Users\mehdi-pc\Local Sites\elementor-new\app\public\wp-content\plugins\elementor\includes\base\controls-stack.php on line 695

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support Milos

    (@miloss84)

    Hi there,

    Thanks for contacting us and hope you are doing well and having a great day.

    To rule out the possibility of a plugin or theme conflict, please deactivate all your plugins (besides Elementor and Elementor Pro). If it solves the issue reactivate them one by one to find the culprit. If it didn’t help, switch your theme (temporarily) to a default WP theme such as Twenty Nineteen and see if it makes any difference.

    I am looking forward to hearing back from you soon.

    Kind regards,

    dremeda

    (@dremeda)

    I am getting the same plugin error on a fresh WP install, fresh Elementor / Elementor Pro, no other plugins enabled.

    Warning: Undefined array key 31 in /www/wp-content/plugins/elementor/includes/base/controls-stack.php on line 695

    • This reply was modified 1 month ago by dremeda. Reason: comment formatting
    Thread Starter Mehdi ardeshir

    (@mehdi0121)

    @miloss84
    Hi there,

    Thanks for your answer.

    This error sometimes displays, and when I refresh the page, it will be fixed.

    It is not always showing me.

    Kaeli Bunt

    (@thecraftmarketplace)

    We’re getting the same message, can’t seem to find any conflicts

    Hello,
    I have the same error. It occurred after updating Elementor and a few other plugins. After changing the PHP version to 7.4, the problem disappears. Elementor has constant problems in PHP higher than 7.4, because it officially supports only PHP up to 7.4. The problem is that 7.4 is no longer supported and hosting companies charge extra for maintaining them on servers.

    Temporary solution:
    I changed Elementor version to 3.22.3 and Elementor Pro to 3.22.1 and the problem disappeared. I did not check with higher versions – I do not have time to play. I simply reverted the version from which I was updating to 3.25.X.
    We have to wait until Elementor Team takes care of the problem.

    If you google the error, there are thousands of ready sites on the internet who have this error, I have this error on a fresh install too on the latest versions of elementor. Can anyone tell me how to solve it?

    I think I know what the cause is. I have looked at sites from google search with the same error, usually this error appears on all sites where there is a slider widget. On my sites that don’t have this widget there is no error, only where there is a widget there is an error.

    I encountered the same problem after updating Elementor, where errors were still showing on the frontend even though WP_DEBUG was set to false. After some investigation, I discovered that code duplication in my wp-config.php file was suppressing the WP_DEBUG setting, causing the errors to display.

    If you’re facing a similar issue, try adding the following lines to your wp-config.php file to properly enable debugging:

    if ( ! defined( ‘WP_DEBUG’ ) ) {
    define( ‘WP_DEBUG’, true );
    }

    if ( ! defined( ‘WP_DEBUG_LOG’ ) ) {
    define( ‘WP_DEBUG_LOG’, true );
    }

    if ( ! defined( ‘WP_DEBUG_DISPLAY’ ) ) {
    define( ‘WP_DEBUG_DISPLAY’, false );
    }

    This will:

    • Enable error logging to a file (wp-content/debug.log)
    • Keep errors hidden from visitors on the frontend

    This should help resolve the issue and prevent unnecessary error messages from displaying publicly.

    same issue (both errors) here with the media carousel on the frontend of three different homepages. just ele free 3.25.6 + ele pro 3.25.3 enabled, wp 6.7, php 8.2.18. all the usual fixes (cache, regenerate css, delete revisions etc.) didn’t helped
    saving the affected page again fixes the problem, but changing the menu or header/footer, for example, brings back the error.

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.