Ok, I think I have resolved it by adding
propel.behavior.default = symfony
to my propel.ini - certainly the sfMixer code is there. Is this the
'official' way of doing it or is there another way?
After this update, the sfMixer code now appears but the hook names are
different to 1.2 e.g. in BaseCustomerPeer::doUpdate() the hook was
foreach (sfMixer::getCallables('BaseCustomerPeer:doUpdate:post') as
$callable)
{
call_user_func($callable, 'BaseCustomerPeer', $values, $con, $ret);
}
now it is
foreach (sfMixer::getCallables('Customer:doUpdate:post') as $sf_hook)
{
call_user_func($sf_hook, 'Customer', $values, $con, $ret);
}
which does not trigger my hook, plus it passes in an incorrect first
parameter "Customer" and not "BaseCustomerPeer"
Is this a bug or a change - i.e. do I need to update my hook names
when registering?
Thanks,
Andy
On Oct 26, 11:36 am, "arri...@gmail.com" <arri...@gmail.com> wrote:
> Hi,
>
> Just updated my code and looks like symfony is now using the propel
> native behavior system. This is good news, but I'm struggling to get
> it working.
>
> From what I can work out, the behaviors all sit under a 'symfony'
> behavior. I am struggling to enable this. In my propel.ini I have:
>
> ; builder settings
> propel.builder.object.class =
> lib.override.plugins.sfPropelPlugin.lib.builder.CtObjectBuilder
>
> propel.behavior.symfony.class =
> plugins.sfPropelPlugin.lib.behavior.SfPropelBehaviorSymfony
> propel.behavior.symfony_i18n.class =
> plugins.sfPropelPlugin.lib.behavior.SfPropelBehaviorI18n
> propel.behavior.symfony_i18n_translation.class =
> plugins.sfPropelPlugin.lib.behavior.SfPropelBehaviorI18nTranslation
> propel.behavior.symfony_behaviors.class =
> plugins.sfPropelPlugin.lib.behavior.SfPropelBehaviorSymfonyBehaviors
> propel.behavior.symfony_timestampable.class =
> plugins.sfPropelPlugin.lib.behavior.SfPropelBehaviorTimestampable
>
> propel.builder.addComments = true
> propel.builder.addBehaviors = true
>
> But the code for sfMixer, etc is not in the generated Base peer
> classes.
>
> I have tried:
>
> propel:
> _attributes: { package:
> lib.model.retailer, propel_behaviors: symfony }
>
> in my schema.yml without success.
>
> I have looked at the upgrade wiki but it doesn't seem to mention
> behaviors.
>
> I have had some success with adding
> _propel_behaviors:
> symfony: ~
>
> to a table, but surely that is incorrect - I would have to add it to
> every table?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
