Upgrading

• Framework
  • Cache
  • Gatekeeper
  • Response

This guide takes you through the steps needed to migrate from Mako 5.1.x to 5.2.x.

Framework

Cache

The CacheManager::instance method will now return an instance of mako\cache\stores\StoreInterface instead of a mako\cache\Cache instance. You'll have to update any type hints where a mako\cache\Cache is expected.

Gatekeeper

Gatekeeper has been rewritten from scratch to make it easier to extend and to make it possible add authentication adapters.

The library has been moved from the mako\auth namespace to the mako\gatekeeper namespace and some classes have been renamed and/or moved internally so some changes will have to be made if your application is using type hinted dependency injection.

You must also update the namespace of the User and Group models and change your code to work with the following method name changes:

• Gatekeeper::getUserProvider() is now named Authentication::getGroupRepository().
• Gatekeeper::getGroupProvider() is now named Authentication::getGroupRepository().

The final change is that the Authentication::basicAuth() method will now always return a boolean. This change allows you to set your own message (the WWW-Authenticate header and 401 status code will still be set for you automatically).

if($this->gatekeeper->basicAuth() === false)
{
	return 'Authentication required.';
}

Response

Response headers will now be set with the case that they where defined with. If your clients adhere to the spec then no changes will have to be made.