Merge remote-tracking branch 'origin/3.0' into 3.0-finders
Making it possible to build queries using an array like in Cake 2.x
Merge remote-tracking branch 'origin/3.0' into 3.0-query-array
Fixing doc block
Applying query options before triggering beforeFind
making the config method of email-transport-classes mergable into the current config value.
Condings standards fix
Correctly encode confirm handlers

With encode set to false the onclick handler will be sent through
h() regardless, making links and postLinks work again.
All tests pass in Sqlite now, additionally made more secure the way
DateDiff is translated
Apply ADmad's patch and update testConfig method according to a new specification.
correct doc blocks as per cs
Corrected translation string
Use inner join instead of a left join.

In some database servers an INNER join performs better than a LEFT join.

Fixes #3979
Allow CakeEmail::template() to disable layout rendering.

Fix the code to act as documented. Sending template('view', null) should
disable layout rendering.

Fixes #3983
Merge pull request #1516 from dmromanov/2.4-translations

Corrected translation string
Rename LogEngineCollection to LogEngineRegistry

In preparation for converting the logging collection into the newer
style registry rename the internal property and collection class.
Deprecate several Log methods.

Having both loaded/enabled modes makes Log more complex than it needs to
be. There are very few cases where you need to disable/enable loggers.
These can generally be solved by droping loggers.
Remove deprecated method use.

Stop calling deprecated features of Log.
Convert Log to use new Registry object.

Update the registry and Log to use the new Registry base class.
Remove dependency on Configure for logging.

Not using Configure to setup logging has a couple benefits.

* Using Configure creates magic at a distance. Setting things in one
  class creates effects in another.
* Loggers at bootstrap and loggers created at runtime are handled
  consistently.
* Dropped loggers don't magically re-create themselves once Log has been
  reset.
* It is still simple to create loggers using configuration files, or
  inject instances directly.

With this change we are still able to lazily load loggers once Log is
used.