Explore topic-wise InterviewSolutions in .

ZEND Framework requires PHP 5.2.4 and up. Some Zend Framework components may WORK with earlier versions of PHP, but these components are TESTED and supported only on 5.2.4 and up.

Zend Framework requires PHP 5.2.4 and up. Some Zend Framework components may work with earlier versions of PHP, but these components are tested and supported only on 5.2.4 and up.

Yes, you can CALL a MODEL in view. Simple CREATE the object and call the METHOD.

Yes, you can call a model in view. Simple create the object and call the method.

Example1:

Now in your index.phtml you can have this statement to CALL other VIEW
$this->action(‘action name’,’controller name’,’MODULE name’,ARRAY(‘parameter name’=>’parameter value’));

Example1:

Now in your index.phtml you can have this statement to call other view
$this->action(‘action name’,’controller name’,’module name’,array(‘parameter name’=>’parameter value’));

The model component can VARY dramatically in RESPONSIBILITIES and data store from ONE MVC APPLICATION to the next.

The model component can vary dramatically in responsibilities and data store from one MVC application to the next.

Uses of Zend_Controller
Gives the request & response methods by using its sub-classes.
$request = new Zend_Controller_Request_Http()
$response = new Zend_Controller_Response_Http()

Uses of Zend_Date
Date related processing can be done using this component.

Uses of Zend_File_Transfer
it provides extensive support for file uploads and downloads.

Uses of Zend_Db
It is used to doing database related purpose in our appication.

Uses of Zend_Paginator
Doing the pagination in our application.

Uses of Zend_Auth
It is used to authenticate a user.

Zend_Session_Namespace
This is a simple proxy CLASS to use API into the Zend_Session MANAGED $_SESSION Superglobal.

Uses of Zend_Controller
Gives the request & response methods by using its sub-classes.
$request = new Zend_Controller_Request_Http()
$response = new Zend_Controller_Response_Http()

Uses of Zend_Date
Date related processing can be done using this component.

Uses of Zend_File_Transfer
it provides extensive support for file uploads and downloads.

Uses of Zend_Db
It is used to doing database related purpose in our appication.

Uses of Zend_Paginator
Doing the pagination in our application.

Uses of Zend_Auth
It is used to authenticate a user.

Zend_Session_Namespace
This is a simple proxy class to use API into the Zend_Session managed $_SESSION Superglobal.

The Zend_Filter component provides a set of COMMONLY needed data filters. It ALSO provides a simple filter chaining mechanism by which multiple filters may be applied to a single datum in a user-defined order.

Example:

Other Filters:
Alnum – Zend_Filter_Alnum is a filter which returns only alphabetic characters and digits. All other characters are supressed.
Alpha – Zend_Filter_Alpha is a filter which returns the string $value, removing all but alphabetic characters. This filter includes an option to also allow WHITE space characters.

The Zend_Filter component provides a set of commonly needed data filters. It also provides a simple filter chaining mechanism by which multiple filters may be applied to a single datum in a user-defined order.

Example:

Other Filters:
Alnum – Zend_Filter_Alnum is a filter which returns only alphabetic characters and digits. All other characters are supressed.
Alpha – Zend_Filter_Alpha is a filter which returns the string $value, removing all but alphabetic characters. This filter includes an option to also allow white space characters.

At the TIME of calling AJAX to FETCH we NEED to disable LAYOUT.
$this->_helper->layout()->disableLayout();
$this->_helper->viewRenderer->setNoRender(TRUE);

At the time of calling AJAX to fetch we need to disable layout.
$this->_helper->layout()->disableLayout();
$this->_helper->viewRenderer->setNoRender(true);

The basic DIFFERENCE between these objects is the ‘scope’ in which they are valid:
a) Zend_Registry : request scope
b) Zend_Session : session scope

Zend_Registry is used to store objects/values for the current request. In SHORT, anything that you commit to Registry in index.php can be accessed from other controllers/actions (because EVERY request is FIRST ROUTED to the index.php bootstrapper via the .htaccess file). Config parameters and db parameters are generally prepared for global use using the Zend_Registry object.

Zend_Session ACTUALLY uses PHP sessions. Data stored using Zend_Session can be accessed in different/all pages. So, if you want to create a variable named ‘UserRole’ in the /auth/login script and want it to be accessible in /auth/redirect, you would use Zend_Session.

The basic difference between these objects is the ‘scope’ in which they are valid:
a) Zend_Registry : request scope
b) Zend_Session : session scope

Zend_Registry is used to store objects/values for the current request. In short, anything that you commit to Registry in index.php can be accessed from other controllers/actions (because EVERY request is first routed to the index.php bootstrapper via the .htaccess file). Config parameters and db parameters are generally prepared for global use using the Zend_Registry object.

Zend_Session actually uses PHP sessions. Data stored using Zend_Session can be accessed in different/all pages. So, if you want to create a variable named ‘UserRole’ in the /auth/login script and want it to be accessible in /auth/redirect, you would use Zend_Session.

$this->_db->LASTINSERTID();
$this->_db->fetchAll($SQL);
$this->_db->fetchRow($sql);

$this->_db->lastInsertId();
$this->_db->fetchAll($sql);
$this->_db->fetchRow($sql);

No. Zend Framework was built to use all of the sophisticated object ORIENTED FEATURES of PHP 5 and take ADVANTAGE of SIGNIFICANT performance and security enhancements.

No. Zend Framework was built to use all of the sophisticated object oriented features of PHP 5 and take advantage of significant performance and security enhancements.

$REQUEST = $this->GETREQUEST();
$_GET = $request->getParams();
$_POST = $request->getPost();

$request = $this->getRequest();
$_GET = $request->getParams();
$_POST = $request->getPost();

CONFIGURATION can be DONE in APPLICATION.ini file in Zend framework. This file in the path application/ configs/application.ini.

Configuration can be done in application.ini file in Zend framework. This file in the path application/ configs/application.ini.

a) $request->setModuleName(‘FRONT’);
b) $request->setControllerName(‘address’);
C) $request->setActionName(‘addresslist’);

a) $request->setModuleName(‘front’);
b) $request->setControllerName(‘address’);
c) $request->setActionName(‘addresslist’);

BASED on the zend authentication it ALLOWS the user to ACCESS CERTAIN actions.

Based on the zend authentication it allows the user to access certain actions.

It is USED to authenticate user, for EXAMPLE LIKE ADMIN, general etc.

It is used to authenticate user, for example like admin, general etc.

ZF is both. Zend Framework provides all the components required for most web applications in a single distribution. But Zend Framework components are also loosely coupled, MAKING it easy to use just a few components in a web APPLICATION- even alongside other frameworks! Using this use-at-will architecture, we are implementing features COMMONLY found in more monolithic frameworks. In fact, we are currently WORKING on a tooling component for the 1.8 release that will make it simpler to build applications using ZF components, yet will not sacrifice the use-at-will nature of existing ZF components. It’s a testament to the use-at-will architecture of Zend Framework that the tooling component itself can be used STANDALONE.

ZF is both. Zend Framework provides all the components required for most web applications in a single distribution. But Zend Framework components are also loosely coupled, making it easy to use just a few components in a web application- even alongside other frameworks! Using this use-at-will architecture, we are implementing features commonly found in more monolithic frameworks. In fact, we are currently working on a tooling component for the 1.8 release that will make it simpler to build applications using ZF components, yet will not sacrifice the use-at-will nature of existing ZF components. It’s a testament to the use-at-will architecture of Zend Framework that the tooling component itself can be used standalone.

Apart from index if we want to do any EXTRA CONFIGURATION REGARDING DATABASE and other things that is DONE within bootstrap.

Apart from index if we want to do any extra configuration regarding database and other things that is done within bootstrap.

Routing and dispatching is managed in the front CONTROLLER. It COLLECTS all the REQUEST from the server and handles it.

Routing and dispatching is managed in the front controller. It collects all the request from the server and handles it.

AUTOLOADER is FUNCTION that LOAD all the OBJECT on START up.

Autoloader is function that load all the object on start up.