==================== 2.2.0-beta2 ==================== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Base Distribution ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPO3.Eel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ No changes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPO3.Flow ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [TASK] Update references in documentation ----------------------------------------------------------------------------------------- See https://ci.neos.typo3.org/job/typo3-flow-release/15/ * Commit: `5704ae7 `_ [TASK] Update Upgrading.txt with note about changed persistAll() ----------------------------------------------------------------------------------------- * Commit: `d7714f0 `_ [BUGFIX] Prevent invocation of protected controller methods ----------------------------------------------------------------------------------------- Currently any method with an "Action" suffix is callable via the default request handling if a corresponding route exists. For the fallback routes provided by Flow this is the case for the ``initialize*Action()`` methods that are called before the actual action invocation. This change adds a check for the visibility of an action method and only allows invocation of public methods. * Fixes: `#57410 `_ * Commit: `2221256 `_ [BUGFIX] SlaveRequestHandler must not ignore QUIT command ----------------------------------------------------------------------------------------- The ``SlaveRequestHandler`` listens for a "QUIT\\n" command but it trims the input first, removing the newline character. * Commit: `b8155cf `_ [FEATURE] Persist whitelisted objects even for safe requests ----------------------------------------------------------------------------------------- This change provides the possibility to register single objects which should be allowed to be persisted even if the current request is a "safe" request. See documentation for further explanation and an example. * Commit: `b51d10b `_ [FEATURE] Split configuration sources include non-split default ----------------------------------------------------------------------------------------- This change changes the behavior of split configuration sources to include the default non-prefixed source as a fallback for increased flexibility, allowing some packages to have split sources and others to have a single source. Also a check in the has method is made more strict. * Related: `#37854 `_ * Commit: `d9d1fd0 `_ [BUGFIX] Fix temporary path for AvailableProxyClasses.php ----------------------------------------------------------------------------------------- This fixes the temporary path used for "AvailableProxyClasses.php" for situations when a application sub context was used. Provided that the context is "Development/MyMachine", without this patch Flow would create a file "Data/Temporary/Development/MyMachine/AvailableProxyClasses.php" while all other temporary files would reside in "Data/Temporary/Development/SubContextMyMachine/". With this patch, the path will be "Data/Temporary/Development/SubContextMyMachine/AvailableProxyClasses.php" * Commit: `da46db2 `_ [BUGFIX] Fix resolving of imported collection types ----------------------------------------------------------------------------------------- This change extends the ReflectionService so that it is able to expand our custom notation for collection types:: CollectionType Background: In the Coding Guidelines we encourage developers to import namespaces in order to increase readability. With #46008 the ReflectionService is able to resolve relative and imported namespace (with #50909 this also works for abstract classes). But this does not work for our custom notation of Collection types yet. With this fix relative and imported class names are supported also for our custom notation of collection types and the above would be expanded to:: \\CollectionTypeNamespace\\CollectionType<\\ElementTypeNamespace\\ElementType> * Fixes: `#57034 `_ * Related: `#46008 `_ * Related: `#50909 `_ * Commit: `0b45aa5 `_ [FEATURE] Custom cache directory for file based cache backends ----------------------------------------------------------------------------------------- This introduces a new backend option "cacheDirectory" which allows for explicitly specifying a path to the directory where entries of a specific cache are stored. This option overrides the automatically chosen path within Flow's temporary directory. * Commit: `0c8315b `_ Revert "[TASK] Resources are published with relative symlinks" ----------------------------------------------------------------------------------------- This reverts commit 6d206c1d35324f26e8780fdad80fed466bc9f4e1 (also known as I2e84cd8f9abd41578a87791813d03e764528feb9) In a real-world Surf setup, this patch will cause invalid relative paths in the generated symbolic links. For example: The current release is in /var/www/acme.com/releases/current which would have a realpath() of /var/www/acme.com/releases/201403060101 A published resource symlink would incorrectly point to ../../../releases/20140306210347/Data/Persistent/Resources/abcdef1234 The correct path would be ../../../Data/Persistent/Resources/abcdef1234 Since there are more variations to consider (virtual host root path contains a symlink to releases/current/Web/_Resources or not) this can't be solved last minute and needs thorough testing. * Commit: `2ba78fa `_ [TASK] Fix intermittent failures in SessionTest ----------------------------------------------------------------------------------------- At time the garbageCollectionOnlyRemovesTheDefinedMaximumNumberOfSessions in SessionTest fails with "Failed asserting that 1 matches expected 5." Since the test is about making sure a maximum is not exceeded, this changes the assertion from "equal" to "less than or equal". * Commit: `d8fcd9d `_ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPO3.Fluid ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [BUGFIX] Arrays as form objects also support property paths ----------------------------------------------------------------------------------------- When having an array as form object and a dotted property notation for form fields, that dotted notation wasn't followed for no reason. Now it's possible to have a ```` if the underlying form object is ``array('product'=>array('tag'=>'somevalue'))``. * Commit: `736d07a `_ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPO3.Kickstart ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ No changes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPO3.Party ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ No changes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPO3.Welcome ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ No changes