Returns a list of external action classes. Array keys are action IDs, and
array values are the corresponding action class in dot syntax (e.g.
'edit'=>'application.controllers.article.EditArticle') or arrays representing
the configuration of the actions, such as the following,
return array(
'action1'=>'path.to.Action1Class',
'action2'=>array(
'class'=>'path.to.Action2Class',
'property1'=>'value1',
'property2'=>'value2',
),
);
Derived classes may override this method to declare external actions.
Returns a list of external action classes. Array keys are action IDs, and
array values are the corresponding action class in dot syntax (e.g.
'edit'=>'application.controllers.article.EditArticle') or arrays representing
the configuration of the actions, such as the following,
return array(
'action1'=>'path.to.Action1Class',
'action2'=>array(
'class'=>'path.to.Action2Class',
'property1'=>'value1',
'property2'=>'value2',
),
);
Derived classes may override this method to declare external actions.
Note, in order to inherit actions defined in the parent class, a child class
needs to merge the parent actions with child actions using functions like
array_merge().
You may import actions from an action provider (such as a widget, see CWidget::actions), like the following:
return array(
...other actions...
// import actions declared in ProviderClass::actions()
// the action IDs will be prefixed with 'pro.'
'pro.'=>'path.to.ProviderClass',
// similar as above except that the imported actions are
// configured with the specified initial property values
'pro2.'=>array(
'class'=>'path.to.ProviderClass',
'action1'=>array(
'property1'=>'value1',
),
'action2'=>array(
'property2'=>'value2',
),
),
)
In the above, we differentiate action providers from other action
declarations by the array keys. For action providers, the array keys must
contain a dot. As a result, an action ID 'pro2.action1' will be resolved as the
'action1' action declared in the 'ProviderClass'.
Returns
array
list of external action classes
See
Overrides
CBaseController