Support » Plugin: Responsive Menu - Create Mobile-Friendly Menu » Fatal error: Uncaught Error: Class

  • Resolved Viktor Bijlenga

    (@viktorbijlenga)


    We get a fatal error, when using the Responsive Menu plugin. It seems to be caused by a class, which doesn’t seems to be found.

    I’ve redacted the full url, since it’s a staging-site behind a VPN.

    SERVER ENV

    
    Web Server: ..................... nginx/1.16.1
    PHP: ............................ 7.4.5
    WP Memory Limit: ................ 40M
    PHP Time Limit: ................. 30
    Blocked External HTTP Requests:   None
    fsockopen: ...................... Enabled
    OpenSSL: ........................ OpenSSL 1.1.1d  10 Sep 2019
    cURL: ........................... Enabled
    Enable SSL verification setting:  No
    Opcache Enabled: ................ Enabled
    

    ERORR IN BROWSER

    
    Fatal error: Uncaught Error: Class 'ResponsiveMenu\Controllers\FrontController' not found in /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/services.php:37 Stack trace: #0 /sites/SITENAME/files/wp-content/plugins/responsive-menu/app/Container/Container.php(27): {closure}() #1 /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/services.php(42): ResponsiveMenu\Container\Container->offsetGet() #2 /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/routing.php(64): get_responsive_menu_service() #3 /sites/SITENAME/files/wp-includes/class-wp-hook.php(287): {closure}() #4 /sites/SITENAME/files/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters() #5 /sites/SITENAME/files/wp-includes/plugin.php(478): WP_Hook->do_action() #6 /sites/SITENAME/files/wp-includes/template-loader.php(13): do_action() #7 /sites/SITENAME/files/wp-blog-header.php(19): require_once('/sites/SITENAME...') in /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/services.php on line 37
    

    ERROR LOG ON SERVER

    
    020/08/27 09:53:17 [error] 23370#23370: *240 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Class 'ResponsiveMenu\Controllers\FrontController' not found in /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/services.php:37
    Stack trace:
    #0 /sites/SITENAME/files/wp-content/plugins/responsive-menu/app/Container/Container.php(27): {closure}()
    #1 /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/services.php(42): ResponsiveMenu\Container\Container->offsetGet()
    #2 /sites/SITENAME/files/wp-content/plugins/responsive-menu/config/routing.php(64): get_responsive_menu_service()
    #3 /sites/SITENAME/files/wp-includes/class-wp-hook.php(287): {closure}()
    #4 /sites/SITENAME/files/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
    #5 /sites/SITENAME/files/wp-includes/plugin.php(478): WP_Hook->do_action()
    #6 /sites/SITENAME/files/wp-includes/template-loader.php(13): do_action()
    #7 /sites/SITENAME/files/wp-blog-header" while reading response header from upstream,"GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-SITENAME.sock:", host: "SITENAME", referrer: "SITENAME/wp-admin/plugins.php?plugin_status=all&paged=1&s"
    2020/08/27 09:53:17 [error] 23370#23370: *242 open() "/sites/SITENAME/files/favicon.ico" failed (2: No such file or directory), client: 162.158.92.87, server: SITENAME, request: "GET /favicon.ico HTTP/1.1", host: "SITENAME"
    

    Any ideas on how this can be solved?

    • This topic was modified 4 months, 3 weeks ago by Viktor Bijlenga.
    • This topic was modified 4 months, 3 weeks ago by Viktor Bijlenga. Reason: better readabilty
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support expresstechsupport

    (@expresstechsupport)

    Hi @viktorbijlenga,

    I need to talk to the development team regarding these errors. I will get back to you as soon as I hear back from them.

    Regards,
    Kriti

    Hi @expresstechsupport,

    Any progress on this, or anything I can contribute for you to debug further?

    Plugin Support expresstechsupport

    (@expresstechsupport)

    Hi Viktor,

    As per the development team, they tried to replicate the issue but couldn’t. It seems like the package has gone corrupt. Also, please try with a fresh install and let us know regarding the outcome.

    If the issue happens again then we need the export file of the plugin to replicate the issue.

    Regards,
    Kriti

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