Blog

Comments

• 

  #1 pierre said on the 2006/06/23 at 23:14
  Is there andy documentation out there about the ZF/EZC bridges? I worked with this frameworks already, and I wanna see what this bridge can offer me.
• 

  #2 François Zaninotto said on the 2006/06/24 at 10:08
  Pierre: try the custom extensions chapter in the symfony book
  
  http://www.symfony-project.com/content/book/page/custom_helper.html
• 

  #3 Mohammad said on the 2006/06/24 at 15:37
  WOW it's wonderful
• 

  #4 NiKo said on the 2006/06/25 at 20:47
  Well, I've just upgraded and now I got a strange message : "Configuration file "/usr/share/php/data/symfony/config/php.yml" specifies that php.ini "magic_quotes_gpc" key must be set to "". The current value is "1" (php.ini location: "/etc/php5/apache2/php.ini"). [err0001]"
  
  ... While the settings are corrects in my php.ini :-?
• 

  #5 NiKo said on the 2006/06/25 at 21:18
  The problem seem to be variable type misunderstanding while parsing php yaml conf files in this new version.
  
  Indeed, this is a vardump of the result of the parsing of my php.yml file (in ./util/sfYaml.class.php) :
  
  array(2) {
  ["set"]=>
  array(3) {
  ["magic_quotes_runtime"]=>
  bool(false)
  ["log_errors"]=>
  bool(true)
  ["arg_separator.output"]=>
  string(6) "\&"
  }
  ["check"]=>
  array(3) {
  ["magic_quotes_gpc"]=>
  bool(false)
  ["register_globals"]=>
  bool(false)
  ["zend.ze1_compatibility_mode"]=>
  bool(false)
  }
  }
  
  which is :
  
  set:
  magic_quotes_runtime: off
  log_errors: on
  arg_separator.output: \&
  
  check:
  magic_quotes_gpc: off
  register_globals: off
  zend.ze1_compatibility_mode: off
  
  ... so the test in ./config/sfPhpConfigHandler.class.php compare booleans with... php.ini strings.
  
  But maybe it's my config or I missed something...
• 

  #6 daniel said on the 2006/06/26 at 04:34
  all my ajax and rico has stopped working with the new update..
  
  what the??
• 

  #7 Peter said on the 2006/07/14 at 11:30
  Quite bad that actions and routing are now case sensitive :(
  Perhaps we could have additional setting in settings.yml to turn this feature on and off?