If you are using sfModerationPlugin as an external, you may have noticed a critical bug since the last commit by blacksun on Thursday.
The introduction of the following new function produces a completely silent error : public static function getWatchedColumns(string $class) It uses type hinting with the string type, which is not supported by PHP "Traditional type hinting with int and string isn't supported. " source: http://fr2.php.net/manual/en/language.oop5.typehinting.php I encourage you not to update to the last version or change the guilty line in file lib/sfPropelModerationBehavior.class.php, line 438 to : public static function getWatchedColumns($class) which seemed to solve our problem for the moment. However I am not comfortable with the fact that blacksun's new commit uses unsupported features. This brings me to a new topic : how do you handle external plugins on your projects ? Clearly, this experience proves me that externals are too dangerous. But how do you keep track of security updates if you don't use externals ? Fabrice Bernhard -- http://www.allomatch.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
