Plugin report Fatal Error on itself

  • Resolved Polaris

    (@namrur)


    5 months, 2 weeks ago

    PHP Fatal error: Uncaught Exception: No route defined for this Routes : get_terminal_settings in /home/go/mydomain.com/wp-content/plugins/debug-log-config-tool/app/Router.php:77 #0 /home/go/mydomain.com/wp-content/plugins/debug-log-config-tool/app/Classes/AjaxHandler.php(23): DebugLogConfigTool\Router->direct(‘get_terminal_se…’, ‘GET’) #1 /home/go/mydomain.com/wp-includes/class-wp-hook.php(341): DebugLogConfigTool\Classes\AjaxHandler->handleRequest(”) #2 /home/go/mydomain.com/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(”, Array) #3 /home/go/mydomain.com/wp-includes/plugin.php(522): WP_Hook->do_action(Array) #4 /home/go/mydomain.com/wp-admin/admin-ajax.php(192): do_action(‘wp_ajax_dlct_lo…’) #5 {main} thrown in /home/go/mydomain.com/wp-content/plugins/debug-log-config-tool/app/Router.php on line 77

Viewing 1 replies (of 1 total)
  • Plugin Author Lukman Nakib

    (@pyrobd)

    1 week, 1 day ago

    Hi @namrur,

    Thanks for filing this.

    The stack trace shows the plugin’s internal router throwing on the get_terminal_settings route.

    That route exists in current builds. What you hit was an earlier 3.0.x version where the route had been removed during the 3.0.0 rewrite and had not yet been re-added.

    Version 3.0.6 hardens the router so any unknown-route hit now returns a JSON 404 instead of throwing a fatal error. The get_terminal_settings route itself is also registered in the current build.

    Please update to 3.0.6.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.