1.0.5

Issues by
AOP

3/3
Build Process

1/1
Command

1/1
Configuration

1/1
Core

1/1
Core

1/1
Error

1/1
Object

1/1
Resource

2/2
Security

2/2
Validation

2/2
ViewHelpers

1/1

2012-06-05

100%

21 closed (100%)   0 open (0%)

Related issues
  • Bug #13333: AOP for methods with references do not work.
  • Bug #25961: HTML should be escaped in the pre output of DebugExceptionHandler
  • Bug #28213: Sites Configuration should overrule package Configuration
  • Bug #29603: __toString() usage for rendering the compiled Fluid template breaks the concept of security exceptions
  • Bug #29694: \TYPO3\FLOW3\Resource\Resource is missing the __toString Method
  • Bug #30914: Proxy methods for methods with "by reference" return type are broken
  • Bug #31380: DocComment of Form.ValidationResultsViewHelper is incorrect
  • Bug #31905: getInterceptedRequest is NULL but ACL matches correctly DENY
  • Bug #32959: Exception thrown on missing role definition
  • Bug #33139: Confusing error message if a CommandController is outside /Controller/ directory
  • Bug #33410: Production Settings.yaml.example is not useable as is
  • Bug #33932: AOP Proxy Compiler does not handle numeric annotation parameters
  • Bug #33968: Missing privileges to create symlinks in Windows cause exception
  • Bug #34048: ResolveValidator breaks on DateTime method arguments
  • Bug #34614: Evil packed bz2 package
  • Bug #35338: Action arguments of type DateTime throw Exception
  • Bug #36155: kickstart:model example for property creation is wrong
  • Bug #36185: Creation of packages fails or they cannot be called later
  • Bug #36279: When setting file permissions, the return code is always 0, even on error
  • Bug #36580: Broken links and outdated text on Welcome screen
  • Bug #37193: Nested array annotation options are not rendered in proxy classes