• Resolved Malae

    (@malae)


    Hello Kaspars,

    Can you help with the following:

    [PHP Warning: include(): Failed opening '/wp-content/plugins/widget-context/vendor/composer/../../src/WidgetContext.php' for inclusion (include_path='.:/opt/alt/php74/usr/share/pear') in /wp-content/plugins/php-compatibility-checker/vendor/composer/ClassLoader.php on line 444

    PHP Fatal error:  Uncaught Error: Class 'WidgetContext' not found in /wp-content/plugins/widget-context/widget-context.php:17
    Stack trace:
    #0 /wp-settings.php(371): include_once()
    #1 /wp-config.php(104): require_once('/home/...')
    #2 /wp-load.php(37): require_once('/home/...')
    #3 /wp-admin/admin-ajax.php(22): require_once('/home/...')
    #4 {main}
      thrown in /wp-content/plugins/widget-context/widget-context.php on line 171
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Kaspars

    (@kasparsd)

    Could you please confirm if you installed the plugin from the WP.org plugin repository? That errors appears to be related to the php-compatibility-checker plugin trying to load the Widget Context plugin through its Composer autoloader.

    Thread Starter Malae

    (@malae)

    Thank you for your quick response. Yes, it was downloaded from www.remarpro.com.

    I think you are correct that the warning is caused by the PHP Compatibility plugin, although I have been using both plugins for a long time and never had this warning before. The only things that have changed are that I recently updated to PHP 7.4 and I recall your update several weeks ago. I rarely run the compatibility checker and, if the error also only occurs when it is run, then there should be no problem.

    Plugin Author Kaspars

    (@kasparsd)

    Thanks for confirming @malae!

    Failed opening '/wp-content/plugins/widget-context/vendor/composer/../../src/WidgetContext.php' for inclusion

    That path resolves to /wp-content/plugins/widget-context/src/WidgetContext.php which is correct so I’m not sure why it would fail to load that file. Could it be related to the case-sensitivity of the filenames on the webserver?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error and warnings in PHP 7.4’ is closed to new replies.