tickets  

Messages by Thread

• • Re: [Agavi-Tickets] [Agavi] #956: Create Testcases for #955 Agavi
  • Re: [Agavi-Tickets] [Agavi] #956: Create Testcases for #955 Agavi
  • Re: [Agavi-Tickets] [Agavi] #956: Create Testcases for #955 Agavi
• [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
  • Re: [Agavi-Tickets] [Agavi] #955: AgaviWebRequestDataHolder method implementations are all over the place Agavi
• Re: [Agavi-Tickets] [Agavi] #907: Escaping of brackets and braces inside routing patterns is inconsistent (was: Escaping of brackets and braces inside routing patterns is broken) Agavi
• [Agavi-Tickets] [Agavi] #954: Access to global request data holder is not locked during AgaviAction::getDefaultViewName() Agavi
  • Re: [Agavi-Tickets] [Agavi] #954: Access to global request data holder is not locked during AgaviAction::getDefaultViewName() Agavi
• [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require 5.2.7 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require 5.2.7 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require 5.2.7 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there (was: Change magic_quotes_gpc handling to require 5.2.7 and use the fixes introduced there) Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
  • Re: [Agavi-Tickets] [Agavi] #953: Change magic_quotes_gpc handling to require PHP 5.2.8 and use the fixes introduced there Agavi
• [Agavi-Tickets] [Agavi] #952: Re-throw exception instead of printing stack trace and info in exception templates when display_errors is off Agavi
  • Re: [Agavi-Tickets] [Agavi] #952: Re-throw exception instead of printing stack trace and info in exception templates when display_errors is off Agavi
• [Agavi-Tickets] [Agavi] #951: The class name of the AgaviAndoperatorValidator doesn't match the coding guidelines Agavi
  • Re: [Agavi-Tickets] [Agavi] #951: The class name of the AgaviAndoperatorValidator doesn't match the coding guidelines Agavi
  • Re: [Agavi-Tickets] [Agavi] #951: The class name of AgaviAndoperatorValidator and AgaviNotoperatorValidator don't match the coding guidelines (was: The class name of the AgaviAndoperatorValidator doesn't match the coding guidelines) Agavi
  • Re: [Agavi-Tickets] [Agavi] #951: The class name of AgaviAndoperatorValidator and AgaviNotoperatorValidator don't match the coding guidelines Agavi
• [Agavi-Tickets] [Agavi] #950: Remove deprecated AgaviException::printStackTrace() Agavi
• [Agavi-Tickets] [Agavi] #949: Rename AgaviException::printStackTrace() Agavi
  • Re: [Agavi-Tickets] [Agavi] #949: Rename AgaviException::printStackTrace() Agavi
  • Re: [Agavi-Tickets] [Agavi] #949: Rename AgaviException::printStackTrace() Agavi
  • Re: [Agavi-Tickets] [Agavi] #949: Rename AgaviException::printStackTrace() Agavi
  • Re: [Agavi-Tickets] [Agavi] #949: Rename AgaviException::printStackTrace() Agavi
• [Agavi-Tickets] [Agavi] #948: Add an arraylength validator Agavi
  • Re: [Agavi-Tickets] [Agavi] #948: Add an arraylength validator Agavi
  • Re: [Agavi-Tickets] [Agavi] #948: Add an arraylength validator Agavi
  • Re: [Agavi-Tickets] [Agavi] #948: AgaviArraylengthValidator (was: Add an arraylength validator) Agavi
• [Agavi-Tickets] [Agavi] #947: AgaviValidator::getKeysInCurrentBase triggers a warning if the current validator base is no array Agavi
  • Re: [Agavi-Tickets] [Agavi] #947: AgaviValidator::getKeysInCurrentBase triggers a warning if the current validator base is no array Agavi
• Re: [Agavi-Tickets] [Agavi] #923: AgaviNumberValidator with translation raises a notice when argument value is an array. Agavi
• [Agavi-Tickets] [Agavi] #946: Several validators might raise notices or break altogether on incorrect argument types Agavi
  • Re: [Agavi-Tickets] [Agavi] #946: Several validators might raise notices or break altogether on incorrect argument types Agavi
• Re: [Agavi-Tickets] [Agavi] #751: stdout/stderror log appenders are broken Agavi
• [Agavi-Tickets] [Agavi] #945: Add conditional for workaround addressed by PHP Bug #46313 Agavi
  • Re: [Agavi-Tickets] [Agavi] #945: Add conditional for workaround addressed by PHP Bug #46313 Agavi
  • Re: [Agavi-Tickets] [Agavi] #945: Add conditional for workaround addressed by PHP Bug #46313 Agavi
  • Re: [Agavi-Tickets] [Agavi] #945: Add conditional for workaround addressed by PHP Bug #46313 Agavi
  • Re: [Agavi-Tickets] [Agavi] #945: Add conditional for workaround addressed by PHP Bug #46313 Agavi
  • Re: [Agavi-Tickets] [Agavi] #945: Add conditional for workaround addressed by PHP Bug #46313 Agavi
• [Agavi-Tickets] [Agavi] #944: Remove workaround for PHP Bug #41093 Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Remove workaround for PHP Bug #41093 Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Remove workaround for PHP Bug #41093 Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Make workaround for PHP Bug #41093 conditional (was: Remove workaround for PHP Bug #41093) Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Make workaround for PHP Bug #41093 conditional Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Make workaround for PHP Bug #41093 conditional Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Make workaround for PHP Bug #41093 conditional Agavi
  • Re: [Agavi-Tickets] [Agavi] #944: Make workaround for PHP Bug #41093 conditional Agavi
• [Agavi-Tickets] [Agavi] #943: FPF error insertion fails if XPath expression yields more than one location in the document Agavi
  • Re: [Agavi-Tickets] [Agavi] #943: FPF error insertion fails if XPath expression yields more than one location in the document Agavi
• [Agavi-Tickets] [Agavi] #942: Arguments are unable to be named in validators configuration Agavi
  • Re: [Agavi-Tickets] [Agavi] #942: Arguments are unable to be named in validators configuration Agavi
  • Re: [Agavi-Tickets] [Agavi] #942: Arguments are unable to be named in validators configuration Agavi
  • Re: [Agavi-Tickets] [Agavi] #942: Arguments are unable to be named in validators configuration Agavi
  • Re: [Agavi-Tickets] [Agavi] #942: Arguments are unable to be named in validators configuration Agavi
• Re: [Agavi-Tickets] [Agavi] #934: Possible to run any action by passing module/action parameters to invalid URL Agavi
• Re: [Agavi-Tickets] [Agavi] #934: Possible to run any action by passing module/action parameters to invalid URL (was: Possible to run any action with crafted URL) Agavi
• [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
  • Re: [Agavi-Tickets] [Agavi] #941: AgaviConfigCache reaches Maximum function nesting level Agavi
• Re: [Agavi-Tickets] [Agavi] #829: Throw out legacy naming schemes support and support autoloading of Actions, Views and Models Agavi
• Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
  • Re: [Agavi-Tickets] [Agavi] #519: Change configuration system to support only XML Agavi
• Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
  • Re: [Agavi-Tickets] [Agavi] #380: Implement an infrastructure for funtional and unit testing of applications (and Agavi itself) Agavi
• Re: [Agavi-Tickets] [Agavi] #935: Refactor AgaviToolkit::stringBase() (was: refactor AgaviToolkit::stringBase()) Agavi
• [Agavi-Tickets] [Agavi] #940: Allow optional marshalling of document/literal wrapped request and response elements Agavi
  • Re: [Agavi-Tickets] [Agavi] #940: Allow optional marshalling of document/literal wrapped request and response elements Agavi
  • Re: [Agavi-Tickets] [Agavi] #940: Allow optional marshalling of document/literal wrapped request and response elements Agavi
  • Re: [Agavi-Tickets] [Agavi] #940: Allow optional marshalling of document/literal wrapped request and response elements Agavi
  • Re: [Agavi-Tickets] [Agavi] #940: Allow optional marshalling of document/literal wrapped request and response elements Agavi
  • Re: [Agavi-Tickets] [Agavi] #940: Allow optional marshalling of document/literal wrapped request and response elements Agavi
• [Agavi-Tickets] [Agavi] #939: Delimiter is not passed to numerous preg_quote calls Agavi
  • Re: [Agavi-Tickets] [Agavi] #939: Pattern delimiter is not passed to several preg_quote calls (was: Delimiter is not passed to numerous preg_quote calls) Agavi
  • Re: [Agavi-Tickets] [Agavi] #939: Pattern delimiter is not passed to several preg_quote calls Agavi
• Re: [Agavi-Tickets] [Agavi] #929: Allow passing of configuration handler information (class/parameters) to AgaviConfigCache::checkConfig() and AgaviConfigCache::load() Agavi
  • Re: [Agavi-Tickets] [Agavi] #929: Allow passing of configuration handler information (class/parameters) to AgaviConfigCache::checkConfig() and AgaviConfigCache::load() Agavi
  • Re: [Agavi-Tickets] [Agavi] #929: Allow passing of configuration handler information (class/parameters) to AgaviConfigCache::checkConfig() and AgaviConfigCache::load() Agavi
  • Re: [Agavi-Tickets] [Agavi] #929: Allow passing of configuration handler information (class/parameters) to AgaviConfigCache::checkConfig() and AgaviConfigCache::load() Agavi
• Re: [Agavi-Tickets] [Agavi] #920: Hassle with cache file on concurrent requests Agavi
  • Re: [Agavi-Tickets] [Agavi] #920: Hassle with cache file on concurrent requests Agavi
• Re: [Agavi-Tickets] [Agavi] #935: refactor AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #935: refactor AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #935: Refactor AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #935: Refactor AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #935: Refactor AgaviToolkit::stringBase() Agavi
• Re: [Agavi-Tickets] [Agavi] #938: Add configuration file path to header comments in compiled files if possible Agavi
  • Re: [Agavi-Tickets] [Agavi] #938: Add configuration file path to header comments in compiled files if possible Agavi
  • Re: [Agavi-Tickets] [Agavi] #938: Add configuration file path to header comments in compiled files if possible Agavi
• Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
  • Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
  • Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
  • Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
  • Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
  • Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
  • Re: [Agavi-Tickets] [Agavi] #932: AgaviConfigCache::getCacheName() possibly creating ambiguous cache names Agavi
• Re: [Agavi-Tickets] [Agavi] #931: AgaviConfigCache::getCacheName() path escaping problems Agavi
  • Re: [Agavi-Tickets] [Agavi] #931: AgaviConfigCache::getCacheName() path escaping problems Agavi
  • Re: [Agavi-Tickets] [Agavi] #931: AgaviConfigCache::getCacheName() path escaping problems Agavi
  • Re: [Agavi-Tickets] [Agavi] #931: AgaviConfigCache::getCacheName() path escaping problems Agavi
  • Re: [Agavi-Tickets] [Agavi] #931: AgaviConfigCache::getCacheName() path escaping problems Agavi
• Re: [Agavi-Tickets] [Agavi] #936: Off-by-one error in AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #936: Off-by-one error in AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #936: Off-by-one error in AgaviToolkit::stringBase() Agavi
  • Re: [Agavi-Tickets] [Agavi] #936: Off-by-one error in AgaviToolkit::stringBase() Agavi
• Re: [Agavi-Tickets] [Agavi] #720: Add support for per-module base action/view/models to build system Agavi

• Later messages