TYPO3 Forge: Issues http://forge.typo3.org/ http://forge.typo3.org/themes/TYPO3/favicon/favicon.png 2013-05-22T08:23:53Z TYPO3 Forge Redmine Coordination Group - Topic #48434 (New): Topic workflow for Coordination Group http://forge.typo3.org/issues/48434 2013-05-22T08:23:53Z Robert Lemke robert@typo3.org <p>We'll need a (briefly) documented workflow for how we organize ourselves in the Coordination Group using the issue tracker</p> TYPO3 Flow Base Distribution - Story #42408 (New): Locale Detection / Selection http://forge.typo3.org/issues/42408 2012-10-26T07:03:38Z Robert Lemke robert@typo3.org <ul> <li>support for automatic locale detection</li> <li>storing locale in a cookie</li> <li>mechanism for overriding locales by user</li> </ul> TYPO3 Flow Base Distribution - Story #42407 (New): Asset Management http://forge.typo3.org/issues/42407 2012-10-26T07:02:42Z Robert Lemke robert@typo3.org <ul> <li>CDN support</li> <li>centralized JS / CSS mgm</li> <li>minifiers</li> <li>SASS support</li> <li>re-use as much concepts and code from Assetic etc. as possible</li> <li>seamlessly integrate into existing Resource framework</li> </ul> TYPO3.TypoScript - Task #41030 (New): TypoScript namespaces should have file scope, not global scope http://forge.typo3.org/issues/41030 2012-09-18T07:46:53Z Robert Lemke robert@typo3.org TYPO3.Flow - Bug #39791 (New): Reflection data of old aspect is not removed http://forge.typo3.org/issues/39791 2012-08-14T07:45:23Z Robert Lemke robert@typo3.org <p>The reflection data of a removed aspect is not removed by the file monitoring / reflection framework.</p> <p>Steps to reproduce:</p> <ol> <li>create something which can be advised, for example a command controller with a command</li> <li>create a new aspect which advises that command, for example with an around advice</li> <li>check that this advice works</li> <li>rename the aspect class and the class file name</li> <li>run the advised command again</li> </ol> <p>Expected result:<br /><pre> Uncaught Exception Warning: Invalid argument supplied for foreach() in Packages/Framework/TYPO3.FLOW3/Classes/Aop/Builder/ProxyClassBuilder.php line 315 </pre></p> <p>The reason for the error message is that the <strong>old</strong> aspect class name is passed to buildAspectContainer() which tries to get the class methods but, as the class does not exist anymore, continues working with an invalid result.</p> <p>It doesn't seem to be the fault of the file monitoring, because the file monitor does detect the change as you can see in the log file:<br /><pre> 12-08-14 09:39:12 4799 INFO FLOW3 Aspect classes have been modified, flushing the whole proxy classes cache. 12-08-14 09:39:12 4799 INFO FLOW3 File Monitor "FLOW3_ClassFiles" detected 1 changed files and 0 changed directories. 12-08-14 09:39:12 4799 DEBUG FLOW3 Reflected class names did not match class names to reflect 12-08-14 09:39:12 4799 DEBUG FLOW3 Reflecting class Acme\Demo\Test2Aspect 12-08-14 09:39:12 4799 INFO FLOW3 Reflected 1 emerged classes. </pre></p> TYPO3.Kickstart - Feature #39790 (New): Allow forward slashes where backslashes need to be specified http://forge.typo3.org/issues/39790 2012-08-14T07:28:02Z Robert Lemke robert@typo3.org <p>Typing backslashes on the command line is cumbersome because each of them needs to be escaped with an additional backslash. Therefore it would be convenient if the kickstarter would allow forward slashes as well and convert them to backslashes internally.</p> <p>This should be implemented especially for the kickstart:model command (property types are often class names) but may apply to other commands as well.</p> TYPO3.Flow - Bug #36804 (New): Orphaned entities within aggregates are not removed http://forge.typo3.org/issues/36804 2012-05-03T09:04:25Z Robert Lemke robert@typo3.org <p>Consider this example:</p> <p>An entity Image has a many-to-one or one-to-one relation to an entity Resource.<br />Image is an aggregate root and is stored in an ImageRepository.<br />Resource does not have its own repository and thus is a practically member of the Image aggregate.</p> <p>Now, if an Image object is removed, its Resource object remains in the database and can't accessed through any object or repository anymore.</p> TYPO3.Flow - Feature #29476 (New): Provider rendering time and query count for request http://forge.typo3.org/issues/29476 2011-09-05T07:22:45Z Robert Lemke robert@typo3.org <p>It would be nice if FLOW3 could calculate the rendering time and the amount of queries executed for a single request and then make that information available to the developer. A simple way to do that could be by adding an HTML comment or HTTP response header. Later on the admin tool should support it of course.</p> TYPO3.Flow - Feature #5774 (New): Package Manager should clear all cache entries tagged with %PAC... http://forge.typo3.org/issues/5774 2009-12-17T15:52:43Z Robert Lemke robert@typo3.org <p>Whenever a package is activate, deactivated or upgraded the Package Manager should flush all cache entries which are tagged with \F3\FLOW3\Cache\Frontend\FrontendInterface::TAG_PACKAGE.</p> TYPO3.Flow - Task #3755 (New): Concurrency stress testing and cache mechanism http://forge.typo3.org/issues/3755 2009-06-25T07:36:52Z Robert Lemke robert@typo3.org <p>After the first experiences and results from <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Concurrency stress test (Closed)" href="http://forge.typo3.org/issues/3582">#3582</a> we need to do some more thorough stress testing to identify race conditions in FLOW3, especially in the caching mechanism. We need to assure that especially the code caches cannot be built multiple times simultaneously which currently is seems to be not always the case.</p> TYPO3.Flow - Feature #3587 (New): Enforce validation rules for value objects already in constructor http://forge.typo3.org/issues/3587 2009-06-05T09:21:11Z Robert Lemke robert@typo3.org <p>Because the values of a value object can't be changed after instantiation, we should assure that only valid value objects exist. This should be done by validating the constructor arguments already in the constructor.</p> <p>The validation mechanism should be introduced by some aspect (@around the constructor) and throw an exception if validation fails.</p> TYPO3.Flow - Major Feature #3585 (New): Implement support for value objects http://forge.typo3.org/issues/3585 2009-06-05T09:12:04Z Robert Lemke robert@typo3.org <p>Currently value objects are not truly supported as such - but we want that.<br />This ticket consists of several sub tasks (see related issues)</p> TYPO3.Flow - Feature #3580 (New): Create an administration panel for the FLOW3 Development context http://forge.typo3.org/issues/3580 2009-06-05T08:31:35Z Robert Lemke robert@typo3.org <p>We need some kind of admin panel which is (can be) displayed on the page rendered by FLOW3 and provides some useful information to the developer. That could be:</p> <ul> <li>Information about caches, ability to flush certain caches</li> <li>Information about routing (which route matched etc.)</li> <li>Memory consumption / parse time</li> <li>Tail of certain logs ?</li> </ul> <p>The graphical design and code architecture should allow for third party packages to plugin to the panel for providing custom functionality.</p> <p>Before this ticket can be close we need (solved in separate tickets - please create some):</p> <ul> <li>A UI concept and after that, an actual design</li> <li>A rough concept for the implementation</li> <li>The actual implementation</li> </ul> TYPO3.Flow - Feature #3153 (New): Support of action based filter rules defined by annotation. http://forge.typo3.org/issues/3153 2009-04-22T15:15:40Z Robert Lemke robert@typo3.org <p>Similar to <a class="issue tracker-2 status-3 priority-3 priority-lowest closed" title="Feature: Support annotation-based validation rules in controller actions (Resolved)" href="http://forge.typo3.org/issues/3092">#3092</a> there should be a way to declare additional filter rules for the arguments of an action method:</p> <pre> /** * @param string $theArgument * @filter $theArgument LowerCase, Trim */ public function theAction($theArgument) { } </pre> TYPO3.Flow - Feature #1785 (New): Automatic garbage collection for expired cache entries http://forge.typo3.org/issues/1785 2008-10-22T21:02:36Z Robert Lemke robert@typo3.org <p>Expired cache entries - even those of caches which are not registered (anymore) - should be cleaned up from time to time by a garbage collection.</p>