nextframework/next — pull request #47 by brunoaugusto (2014-10-14 16:01:27+00:00)
Title: << Click to Read >>

Next\Components\Debug\Handlers\Controllers\ExceptionController
- Fixed the namespace used in the try...catch() block which catches the
possible Next\View\ViewException thrown

Next\Controller\Dispatcher\Standard
-Fixed imported namespace for Exception Handlers

Next\DB\Query\Builder
- Changed the default behavior of SQL LIMIT

Next\File\Tools
- Changed the default behavior of Tools::cleanAndInvertPath() to not
remove the starting slash of *nix paths

Next\HTTP\Headers\AbstractHeaders
- Replaced a deprecated regex with PCRE evaluation modifer (e) with
preg_replace_callback()

Next\HTTP\Request
- Fixed a condition to whether or not add default HTTP headers when
TURBO MODE is enabled/disabled

Next\HTTP\Response
- Changed when the Response flow is aborted (if defined) helping
integration with WordPress Themes

Next\View\CompositeQueue
- Changed the acceptance condition of Composite Views to an separate
interface

Next\View\CompositeView
- Added a new interface for the feature described above

Next\View\Standard
- Fixed a wrong variable name in Standard::setFileSpec()
- Removed reference operator in Standard::assign() as part of future
performance improvement
- Fixed Standard::render() to not break the execution flow if an output
is already sent (ob_get_lengh() check) preventing premature abort when
in a WordPress Theme
- Changed the way a classname is obtained in Standard::findFileBySpec()
because of differences produced by basename() function in *nix and
Windows environments
- Minor doc-block changes, also in Standard::findFileBySpec()

Other changes
- Added new dummy template file for HTTP Response Code 500