Settings

Choose language

new topic 35 posts, 5 writers, 5 readers, started 100 months ago

posted 95 months ago (Thursday, June 30) by kovaldm
#26
kovaldm

posted 95 months ago (Thursday, June 30) by kovaldm
#27
kovaldm

posted 95 months ago (Thursday, June 30) by kovaldm
#28
kovaldm

posted 95 months ago (Thursday, June 30) by kovaldm
#29
kovaldm

posted 95 months ago (Thursday, June 30) by kovaldm
#30
kovaldmnewuser

posted 95 months ago (Thursday, June 30) by kovaldm
#31
kovaldmnewuser

posted 95 months ago (Thursday, June 30) by kovaldm
#32
kovaldm

newuser

posted 95 months ago (Thursday, June 30) by kovaldm
#33
kovaldmnewuser

posted 95 months ago (Thursday, June 30) by kovaldm
#34
kovaldmnewuser

posted 88 months ago (Thursday, February 9) by kovaldm
#35
dmitry-kovalev

posted 88 months ago (Thursday, February 9) by kovaldm
#36
qwe-1kovaldmkovaldm
kovaldm

posted 88 months ago (Thursday, February 9) by kovaldm
#37
kovaldm

posted 83 months ago (Wednesday, July 19), edited 83 months ago by newuser
#38
When a user requests an action 'XYZ',
CController will do one of the following:
1. Method-based action: call method 'actionXYZ' if it exists;
2. Class-based action: create an instance of class 'XYZ' if the class is found in the action class map (specified via actions(), and execute the action;
3. Call missingAction(), which by default will raise a 404 HTTP exception.
If the user does not specify an action, CController will run the action specified by defaultAction, instead.
CController may be configured to execute filters before and after running actions. Filters preprocess/postprocess the user request/response and may quit executing actions if needed. They are executed in the order they are specified. If during the execution, any of the filters returns true, the rest filters and the action will no longer get executed.