Latest Articles

DotKernel 1.8.

DotKernel 1.8.

The release of ZF 1.12.

Alerts (or Dot_Alert's) are e-mails usually sent to the site developers, these messages are sent with mail() therefore you shouldn't use them to send regular mail. Alerts should only notify you as a developer: "Hey, something's wrong here, you might want to know this!" In this article you will find out how to use the Alerts system in DotKernel, we will also go through an existing example so this can be understood easier.

In the newest version we have removed the GeoIP City integration. The City database on GeoIP 1.

It's very expensive to load configurations and settings from XML files, on every requests. First because of latency of accessing files from hard drive, second because of the XML file parsing burden.

This article is related to: Caching in DotKernel with Zend Framework Cache The variables that DotKernel cache are below: Router Router is the object that load routes (modules, controllers, actions) settings from router.xml file.

This article contains the DotKernel cache layer configuration guide. The DotKernel Caching Layer is based on Zend Framework Cache, more configuration options can be found at the following links: Zend Framework Cache Frontends Zend Framework Cache Backends Main cache settings (Cache Frontend) The main cache settings within the application.

In order to use the new Password Hashing functions , introduced in PHP 5.5 , and unify all password related functions , used for both admin and users, we did a major refactor of DotKernel codebase, in version 1.

Beginning with version 5.5 of MySQL , utf8mb4 character set was introduced, in order to better support Unicode.