Fixes INP-1891 - Display PHP errors in the Phing build log
Bug INP-1894 - Extract "Change Log" code to a central place
Fixes INP-1905 - Clear the "Temp Mode" flag after the Temp Table removal from the "OnCancelEdit" event
Fixes INP-1908 - Discard template parser opened output buffers before doing a redirect
Fixes INP-1910 - Allow specifying upcoming System Log record defaults
Fixes INP-1853 - Use the "\kUtil::varDumpColorized" method in the System Log Web UI
Fixes INP-1852 - Create the "\kUtil::varDumpColorized" method
Fixes INP-1854 - Create global switch for Web Request/Session Data logging into the System Log
Fixes INP-1919 - Reset unit config cache after Module Root Category change
Fixes INP-1920 - Ensure consistent named tab preset usage
Fixes INP-1915 - Add support for IPv6 addresses
Fixes INP-1890 - Force "\kApplication::NextResourceId" method to use master database connection
Fixes INP-1912 - Show "404 Page Not Found" page on the Front-End for unaccessible events
Bug INP-1857 - Prevent recursion in the "\kUrlManager::show404" method
Fixes INP-1911 - Adjust exception message, when accessing non-existing event of an existing unit
Fixes INP-1906 - Execute "customProcessing" method in the "OnDelete" and "OnDeleteAll" events
Bug INP-1725 - Introduce secure Session Key generation/storage
Fixes INP-1894 - Extract "Change Log" code to a central place
Fixes INP-1863 - Correct PHPUnit integration
Fixes INP-1885 - Consistently use PHP binary during the Build
Fixes INP-1884 - Actualize "/system/config.php" created during the build
Fixes INP-1873 - Support MySQL 8 database collations
Bug INP-1827 - Connect a testing framework
Fixes INP-1881 - Change default Debugger URL handler to PhpStorm
Merge (5.3.x > 5.2.x): * [backported] Fixes INP-1883 - Rework URL-encoding in Debugger Report file URLs
Fixes INP-1882 - Rework URL-encoding in Debugger Report file URLs
Fixes INP-1872 - Properly handle constant absence during category cache rebuild
Fixes INP-1858 - HTML-escape data in Admin Console grids
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.