Explore topic-wise InterviewSolutions in .

render() is commonly USED to render a view that corresponds to what a USER sees as a "page" in your application. It first renders the view you have specified and then renders the layout for the current controller action (if applicable), placing the result of the first render into the layout. It then performs output PROCESSING (which at this time means automatically inserting any necessary <script> tags and updating DYNAMIC content) and finally outputs the result.

renderPartial() is commonly used to render a "piece" of a page/HTML. The main difference from render() is that this method does not place the results of the render in a layout.

render() is commonly used to render a view that corresponds to what a user sees as a "page" in your application. It first renders the view you have specified and then renders the layout for the current controller action (if applicable), placing the result of the first render into the layout. It then performs output processing (which at this time means automatically inserting any necessary <script> tags and updating dynamic content) and finally outputs the result.

renderPartial() is commonly used to render a "piece" of a page/HTML. The main difference from render() is that this method does not place the results of the render in a layout.

Steps to remove index.php from your APPLICATION url.

Step 1: First configure your Yii-application CONFIGURATION file like below code

.....
'urlManager'=>array(
'urlFormat'=>'path', //mandatory
'showScriptName'=>false, //mandatory
'urlSuffix'=>'.html', //not mandatory
......
),
....

Step 2: Enable apache rewrite ENGINE. To enable rewrite engine type the following command in your TERMINAL (Ubuntu ).

a2enmod rewrite // to enable rewrite engine
#Restart apache2 after
/etc/init.d/apache2 restart
OR
service apache2 restart

Step 3: Then, if you'd like, you can use the following .htaccess file in your application folder where index.php exists

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Thats all the 3 steps to remove index.php from the URL.

Steps to remove index.php from your application url.

Step 1: First configure your Yii-application configuration file like below code

.....
'urlManager'=>array(
'urlFormat'=>'path', //mandatory
'showScriptName'=>false, //mandatory
'urlSuffix'=>'.html', //not mandatory
......
),
....

Step 2: Enable apache rewrite engine. To enable rewrite engine type the following command in your terminal (Ubuntu ).

a2enmod rewrite // to enable rewrite engine
#Restart apache2 after
/etc/init.d/apache2 restart
OR
service apache2 restart

Step 3: Then, if you'd like, you can use the following .htaccess file in your application folder where index.php exists

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Thats all the 3 steps to remove index.php from the URL.

Gii is a module that provides Web-based code GENERATION capabilities. To work with gii, you need to change the main CONFIGURATION file of your application like FOLLOWING.

return array(
......
'modules'=>array(
'gii'=>array(
'class'=>'system.gii.GiiModule',
'password'=>[*CHOOSE a password*]
),
),
)

To access gii in your local system, hit the url on your BROWSER localhost/your-app/index.php?r=gii. You need to type the password that you have set in the main configuration of your app. to proceed further.

Gii is a module that provides Web-based code generation capabilities. To work with gii, you need to change the main configuration file of your application like following.

return array(
......
'modules'=>array(
'gii'=>array(
'class'=>'system.gii.GiiModule',
'password'=>[*choose a password*]
),
),
)

To access gii in your local system, hit the url on your browser localhost/your-app/index.php?r=gii. You need to type the password that you have set in the main configuration of your app. to proceed further.

To create a MODULE access gii URL and there you can create a module. after creating a module from gii you need to add it the MAI configuration FILE of your yii application.

localhost/your-app/index.php?r=gii // utl to access gii

 ....
'modules' => array(
'module-name',
'other-module',
'user' => array(
'activeAfterRegister' => FALSE,
),
.....

To create a module access gii url and there you can create a module. after creating a module from gii you need to add it the mai configuration file of your yii application.

localhost/your-app/index.php?r=gii // utl to access gii

 ....
'modules' => array(
'module-name',
'other-module',
'user' => array(
'activeAfterRegister' => false,
),
.....

In DEFAULT application of yii, open the main.php file exists in protected/config/main.php and search for a parameter named as db, there you can add host-name, database name , username and PASSWORD of your database server.

In default application of yii, open the main.php file exists in protected/config/main.php and search for a parameter named as db, there you can add host-name, database name , username and password of your database server.

To install YII you NEED to

1. Download the Yii code from its official website or github.
2. Extract the code into your server root directory.
3. Open command line terminal and TYPE the FOLLOWING command.
   php path-to-yii-folder/framework/yiic webapp [webapp-name]
4. After execution of above command , it will ask you for the confirmation of creating your application , on selecting yes , this will create a defaut application.

To install Yii you need to

By adding the JAVASCRIPT files in webroot and call them in default VIEWS if NEEDED EVERYWHERE or just in the RELATED views.

By adding the javascript files in webroot and call them in default views if needed everywhere or just in the related views.

FIND, findAll , findByPk , find By ,QUERY

find, findAll , findByPk , find By ,query

can be done on SUBMISSION in CONTROLLER, or USING javascript/ajax while user is still FILLING the data. Second option is BETTER.

can be done on submission in controller, or using javascript/ajax while user is still filling the data. Second option is better.

by calling AJAX helper and then USING it in CONTROLLER for rendering.

by calling ajax helper and then using it in controller for rendering.

index

index

take the framework either from Yii site or if you have changed according to your needs start from there. Proceed with basic software engg. concepts as requirement gathering etc..

This is a basic Understanding Concept in yii

1. Yii-based apps are driven by data logic. When I build an app, I always start by making sure that my database schemes are well-designed and optimised to FIT the BUSINESS flow of the app. Therefore, my codes are automatically generated based on my database design. And, yes…
2.  … Yii can generate the whole shebang of PHP codes for you automatically! Just define which database you want to use, and with a few clicks it will create a CRUD (create-read-update-delete) app for you. It looks so cute, I tell you! Speaking of automatic…
3. … Yii can generate a skeleton app for you automatically. This skeleton app include a view page, a LOGIN page, contact page and basic navigation, all wrapped within a completely organized folder tree based on the standard MVC programming model.
4. The extensive choice of Yii functions makes sense. As a self-taught web programmer, I was able to map out its functions to all of the RESPONSE and REQUEST tasks I most often use when building webapps within a matter of minutes. It also doesn’t hurt that the Yii community has kindly provided cheat sheets for the functions so that I can do a quick reference when I need to.
5. The Definitive Guide to Yii document that comes with the Yii install is actually quite easy to go through, at least for me. I don’t know why, though. I thought CakePHP docs were more user-friendly and attractive, but surprisingly I was able to go through Yii documentation and tutorial in just two hours and not get cross-eyed by the end of it.
6. Yii uses MySQL and SQLite as its choice database types. Of course, you can run any other type of databases as long as you have its PDO enabled in your php.ini file. I develop USING MySQL most of the time, but my fondness for SQLite is increasing, due to the fact that SQLite is so darn lightweight and easy to use.
7. Yii is integrated with jQuery, which means that many of the necessary validation functions I use can easily be plugged within the Yii function calls itself, which is usually only a line of code or two.
8. Yii is open-source, and it’s free. Open-source products turn me on.

take the framework either from Yii site or if you have changed according to your needs start from there. Proceed with basic software engg. concepts as requirement gathering etc..

This is a basic Understanding Concept in yii

A component is an INDEPENDENT piece of code WRITTEN for specific TASK that can be used by calling in controllers (example : email component), helper is used for HELPING yii in rendering the data to be shown to user with views, these only adds to MODULARITY in code otherwise same coding can be implemented in controllers.

A component is an independent piece of code written for specific task that can be used by calling in controllers (example : email component), helper is used for helping yii in rendering the data to be shown to user with views, these only adds to modularity in code otherwise same coding can be implemented in controllers.

You can DEFINE table prefix when using Gii. In your case you need to set it to tbl_. Then it should generate UserController INSTEAD of TblUserController.

The Yii Framework employs a class naming convention whereby the names of the classes directly map to the directories in which they are stored. The root level directory of the Yii Framework is the “framework/” directory, under which all classes are stored hierarchically.

Class names may only contain ALPHANUMERIC CHARACTERS. Numbers are permitted in class names but are DISCOURAGED. Dot (.) is only permitted in place of the path separator.

You can define table prefix when using Gii. In your case you need to set it to tbl_. Then it should generate UserController instead of TblUserController.

The Yii Framework employs a class naming convention whereby the names of the classes directly map to the directories in which they are stored. The root level directory of the Yii Framework is the “framework/” directory, under which all classes are stored hierarchically.

Class names may only contain alphanumeric characters. Numbers are permitted in class names but are discouraged. Dot (.) is only permitted in place of the path separator.

Models represent the underlying data structure of a Web application. Models are often shared among different sub-applications of a Web application. For example, a LoginForm model MAY be used by both the front end and the back end of an application; a News model may be used by the console commands, Web APIs, and the front/back end of an application. Therefore, models

• should contain properties to represent specific data;
• should contain BUSINESS logic (e.g. validation rules) to ensure the represented data fulfills the design requirement;
• may contain code for manipulating data. For example, a SearchForm model, besides representing the search input data, may contain a search METHOD to implement the actual search.

Views are responsible for presenting models in the format that end users desire. In general, views

• should mainly contain presentational code, such as HTML, and simple PHP code to traverse, format and render data;
• should avoid containing code that performs explicit DB queries. Such code is better placed in models.
• should avoid direct access to $_GET, $_POST, or other similar variables that represent the end user request. This is the CONTROLLER's job. The view should be focused on the display and layout of the data provided to it by the controller and/or model, but not attempting to access request variables or the database directly.
• may access properties and methods of controllers and models directly. However, this should be done only for the purpose of presentation.

Controllers are the glue that binds models, views and other components together into a RUNNABLE application. Controllers are responsible for dealing directly with end user requests. Therefore, controllers

• may access $_GET, $_POST and other PHP variables that represent user requests;
• may create model instances and manage their life cycles. For example, in a typical model update action, the controller may first create the model instance; then populate the model with the user input from$_POST; after saving the model successfully, the controller may redirect the user browser to the model detail page. Note that the actual implementation of saving a model should be located in the model instead of the controller.
• should avoid containing embedded SQL statements, which are better kept in models.
• should avoid containing any HTML or any other presentational markup. This is better kept in views.

Models represent the underlying data structure of a Web application. Models are often shared among different sub-applications of a Web application. For example, a LoginForm model may be used by both the front end and the back end of an application; a News model may be used by the console commands, Web APIs, and the front/back end of an application. Therefore, models

Views are responsible for presenting models in the format that end users desire. In general, views

Controllers are the glue that binds models, views and other components together into a runnable application. Controllers are responsible for dealing directly with end user requests. Therefore, controllers

index.php

index.php

BACKEND/
common/
COMPONENTS/
config/
params.php
params-local.php *
LIB/
Pear/
yii/
Zend/
migrations/
models/
Comment.php
Extension.php
...
console/
COMMANDS/
SitemapCommand.php
...
config/
main.php
main-local.php *
params.php
params-local.php *
runtime/
yiic.php *
frontend/
components/
config/
main.php
main-local.php *
params.php
params-local.php *
controllers/
SiteController.php
...
lib/
models/
ContactForm.php
SearchForm.php
runtime/
views/
layouts/
SITE/
www/
assets/
css/
js/
index.php *
yiic
yiic.bat

backend/
common/
components/
config/
params.php
params-local.php *
lib/
Pear/
yii/
Zend/
migrations/
models/
Comment.php
Extension.php
...
console/
commands/
SitemapCommand.php
...
config/
main.php
main-local.php *
params.php
params-local.php *
runtime/
yiic.php *
frontend/
components/
config/
main.php
main-local.php *
params.php
params-local.php *
controllers/
SiteController.php
...
lib/
models/
ContactForm.php
SearchForm.php
runtime/
views/
layouts/
site/
www/
assets/
css/
js/
index.php *
yiic
yiic.bat

Yii is so much faster because it is using the lazy loading technique extensively. For example, it does not include a class file until the class is USED for the first time; and it does not create an object until the object is accessed for the first time. Other FRAMEWORKS suffer from the performance hit because they would enable a functionality (e.g. DB CONNECTION, user SESSION) no MATTER it is used or not during a request.

Yii is so much faster because it is using the lazy loading technique extensively. For example, it does not include a class file until the class is used for the first time; and it does not create an object until the object is accessed for the first time. Other frameworks suffer from the performance hit because they would enable a functionality (e.g. DB connection, user session) no matter it is used or not during a request.

YII is a high-performance component-based PHP FRAMEWORK best for Web 2.0 development.

Yii is a high-performance component-based PHP framework best for Web 2.0 development.