Commits

[1910 total ]
Avatar
[-API] FLOW3 (Configuration): Removed the Configuration Manager's getSettings() method! If you relied on this method please use getConfiguration() instead, but be aware that this is not an official API method. The recommended way to retrieve settings are injectSettings() methods (see manual for more information). Relates to #5577

by Robert Lemke (Using name ‘robert’) on 2009-11-30 16:48 (5 days ago)

Avatar
[~TASK] FLOW3 (Reflection): Split the cache in two parts, one using the VariableFrontend (for reflection data) and one using the StringFrontend (for simple status data).

by Karsten Dambekalns (Using name ‘k-fish’) on 2009-11-30 15:03 (5 days ago)

Avatar
[~TASK] FLOW3: Fixed some @param annotations.

by Karsten Dambekalns (Using name ‘k-fish’) on 2009-11-30 14:53 (5 days ago)

Avatar
[~TASK] Testing: Fixed some @param annotations.

by Karsten Dambekalns (Using name ‘k-fish’) on 2009-11-30 14:49 (5 days ago)

Avatar
[~TASK] FLOW3: Fixed the failing Configuration Manager test committed in the last revision. Also removed the Blog package from the PackageStates.yaml

by Robert Lemke (Using name ‘robert’) on 2009-11-30 14:40 (5 days ago)

Avatar
[~TASK] FLOW3: Fixed the failing Configuration Manager test committed in the last revision. Also removed the Blog package from the PackageStates.yaml

by Robert Lemke (Using name ‘robert’) on 2009-11-30 14:40 (5 days ago)

Avatar
[~TASK][!!!] FLOW3 (Configuration): Merged the FLOW3 settings into the generic Settings.yaml file, dropping support for the FLOW3.yaml files. This means that you need to move all your custom settings from your own FLOW3.yaml files to Settings.yaml. Note that in FLOW3.yaml files no "FLOW3:" key on the first level was necessary which now becomes mandatory in the Settings.yaml file. Resolves #5579

by Robert Lemke (Using name ‘robert’) on 2009-11-30 14:04 (5 days ago)

Avatar
[~TASK][!!!] FLOW3 (Configuration): Merged the FLOW3 settings into the generic Settings.yaml file, dropping support for the FLOW3.yaml files. This means that you need to move all your custom settings from your own FLOW3.yaml files to Settings.yaml. Note that in FLOW3.yaml files no "FLOW3:" key on the first level was necessary which now becomes mandatory in the Settings.yaml file. Resolves #5579

by Robert Lemke (Using name ‘robert’) on 2009-11-30 14:04 (5 days ago)

Avatar
[~API] TYPO3CR: Binary::read() now takes an optional third parameter to limit the number of bytes returned.

by Karsten Dambekalns (Using name ‘k-fish’) on 2009-11-29 16:46 (6 days ago)

Avatar
[~API] PHPCR: BinaryInterface::read() now takes an optional third parameter to limit the number of bytes returned.

by Karsten Dambekalns (Using name ‘k-fish’) on 2009-11-29 16:46 (6 days ago)