From 3d35cffb680b42c94bc3f08cba3323b0b3dc09fe Mon Sep 17 00:00:00 2001 From: Victor Berchet Date: Mon, 13 Dec 2010 22:03:25 +0100 Subject: [PATCH] [reference] ch 6 - object actions --- reference/en/06-Admin-Generator.markdown | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/reference/en/06-Admin-Generator.markdown b/reference/en/06-Admin-Generator.markdown index b8db913..c50baa0 100644 --- a/reference/en/06-Admin-Generator.markdown +++ b/reference/en/06-Admin-Generator.markdown @@ -563,11 +563,7 @@ The executed method received the primary keys of the selected objects via the *Default value*: `{ _edit: ~, _delete: ~ }` The `object_actions` option defines the list of actions that can be executed -on each object of the list. The list of actions is an associative array which -keys are the route names and values an array of methods: - - [yml] - object_actions: { publish: get, publishBis: [get, post] } +on each object of the list. If you don't define an `action`, the admin generator will look for a method named after the camel-cased name prefixed by `executeList`.