CWebApplication
CWebApplication extends CApplication by providing functionalities specific to Web requests.
CWebApplication manages the controllers in MVC pattern, and provides the following additional
core application components:
- urlManager: provides URL parsing and constructing functionality;
- request: encapsulates the Web request information;
- session: provides the session-related functionalities;
- assetManager: manages the publishing of private asset files.
- user: represents the user session information.
- themeManager: manages themes.
- authManager: manages role-based access control (RBAC).
- clientScript: manages client scripts (javascripts and CSS).
- widgetFactory: creates widgets and supports widget skinning.
User requests are resolved as controller-action pairs and additional parameters.
CWebApplication creates the requested controller instance and let it to handle
the actual user request. If the user does not specify controller ID, it will
assume
defaultController is requested (which defaults to 'site').
Controller class files must reside under the directory
controllerPath
(defaults to 'protected/controllers'). The file name and the class name must be
the same as the controller ID with the first letter in upper case and appended with 'Controller'.
For example, the controller 'article' is defined by the class 'ArticleController'
which is in the file 'protected/controllers/ArticleController.php'.
Property Details
the asset manager component
the authorization manager component
Returns the relative URL for the application.
This is a shortcut method to CHttpRequest::getBaseUrl().
public array $catchAllRequest;
the configuration specifying a controller which should handle
all user requests. This is mainly used when the application is in maintenance mode
and we should use a controller to handle all incoming requests.
The configuration specifies the controller route (the first element)
and GET parameters (the rest name-value pairs). For example,
array(
'offline/notice',
'param1'=>'value1',
'param2'=>'value2',
)
Defaults to null, meaning catch-all is not effective.
Returns the client script manager.
the currently active controller
public array $controllerMap;
mapping from controller ID to controller configurations.
Each name-value pair specifies the configuration for a single controller.
A controller configuration can be either a string or an array.
If the former, the string should be the class name or
class path alias of the controller.
If the latter, the array must contain a 'class' element which specifies
the controller's class name or class path alias.
The rest name-value pairs in the array are used to initialize
the corresponding controller properties. For example,
array(
'post'=>array(
'class'=>'path.to.PostController',
'pageTitle'=>'something new',
),
'user'=>'path.to.UserController',,
)
Note, when processing an incoming request, the controller map will first be
checked to see if the request can be handled by one of the controllers in the map.
If not, a controller will be searched for under the
default controller path.
the directory that contains the controller classes. Defaults to 'protected/controllers'.
public string $defaultController;
the ID of the default controller. Defaults to 'site'.
the homepage URL
public mixed $layout;
the application-wide layout. Defaults to 'main' (relative to layoutPath).
If this is false, then no layout will be used.
the root directory of layout files. Defaults to 'protected/views/layouts'.
the session component
the root directory of system view files. Defaults to 'protected/views/system'.
the theme used currently. Null if no theme is being used.
the theme manager.
the user session information
the root directory of view files. Defaults to 'protected/views'.
Returns the view renderer.
If this component is registered and enabled, the default
view rendering logic defined in CBaseController will
be replaced by this renderer.
Returns the widget factory.
Method Details
The post-filter for controller actions.
This method is invoked after the currently requested controller action and all its filters
are executed. You may override this method with logic that needs to be done
after all controller actions.
|
|
| $controller |
CController |
the controller |
| $action |
CAction |
the action |
| {return} |
boolean |
whether the action should be executed. |
The pre-filter for controller actions.
This method is invoked before the currently requested controller action and all its filters
are executed. You may override this method with logic that needs to be done
before all controller actions.
|
public string createAbsoluteUrl(string $route, array $params=array (
), string $schema='', string $ampersand='&')
|
| $route |
string |
the URL route. This should be in the format of 'ControllerID/ActionID'. |
| $params |
array |
additional GET parameters (name=>value). Both the name and value will be URL-encoded. |
| $schema |
string |
schema to use (e.g. http, https). If empty, the schema used for the current request will be used. |
| $ampersand |
string |
the token separating name-value pairs in the URL. |
| {return} |
string |
the constructed URL |
Creates an absolute URL based on the given controller and action information.
public array createController(string $route, CWebModule $owner=NULL)
|
| $route |
string |
the route of the request. |
| $owner |
CWebModule |
the module that the new controller will belong to. Defaults to null, meaning the application
instance is the owner. |
| {return} |
array |
the controller instance and the action ID. Null if the controller class does not exist or the route is invalid. |
Creates a controller instance based on a route.
The route should contain the controller ID and the action ID.
It may also contain additional GET variables. All these must be concatenated together with slashes.
This method will attempt to create a controller in the following order:
- If the first segment is found in controllerMap, the corresponding
controller configuration will be used to create the controller;
- If the first segment is found to be a module ID, the corresponding module
will be used to create the controller;
- Otherwise, it will search under the controllerPath to create
the corresponding controller. For example, if the route is "admin/user/create",
then the controller will be created using the class file "protected/controllers/admin/UserController.php".
|
public string createUrl(string $route, array $params=array (
), string $ampersand='&')
|
| $route |
string |
the URL route. This should be in the format of 'ControllerID/ActionID'. |
| $params |
array |
additional GET parameters (name=>value). Both the name and value will be URL-encoded. |
| $ampersand |
string |
the token separating name-value pairs in the URL. |
| {return} |
string |
the constructed URL |
Creates a relative URL based on the given controller and action information.
|
|
| $id |
string |
module ID |
| {return} |
CWebModule |
the module that has the specified ID. Null if no module is found. |
Searches for a module by its ID.
This method is used internally. Do not call this method.
|
public string getBaseUrl(boolean $absolute=false)
|
| $absolute |
boolean |
whether to return an absolute URL. Defaults to false, meaning returning a relative one.
This parameter has been available since 1.0.2. |
| {return} |
string |
the relative URL for the application |
Returns the relative URL for the application.
This is a shortcut method to CHttpRequest::getBaseUrl().
Returns the client script manager.
|
public string getControllerPath()
|
| {return} |
string |
the directory that contains the controller classes. Defaults to 'protected/controllers'. |
|
public string getHomeUrl()
|
| {return} |
string |
the homepage URL |
|
public string getLayoutPath()
|
| {return} |
string |
the root directory of layout files. Defaults to 'protected/views/layouts'. |
|
public string getSystemViewPath()
|
| {return} |
string |
the root directory of system view files. Defaults to 'protected/views/system'. |
|
|
| {return} |
CTheme |
the theme used currently. Null if no theme is being used. |
|
|
| {return} |
CWebUser |
the user session information |
|
public string getViewPath()
|
| {return} |
string |
the root directory of view files. Defaults to 'protected/views'. |
Returns the view renderer.
If this component is registered and enabled, the default
view rendering logic defined in CBaseController will
be replaced by this renderer.
Returns the widget factory.
Initializes the application.
This method overrides the parent implementation by preloading the 'request' component.
|
protected string parseActionParams(string $pathInfo)
|
| $pathInfo |
string |
path info |
| {return} |
string |
action ID |
Parses a path info into an action ID and GET variables.
|
public void processRequest()
|
Processes the current request.
It first resolves the request into controller and action,
and then creates the controller to perform the action.
|
protected void registerCoreComponents()
|
Registers the core application components.
This method overrides the parent implementation by registering additional core components.
|
public void runController(string $route)
|
| $route |
string |
the route of the current request. See createController for more details. |
Creates the controller and performs the specified action.
|
public void setControllerPath(string $value)
|
| $value |
string |
the directory that contains the controller classes. |
|
public void setHomeUrl(string $value)
|
| $value |
string |
the homepage URL |
|
public void setLayoutPath(string $path)
|
| $path |
string |
the root directory of layout files. |
|
public void setSystemViewPath(string $path)
|
| $path |
string |
the root directory of system view files. |
|
public void setTheme(string $value)
|
| $value |
string |
the theme name |
|
public void setViewPath(string $path)
|
| $path |
string |
the root directory of view files. |
Maybe both class name and file name must be appended with 'Controller'?