From 9384936c512ab2275c354a0d16fb1420dc21190c Mon Sep 17 00:00:00 2001 From: Will Rossiter Date: Fri, 22 May 2009 02:49:30 +0000 Subject: [PATCH] MINOR: updated legacy form comment. PATCH #3769 git-svn-id: svn://svn.silverstripe.com/silverstripe/open/modules/sapphire/trunk@77599 467b73ca-7a2a-4603-9d3b-597d59a354a9 --- core/control/Controller.php | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/core/control/Controller.php b/core/control/Controller.php index 751582d90..8572ddf23 100644 --- a/core/control/Controller.php +++ b/core/control/Controller.php @@ -221,12 +221,9 @@ class Controller extends RequestHandler { * Then it looks for the action method. The action is taken from $this->urlParams['Action'] - for this reason, it's important * to have $Action included in your Director rule * - * If $requestParams['executeForm'] is set, then the Controller assumes that we're processing a form. This is usually - * set by adding ?executeForm=XXX to the form's action URL. Form processing differs in the following ways: - * - The action name will be the name of the button clicked. If no button-click can be detected, the first button in the - * list will be assumed. - * - If the given action method doesn't exist on the controller, Controller will look for that method on the Form object. - * this lets developers package both a form and its action handlers in a single subclass of Form. + * $requestParams['executeForm'] support was removed, make the following change in your URLs: + * "/?executeForm=FooBar" -> "/FooBar" + * Also make sure "FooBar" is in the $allowed_actions of your controller class. * * NOTE: You should rarely need to overload run() - this kind of change is only really appropriate for things like nested * controllers - {@link ModelAsController} and {@link RootURLController} are two examples here. If you want to make more