I’m not far into my first v4.x app. I got the Authentication plugin running with the AuthenticationMiddleware and noticed the Debugkit was not at the bottom of the page.
I used the ‘bigger-hammer’ fix to make sure…
Configure::write('DebugKit.ignoreAuthorization', true); Configure::write('DebugKit.forceEnable', true); $this->addPlugin('DebugKit');
This did yield a red ‘something’ in the lower right corner of the screen. I used css to pry that little thing open and found an error page rendering with this error:
Since I haven’t done anything unusual at this point it seems like the default routing should still be viable? I only have one baked controller.
bin/cake routes reports:
Indeed, the named route is missing. Admittedly I don’t have a proper working knowledge of routing, but again, I’m not off the reservation at this point.
What am I looking at here and how do I proceed?
When I add a new route at the end of the default setup (after the fallback):
$builder->fallbacks(); $builder->connect('/:controller/:action/*', ['plugin' => 'DebugKit']);
Things work. But my confusion does not end. When I look at the Routes table in the DebugKit panel:
As I said, I’m not solid on routes yet but… The final route seems to be the one that got me up an running. But its name
debugkit._controller:_action is suggesting to me that it will lead to a debugkit plugin controller?
I am operational at this point but I’d like to understand what’s going on rather than live with this opaque solution. It feels like I’m fixing my Dad’s Studebaker with a bit of tech picked up from a field in Roswell.