Bernhard Schussek wrote: > >> So, thank you both for the hint but don't you think my suggestion is >> valid and will not hurt whoever does not want to use it but will help >> people like me to not touch the "special" methods in the action? >> >> Kupo >> > > In my opinion these protected methods are there exactly to BE modified, > not vice versa. If you look close, some of these "special" methods don't > do much or are only called from one place in the code. For example, it > wouldn't make any difference if you moved the code $storeCatalog->save() > from saveStoreCatalog() to executeEdit(), since this is the only place > calling this method. > > The advantage of the protected method though is, that you CAN override > them without altering the other logic created by the admin generator. > See them as hooks where you can insert your custom code. > > Regards > > > > > > So I should understand that anywhere in the action.class.php methods it is OK to handle request parameters. This was my only issue and if that's the practice everybody is using I will do that too from now on.
Thanks again, Kiril --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
