Pierre B.

Are you instantiating the `TwigMiddleware` with the same `basePath` as you have set in Slim?

Are you sure this gets called: https://github.com/MrBrax/TwitchAutomator/blob/947956114a9002ebcbb909d1efc8b191b249ac9b/public/index.php#L57 Because if you look in the `TwigMiddleware` it gets the `basePath` from the app: https://github.com/slimphp/Twig-View/blob/3.x/src/TwigMiddleware.php#L71

You should try and do some debugging by putting a `var_dump($currentUrl)` at this line: https://github.com/slimphp/Twig-View/blob/3.x/src/TwigRuntimeExtension.php#L80 As you can see, the base path is taken into consideration there.

That doesn't give me any insight on what's going on. You will need to debug what's happening in `TwigRuntimeExtension` and `var_dump($this->uri)` and `var_dump($this->basePath)`. Add those statements in the vendor source...

It seems that something is modifying the request URI and adding the basepath to it and it shouldn’t.

I think there is an issue with double invocation when resolving the middleware perhaps.. It'd be great to get a failing test case so we can fix this.

@Rarst > I am guessing CallableResolverInterface is retained for backwards compatibility so breaking changes to it are probably not an option. This is exactly why. Ultimately in Slim 5 we...

I would be open to making those methods protected for extensibility. I don't have a strong opinion on that @solventt

@odan considering Slim 4 is in a pretty stable place right now changing the method modifier to `protected` wouldn't be the end of the world. If we were at the...

Wow such an oversight on my part. I will open a PR to fix this asap. Thanks for reporting this!