Questions et reponses d'entretien

The basic difference between these objects is the �scope� in which they are valid:

a) Zend_Registry : request scope
b) Zend_Session : session scope

a) 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 prepped for global use using the Zend_Registry object.

b) 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.

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

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

Example1:
Public function indexAction() {
If(condition)
$this->render(�yourview.phtml�);
Else
Index.phtml;

Example2:
Public function indexAction() {
}
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�));

From within a view file: $this->headLink()->appendStylesheet(�filename.css�);
From within a controller: $this->view->headLink()->appendStylesheet(�filename.css�);
And then somewhere in your layout you need to echo out your headLink object:
headLink();?>

You have to quote the strings,
$this->getAdapter ()->quote ( );
$select->where ( � = �, );
OR (If you are using the question mark after equal to sign)
$select->where ( � = ? �, );

=> Declare custom routing rules
Not limited to �controller/action/param� format
=> Optional Controller Plugins, Action Helpers, and View Helpers
ErrorHandler plugin handles exceptions, 404 errors, etc.
FlashMessenger, Redirector, ViewRenderer helpers
Output common HTML elements in views
=> Extensible interfaces
Write your own plugins and helpers

The file element needs a special file decorator, which is added by default. When you set your own decorators for file elements, you delete the default decorators.
For example:
$element->setDecorators(array(
array('ViewHelper'),
array('Errors')
));
You should use a File decorator instead of the ViewHelper for the file element, like so:
$element->setDecorators(array(
array('File'),
array('Errors')
));

You're probably looking for decorators. All forms and form elements in Zend_Form use decorators to render their output.

The CLA protects all users including individuals, small and medium businesses, and large corporations. By having a CLA in place, we mitigate the risk that companies who claim intellectual property infringement may demand royalties or fees from users of Zend Framework, whether individuals or companies. This is especially important for companies basing their business or products on Zend Framework. The Zend Framework CLA helps to ensure that code and other IP in Zend Framework remains free.

If you are contributing code as an individual- and not as part of your job at a company- you should sign the individual CLA. If you are contributing code as part of your responsibilities as an employee at a company, you should submit a corporate CLA with the names of all co-workers that you foresee contributing to the project.