The answer is nuanced. In this case, since the action is to be overridden, solution 1 is more appropriate, which is what I have been doing, whew! Although there was no mention of whether or not the actions.class.php file is overridden when upgrading the plugin. I guess I will just hope that it is not and keep backups.
mosez Messages: 28 Registered: May 2008 Location: Nuremberg
if you are building your onw module it is the best solution. Build a module on app/appname/modules/sfGuarAuth, there you can add an actions class, extend it from the sfGuarAuth module action on plugins folder.
On your own module folder you can overwrite the templates for login and secured page too.