Hey Javi, The two classes without "Plugin" are not directly involved with the autogenerated model layer, the are just custom extensions for a specific purpose. It is considered best practice for writing plugins, that you move the model code into "Plugin" classes and leave the higher model class empty so that you can override them on the application level. In the case of the 2 classes you mention this is not neccessary, because you can determine via app.yml configuration if you want to use a different class instead.
Hope that made sense. Daniel On Nov 3, 10:28 am, tirengarfio <tirengar...@gmail.com> wrote: > Hi, > > if you install sfDoctrineGuardPlugin and look inside the folder > plugins/sfDoctrineGuardPlugin/lib/form/doctrine you will see these > files: > > PluginsfGuardUserForm.class.php > PluginsfGuardGroupForm.class.php > PluginsfGuardUserGroupForm.class.php > PluginsfGuardGroupPermissionForm.class.php > PluginsfGuardUserPermissionForm.class.php > PluginsfGuardPermissionForm.class.php > PluginsfGuardRememberKeyForm.class.php > sfGuardFormSignin.class.php > sfGuardUserAdminForm.class.php > > Why is not added "Plugin" at the beginning of > sfGuardUserAdminForm.class.php and sfGuardUserFormSignin.class.php?? > > Im just curious... > > Bye > > Javi --~--~---------~--~----~------------~-------~--~----~ 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 symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
