Activity
From 2009-11-02 to 2009-12-01
2009-12-01
2009-11-30
-
23:00 Feature #5149 (Resolved): Support counting objects in persistence queries
- Applied in changeset r3532.
-
22:21 Revision 33c5457b: [+API] FLOW3 (Persistence): The QueryInterface now has a count() method for low-overhead counting of objects. Resolves #5149.
-
22:00 Bug #5171 (Resolved): Property Mapper: different action required when identity query returned more than 1 object
- Applied in changeset r3531.
-
22:00 Bug #5589 (Resolved): InitalizeActions typo in FLOW3 Manual
- Applied in changeset r3530.
-
19:13 Bug #5589 (Accepted): InitalizeActions typo in FLOW3 Manual
-
19:06 Bug #5589 (Resolved): InitalizeActions typo in FLOW3 Manual
- The FLOW3 manual mentions the "initializedAction()" init method on action controllers, while the API docs contain "in...
-
21:46 Revision 87f4abaa: [~TASK] FLOW3 (Property): The Mapper now throws different exceptions if no ore more than one object were found for given identity properties. Fixes #5171.
-
21:15 Revision b6918561: [~TASK] FLOW3 (Documentation): Fixed names of initialize methods in MVC, fixes #5589.
-
19:00 Feature #5446 (Resolved): Implement PDO based Cache Backend
- Applied in changeset r3528.
-
18:56 Revision 361f5103: [~TASK] FLOW3 (Environment): Renamed getRawGETArguments() and getRawPOSTArguments() to getRawGetArguments() and getRawPostArguments().
-
18:45 Revision 2914f811: [~TASK] FLOW3 (Cache): Implemented a PDO-based cache backend, resolves #5446.
- [~TASK] FLOW3 (Cache): Renamed APCBackend to ApcBackend, some other changes and optimizations.
[+TASK] FLOW3 (Utility... -
18:00 Bug #5576 (Resolved): Cache Manager receives bloated configuration array
- Applied in changeset r3526.
-
13:24 Bug #5576 (Resolved): Cache Manager receives bloated configuration array
- The Configuration Manager gets the names and options caches configured in Caches.yaml by a setter methods. This array...
-
18:00 Feature #5577 (Resolved): Implement postprocessing and validation into the configuration manager
- Applied in changeset r3526.
-
17:38 Feature #5577 (Accepted): Implement postprocessing and validation into the configuration manager
- Realized that this will be difficult / impossible to implement because at the time the configuration is being parsed,...
-
13:28 Feature #5577 (Resolved): Implement postprocessing and validation into the configuration manager
- The Configuration Manager should provides some kind of hooks to allow the different submodules of FLOW3 to postproces...
-
17:48 Revision cc0e877a: [-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
- [~TASK] FLOW3 (Configuration): Cleaned up and refactored the Configuration Manager's loadConfiguration() method. Reso...
-
17:40 Task #5440: Security should have its own configuration file
- Instead of moving all security related options to a Security.yaml file we should only externalize the policy section ...
-
12:42 Task #5440 (Accepted): Security should have its own configuration file
-
16:03 Revision 79dadd2d: [~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).
- [~TASK] FLOW3 (Core): The cache used to cache revision data is now using the StringFrontend.
-
16:00 Task #5579 (Resolved): Replace FLOW3.yaml file by a regular Settings.yaml file
- Applied in changeset r3518.
-
13:35 Task #5579 (Resolved): Replace FLOW3.yaml file by a regular Settings.yaml file
- Historically it made sense to have a dedicated FLOW3.yaml file. However, in reality it only contains regular settings...
-
15:53 Revision ddb88dd5: [~TASK] FLOW3: Fixed some @param annotations.
-
15:40 Revision d41309c3: [~TASK] FLOW3: Fixed the failing Configuration Manager test committed in the last revision. Also removed the Blog package from the PackageStates.yaml
-
15:04 Revision fe6c6df9: [~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
- [~FEATURE] FLOW3 (Configuration): The configuration cache (usually only used in Production context) is now cleared au...
2009-11-29
2009-11-26
-
18:00 Bug #5153 (Resolved): Routing: RouterCacheAspect only converts objects in the first dimension of route values
- Applied in changeset r3513.
-
17:34 Revision bb44f822: [+BUGFIX] FLOW3 (MVC): RouterCachingAspect now converts objects to hashes recursively, fixes #5153
-
14:50 Revision cc11375b: [~TASK] FLOW3 (Security): Changed the case of the recently introduce configuration option for the hash service's encryption key: it's now hashService: encryptionKey instead of HashService: encryptionKey.
2009-11-24
-
22:20 Revision f7e01a63: [+BUGFIX] FLOW3 (AOP): Added safeguard against missing class and method name in new method, relates to #5484
-
22:00 Bug #5484 (Resolved): AOP proxy builder does not add some annotations to built proxy classes
- Applied in changeset r3500.
-
12:20 Bug #5484 (Resolved): AOP proxy builder does not add some annotations to built proxy classes
- The proxy classes retain @param annotations, but loose @return if no parameters exist and also any other annotations....
-
21:44 Revision e37f951a: [+BUGFIX] FLOW3 (AOP): The built proxy classes now retain vital method annotations, fixes #5484
- [~TASK] FLOW3 (Security): Some tweaks to the HashService, renamed generateHash() to generateHmac(), validateHash() to...
-
21:43 Revision eeca0d7e: [+BUGFIX] FLOW3 (AOP): The built proxy classes now retain vital method annotations, fixes #5484
- [~TASK] FLOW3 (Security): Some tweaks to the HashService, renamed generateHash() to generateHmac(), validateHash() to...
-
11:00 Feature #5480 (Resolved): JoinPoint should provide a method hasException()
- Applied in changeset r3487.
-
10:09 Feature #5480 (Resolved): JoinPoint should provide a method hasException()
- When implementing After advices it might be handy to test for a possible exception thrown by the target method. There...
-
10:20 Revision b91aa398: [+API] FLOW3 (AOP): Added the JoinPoint class to the supported API. Also added a new method "hasException()" to the JoinPoint implementation. Resolves #5480
- [~TASK] FLOW3 (Cache): Set the log level of flushCachesByTag to DEBUG
[~FEATURE] FLOW3 (Security): Implemented a logg... -
10:14 Feature #5481 (Resolved): Implement meaningful logging for security / authentication
- Finding out what's wrong during the authentication process can be cumbersome due to its complexity. Therefore we need...
-
09:48 Feature #3620 (Accepted): Implement a request stack
2009-11-23
-
15:33 Feature #342: Support for file uploads
- What we need (to consider):
* a form.file viewhelper
* a file validator of some sort
** applicable to traversabl...
2009-11-20
-
10:51 Revision ff446ca0: [~TASK] FLOW3 (Security): Renamed the JSBN directory from "jsbn" to "JSBN"
- [~TASK] FLOW3 (Security): Moved the JSBN License from the Resources to the Meta folder.
-
09:44 Feature #5446 (Resolved): Implement PDO based Cache Backend
- We need a cache backend which supports PDO compatible databases.
Hint: Look at TYPO3 4.3.
2009-11-19
-
17:53 Revision 2318e1c2: [~TASK] FLOW3 (MVC): Fixed a tiny error in the NotFoundController.
-
17:50 Feature #5442 (New): Destroy session / logout user on deleting an account
- On calling remove() , the Account Repository should invalidate the session (or whatever is necessary) of the given ac...
-
16:40 Task #5440 (Resolved): Security should have its own configuration file
- Currently all security related options are configured in the FLOW3.yaml configuration file. As this configuration wil...
-
14:53 Revision 9617e872: [~TASK] FLOW3 (Log): Added another safeguard to the log() method for cases when the backtrace contains insufficient information.
- [~TASK] FLOW3 (Object): Corrected an exception and its message in the Object Builder for situations in which a factor...
2009-11-17
-
22:22 Revision eac754d7: [~TASK] FLOW3 (Validation): Tiny (non-functional) fix to method documentation.
2009-11-05
-
23:00 Feature #4445 (Resolved): setfilepermissions.sh should check if parent directories are accessible
- Applied in changeset r3456.
-
22:15 Feature #4445 (Accepted): setfilepermissions.sh should check if parent directories are accessible
- It will only check but not change the permissions, this needs to be done by the user as there are multiple ways to gi...
-
22:17 Revision b0624509: [+FEATURE] FLOW3 (Core): setfilepermissions.sh now checks the path upwards for accessibility by the webserver user, resolves #4445.
-
14:41 Revision 38cbb088: [~API] FLOW3 (Log): setLogFileURL() was renamed to setLogFileUrl() in FileBackend.
- [~API] FLOW3 (MVC): redirectToURI() was renamed to redirectToUri() in AbstractController.
[~API] FLOW3 (MVC): setRequ... -
11:54 Revision 57085368: [~TASK][+API] FLOW3 (MVC): Refactored the Controller Context and how its being built in the Abstract Controller and Action Controller. The controllers now provide a method getControllerContext() which can potentially be used as a factory method for injecting a controller's current context into other objects (such as a TypoScript view).
2009-11-04
2009-11-02
-
17:29 Revision e06a52f4: Set next version number of package FLOW3 to version 1.0.0-alpha7
-
16:00 Bug #4952 (Resolved): Reflection cache of subclasses are not flushed if parent classes change
- Applied in changeset r3392.
-
15:16 Bug #4952 (Accepted): Reflection cache of subclasses are not flushed if parent classes change
-
15:30 Revision c5409c19: [+BUGFIX] FLOW3 (Reflection): If a parent class was modified, the Reflection Service will now also flush the reflection cache of classes inheriting this class. Fixes #4952
-
14:00 Bug #5185 (Resolved): ValidatorResolver fails to parse @validate annotations with complex options
- Applied in changeset r3387.
-
13:47 Revision 9d1dd7c1: [~TASK] FLOW3 (Security): Fixed a comment.
-
13:30 Revision e4bf183e: [+BUGFIX] FLOW3 (Validation): @validate annotations with complex options are parsed correctly now, fixes #5185.
Also available in: Atom