Upgrading from 5.x to 6.0

Summary

The changes you need to port into your project when moving from Dotkernel API 5.x to 6.0, each linked to the pull request that introduced it. This release reorganised shared logic into the Core module, refactored handlers and services, introduced route grouping, and replaced Twig with a custom templating solution.

Details

You can find a complete list in Changelog

FAQ

Q: Which change in 6.0 is most likely to break my code?

A: Moving common logic into the Core module, together with the handler and service refactoring. Namespaces and constructor signatures changed, so your own handlers and services need updating. See Core and App.

Q: What replaced Twig for templating?

A: A custom templating solution shipped with Dotkernel. Templates that relied on Twig syntax need to be rewritten. See Rendering and sending emails.

Q: Why was the /security/token endpoint split in two?

A: To separate issuing a token from refreshing one, which makes each endpoint's request and response contract explicit. See Token authentication.

Q: What does "inject InputFilters in handlers" change for me?

A: Input filters are now resolved from the container and injected rather than constructed inside the handler. See Injectable input filters.

Q: Do I need to regenerate my OAuth2 keys?

A: Keys are generated automatically when cloning the project from 6.0 onward. Existing installations can keep their current keys.

On this page