tickets  

Messages by Thread

• • Re: [Agavi-Tickets] [Agavi] #1035: Allow setting of session_cache_expire(), session_cache_limiter() and session_module_name() through configuration Agavi
• [Agavi-Tickets] [Agavi] #1034: Checking Credentials Agavi
  • Re: [Agavi-Tickets] [Agavi] #1034: Checking Credentials Agavi
  • Re: [Agavi-Tickets] [Agavi] #1034: Checking Credentials Agavi
• [Agavi-Tickets] [Agavi] #1033: Leading / is missing from routes in lighttpd Agavi
  • Re: [Agavi-Tickets] [Agavi] #1033: Leading / is missing from routes in lighttpd Agavi
• [Agavi-Tickets] [Agavi] #1032: Introduce AgaviUncacheableException for cache group callbacks Agavi
  • Re: [Agavi-Tickets] [Agavi] #1032: Introduce special AgaviUncacheableException for cache group callbacks (was: Introduce AgaviUncacheableException for cache group callbacks) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1032: Introduce special AgaviUncacheableException for cache group callbacks Agavi
  • Re: [Agavi-Tickets] [Agavi] #1032: Introduce special AgaviUncacheableException for cache group callbacks Agavi
• [Agavi-Tickets] [Agavi] #1031: Fatal error in AgaviRouting with use_translation=false Agavi
  • Re: [Agavi-Tickets] [Agavi] #1031: Fatal error in AgaviRouting with use_translation=false Agavi
  • Re: [Agavi-Tickets] [Agavi] #1031: Regression: Fatal error in AgaviRouting with use_translation off (was: Fatal error in AgaviRouting with use_translation=false) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1031: Regression: Fatal error in AgaviRouting with use_translation off Agavi
  • Re: [Agavi-Tickets] [Agavi] #1031: Regression: Fatal error in AgaviRouting with use_translation off Agavi
• [Agavi-Tickets] [Agavi] #1030: Rename "messageIndex" in AgaviValidationError to "name" Agavi
  • Re: [Agavi-Tickets] [Agavi] #1030: Rename "messageIndex" in AgaviValidationError to "name" Agavi
  • Re: [Agavi-Tickets] [Agavi] #1030: Rename "messageIndex" in AgaviValidationError to "name" Agavi
  • Re: [Agavi-Tickets] [Agavi] #1030: Rename "messageIndex" in AgaviValidationError to "name" Agavi
  • Re: [Agavi-Tickets] [Agavi] #1030: Rename "messageIndex" in AgaviValidationError to "name" Agavi
  • Re: [Agavi-Tickets] [Agavi] #1030: Rename "messageIndex" in AgaviValidationError to "name" Agavi
• Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
  • Re: [Agavi-Tickets] [Agavi] #1008: [EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it Agavi
• Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
  • Re: [Agavi-Tickets] [Agavi] #858: Backport any necessary ICU changes and fixes Agavi
• [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
  • Re: [Agavi-Tickets] [Agavi] #1029: Throw exception if Apache's SERVER_SOFTWARE env var contains insufficient version information Agavi
• [Agavi-Tickets] [Agavi] #1028: Allow callbacks to return an AgaviResponse Agavi
  • Re: [Agavi-Tickets] [Agavi] #1028: Allow callbacks to return an AgaviResponse Agavi
  • Re: [Agavi-Tickets] [Agavi] #1028: Allow routing callbacks to return an AgaviResponse (was: Allow callbacks to return an AgaviResponse) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1028: Allow routing callbacks to return an AgaviResponse Agavi
  • Re: [Agavi-Tickets] [Agavi] #1028: Allow routing callbacks to return an AgaviResponse Agavi
  • Re: [Agavi-Tickets] [Agavi] #1028: Allow routing callbacks to return an AgaviResponse Agavi
• [Agavi-Tickets] [Agavi] #1027: Call onNotMatched() method on a callback if its onMatched() method returned false Agavi
  • Re: [Agavi-Tickets] [Agavi] #1027: Call onNotMatched() method on a callback if its onMatched() method returned false Agavi
  • Re: [Agavi-Tickets] [Agavi] #1027: Call onNotMatched() method on a routing callback if its onMatched() method returned false (was: Call onNotMatched() method on a callback if its onMatched() method returned false) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1027: Explicitly call onNotMatched() method on a routing callback if its onMatched() method returned false (was: Call onNotMatched() method on a routing callback if its onMatched() method returned false) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1027: Explicitly call onNotMatched() method on a routing callback if its onMatched() method returned false Agavi
  • Re: [Agavi-Tickets] [Agavi] #1027: Explicitly call onNotMatched() method on a routing callback if its onMatched() method returned false Agavi
• [Agavi-Tickets] [Agavi] #1026: Restore state right after a callback returned false from onMatched() rather than at the end of the callback execution loop Agavi
  • Re: [Agavi-Tickets] [Agavi] #1026: Restore state right after a callback returned false from onMatched() rather than at the end of the callback execution loop Agavi
  • Re: [Agavi-Tickets] [Agavi] #1026: Restore state right after a routing callback returned false from onMatched() rather than at the end of the callback execution loop (was: Restore state right after a callback returned false from onMatched() rather than at the end of the callback execution loop) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1026: Restore state right after a routing callback returned false from onMatched() rather than at the end of the callback execution loop Agavi
  • Re: [Agavi-Tickets] [Agavi] #1026: Restore state right after a routing callback returned false from onMatched() rather than at the end of the callback execution loop Agavi
• [Agavi-Tickets] [Agavi] #1025: Use of undefined variable $request in AgaviWebRouting::execute() Agavi
  • Re: [Agavi-Tickets] [Agavi] #1025: Use of undefined variable $request in AgaviWebRouting::execute() Agavi
  • Re: [Agavi-Tickets] [Agavi] #1025: Use of undefined variable $request in AgaviRouting::execute() (was: Use of undefined variable $request in AgaviWebRouting::execute()) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1025: Use of undefined variable $request in AgaviRouting::execute() Agavi
  • Re: [Agavi-Tickets] [Agavi] #1025: Use of undefined variable $request in AgaviRouting::execute() Agavi
  • Re: [Agavi-Tickets] [Agavi] #1025: Use of undefined variable $request in AgaviRouting::execute() Agavi
• [Agavi-Tickets] [Agavi] #1024: Regression: Locale and Request Method are not restored to previous value after a matching route's callback(s) caused the match to ultimately fail Agavi
  • Re: [Agavi-Tickets] [Agavi] #1024: Regression: Locale and Request Method are not restored to previous value after a matching route's callback(s) caused the match to ultimately fail Agavi
  • Re: [Agavi-Tickets] [Agavi] #1024: Regression: Locale and Request Method are not restored to previous value after a matching route's callback(s) caused the match to ultimately fail Agavi
  • Re: [Agavi-Tickets] [Agavi] #1024: Regression: Locale and Request Method are not restored to previous value after a matching route's callback(s) caused the match to ultimately fail Agavi
• [Agavi-Tickets] [Agavi] #1023: Regression: invalid Locale or Output Type names in routes trigger premature exceptions Agavi
  • Re: [Agavi-Tickets] [Agavi] #1023: Regression: invalid Locale or Output Type names in routes trigger premature exceptions Agavi
  • Re: [Agavi-Tickets] [Agavi] #1023: Regression: invalid Locale or Output Type names in routes trigger premature exceptions Agavi
  • Re: [Agavi-Tickets] [Agavi] #1023: Regression: invalid Locale or Output Type names in routes trigger premature exceptions Agavi
• [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Introduce new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Implement new validation report query API (was: Introduce new validation report query API) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Implement new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Implement new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Implement new validation report query API Agavi
  • Re: [Agavi-Tickets] [Agavi] #1022: Implement new validation report query API Agavi
• [Agavi-Tickets] [Agavi] #1021: Implement a basic system for testing Agavi applications and internal components Agavi
  • Re: [Agavi-Tickets] [Agavi] #1021: Implement a basic system for testing Agavi applications and internal components Agavi
  • Re: [Agavi-Tickets] [Agavi] #1021: Implement a basic system for testing Agavi applications and internal components Agavi
• [Agavi-Tickets] [Agavi] #1020: Throw named error if "required" condition is not satisfied in validators Agavi
  • Re: [Agavi-Tickets] [Agavi] #1020: Throw named error if "required" condition is not satisfied in validators Agavi
  • Re: [Agavi-Tickets] [Agavi] #1020: Throw named error if "required" condition is not satisfied in validators Agavi
• [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
  • Re: [Agavi-Tickets] [Agavi] #1019: CVE-2009-0417: Cross-site scripting vulnerability in handling of incoming URLs Agavi
• Re: [Agavi-Tickets] [Agavi] #872: Add support for unit testing to the project configuration system Agavi
  • Re: [Agavi-Tickets] [Agavi] #872: Add support for unit testing to the project configuration system Agavi
  • Re: [Agavi-Tickets] [Agavi] #872: Add support for unit testing to the project configuration system Agavi
• Re: [Agavi-Tickets] [Agavi] #448: Rewrite Routing Agavi
  • Re: [Agavi-Tickets] [Agavi] #448: Rewrite Routing Agavi
  • Re: [Agavi-Tickets] [Agavi] #448: Rewrite Routing Agavi
  • Re: [Agavi-Tickets] [Agavi] #448: Rewrite Routing Agavi
• Re: [Agavi-Tickets] [Agavi] #812: Make populating of module and action names into request data configurable and remove overwriting behavior Agavi
  • Re: [Agavi-Tickets] [Agavi] #812: Make populating of module and action names into request data configurable and remove overwriting behavior Agavi
  • Re: [Agavi-Tickets] [Agavi] #812: Make populating of module and action names into request data configurable and remove overwriting behavior Agavi
• Re: [Agavi-Tickets] [Agavi] #448: Rewrite Routing (was: Rewrite/refactor parts of routing, at least gen()) Agavi
• [Agavi-Tickets] [Agavi] #1018: Allow relative min and max values using strtotime syntax in AgaviDateTimeValidator Agavi
  • Re: [Agavi-Tickets] [Agavi] #1018: Allow relative min and max values using strtotime syntax in AgaviDateTimeValidator Agavi
  • Re: [Agavi-Tickets] [Agavi] #1018: Allow relative min and max values using strtotime syntax in AgaviDateTimeValidator Agavi
  • Re: [Agavi-Tickets] [Agavi] #1018: Allow relative min and max values using strtotime syntax in AgaviDateTimeValidator Agavi
  • Re: [Agavi-Tickets] [Agavi] #1018: Allow relative min and max values using strtotime syntax in AgaviDateTimeValidator Agavi
  • Re: [Agavi-Tickets] [Agavi] #1018: Allow relative min and max values using strtotime syntax in AgaviDateTimeValidator Agavi
• [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
  • Re: [Agavi-Tickets] [Agavi] #1017: Content-Type and Content-Length request headers are treated incorrectly Agavi
• [Agavi-Tickets] [Agavi] #1016: Automatically decode HTTP PUT payload into request parameters for application/x-www-form-urlencoded Content-Type in AgaviWebRequest Agavi
  • Re: [Agavi-Tickets] [Agavi] #1016: Automatically decode HTTP PUT payload into request parameters for application/x-www-form-urlencoded Content-Type in AgaviWebRequest Agavi
  • Re: [Agavi-Tickets] [Agavi] #1016: Automatically decode HTTP PUT payload into request parameters for application/x-www-form-urlencoded Content-Type in AgaviWebRequest Agavi
  • Re: [Agavi-Tickets] [Agavi] #1016: Automatically decode HTTP PUT payload into request parameters for application/x-www-form-urlencoded Content-Type in AgaviWebRequest Agavi
  • Re: [Agavi-Tickets] [Agavi] #1016: Automatically decode HTTP PUT payload into request parameters for application/x-www-form-urlencoded Content-Type in AgaviWebRequest Agavi
• [Agavi-Tickets] [Agavi] #1015: Support for arbitrary HTTP POST Content Types Agavi
  • Re: [Agavi-Tickets] [Agavi] #1015: Support for arbitrary HTTP POST Content Types Agavi
  • Re: [Agavi-Tickets] [Agavi] #1015: Support for arbitrary HTTP POST Content Types Agavi
  • Re: [Agavi-Tickets] [Agavi] #1015: Support for arbitrary HTTP POST Content Types Agavi
• [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
  • Re: [Agavi-Tickets] [Agavi] #1014: AgaviWebRequest HTTP PUT support ignores Content-Type header Agavi
• Re: [Agavi-Tickets] [Agavi] #797: $container->setActionName in callback problem Agavi
  • Re: [Agavi-Tickets] [Agavi] #797: $container->setActionName in callback problem Agavi
• Re: [Agavi-Tickets] [Agavi] #448: Rewrite/refactor parts of routing, at least gen() Agavi
  • Re: [Agavi-Tickets] [Agavi] #448: Rewrite/refactor parts of routing, at least gen() Agavi
  • Re: [Agavi-Tickets] [Agavi] #448: Rewrite/refactor parts of routing, at least gen() Agavi
• Re: [Agavi-Tickets] [Agavi] #723: Calendar::roll() over year boundaries yields wrong results Agavi
  • Re: [Agavi-Tickets] [Agavi] #723: Calendar::roll() over year boundaries yields wrong results Agavi
  • Re: [Agavi-Tickets] [Agavi] #723: Calendar::roll() over year boundaries yields wrong results Agavi
  • Re: [Agavi-Tickets] [Agavi] #723: Calendar::roll() over year boundaries yields wrong results Agavi
• Re: [Agavi-Tickets] [Agavi] #883: Write Schematron schemas to enforce certain additional config constraints Agavi
  • Re: [Agavi-Tickets] [Agavi] #883: Write Schematron schemas to enforce certain additional config constraints Agavi
  • Re: [Agavi-Tickets] [Agavi] #883: Write Schematron schemas to enforce certain additional config constraints Agavi
  • Re: [Agavi-Tickets] [Agavi] #883: Write Schematron schemas to enforce certain additional config constraints Agavi
  • Re: [Agavi-Tickets] [Agavi] #883: Write Schematron schemas to enforce certain additional config constraints Agavi
  • Re: [Agavi-Tickets] [Agavi] #883: Write Schematron schemas to enforce certain additional config constraints Agavi
• Re: [Agavi-Tickets] [Agavi] #744: Support for anti-stampede callbacks in Execution Filter Agavi
  • Re: [Agavi-Tickets] [Agavi] #744: Support for anti-stampede callbacks in Execution Filter Agavi
  • Re: [Agavi-Tickets] [Agavi] #744: Support for anti-stampede callbacks in Execution Filter Agavi
• Re: [Agavi-Tickets] [Agavi] #744: Support for anti-stampede callbacks in Execution Filter (was: Add anti-stampede callbacks to Execution Filter) Agavi
• [Agavi-Tickets] [Agavi] #1013: Update timezone database to 2009a Agavi
  • Re: [Agavi-Tickets] [Agavi] #1013: Update timezone database to 2009a Agavi
  • Re: [Agavi-Tickets] [Agavi] #1013: Update timezone database to 2009a Agavi
  • Re: [Agavi-Tickets] [Agavi] #1013: Update timezone database to 2009a Agavi
  • Re: [Agavi-Tickets] [Agavi] #1013: Update timezone database to 2009a Agavi
  • Re: [Agavi-Tickets] [Agavi] #1013: Update timezone database to 2009a Agavi
• [Agavi-Tickets] [Agavi] #1012: AgaviController::dispatch() should accept module and action names in separate arguments Agavi
  • Re: [Agavi-Tickets] [Agavi] #1012: AgaviController::dispatch() should accept module and action names in separate arguments Agavi
  • Re: [Agavi-Tickets] [Agavi] #1012: AgaviController::dispatch() should accept an AgaviExecutionContainer as optional second argument (was: AgaviController::dispatch() should accept module and action names in separate arguments) Agavi
  • Re: [Agavi-Tickets] [Agavi] #1012: AgaviController::dispatch() should accept an AgaviExecutionContainer as optional second argument Agavi
  • Re: [Agavi-Tickets] [Agavi] #1012: AgaviController::dispatch() should accept an AgaviExecutionContainer as optional second argument Agavi
  • Re: [Agavi-Tickets] [Agavi] #1012: AgaviController::dispatch() should accept an AgaviExecutionContainer as optional second argument Agavi

• Earlier messages
• Later messages