Yii 1.1.2

Obviously, this year's release schedule for the framework is much quieter. But now each release brings much more bug fixes and new features added.

In the new, just released, version 1.1.2, we have about 20 bug fixes and 30 improvements or innovations.

Consider the most remarkable:

• Added the ability to manage relationships in ActiveRecord models on the fly.
  Three methods have been added for this:
  • CActiveRecordMetaData :: addRelation ($ name, $ config) to add a relationship, where $ name is the name of a relationship, $ config is an array with relationship parameters, as is used when overloading the CActiveRecord :: relations () method
  • CActiveRecordMetaData :: hasRelation ($ name) to check for the existence of a relationship with the specified name
  • CActiveRecordMetaData :: removeRelation ($ name) to remove a relation.
  All three methods are essentially a wrapper for managing the open (public) property of CActiveRecordMetaData :: relations , which stores all relationships. These methods and properties from an instance of an AR class are accessed using the CActiveRecord :: getMetaData () method.
  ')
  
• The CActiveRecord :: resetScope () method has been added . It allows you to reset all the named condition groups (scopes) used in the chain, including the default condition group.
  
  
• Added CModel :: getValidatorList () method for flexible control of model validators on the fly.
  
  
• A third parameter has been added to the CBaseController :: widget () method, which allows you not to display the results of the widget immediately on the screen, but to return, for example, to save to a variable. Similarly, as does CController :: render () and other render methods.
  
  
• CCaptchaAction now supports an unlimited number of input attempts by setting the testLimit property to zero.
  
  
• A fourth parameter has been added to CAssetManager :: publish () , which includes forced copying of resource files and directories from the source to the published directory, even if they were published before. This option should be used mainly only during development, when source files of resources are constantly being corrected.
  
  
• Created another class for caching. You can now use WinCache using the CWinCache class. Naturally, for this, the corresponding extension must be included in PHP.
  
  
• Now you can combine regular PHP-native templates and special templates customizable through additional classes (for example, CPradoViewRenderer )
  
  
• CTypeValidator now supports checking not only single variables, but also the contents of arrays.
  
  
• Added CFileHelper :: getExtension method for determining file extension.
  
  
• Improvements in CDbCriteria :
  • Fixed a bug that previously made it impossible to combine two conditions with parameters.
    
    
  • Also in CDbCriteria :: select, field names can now be framed with quotes for complex queries.
    
    
  • The CDbCriteria :: addBetweenCondition () method has been added , which allows you to conveniently add column-type BETWEEN a AND b constructions to the sql query.
• Added Ukrainian translation of messages.
  
  
• The function CHttpSession :: get () was created , which returns the value of the session variable by its name. This function is very similar to CHttpSession :: itemAt () , except that it can return a default value if the session variable with the specified name is not defined.
  
  

Gii module

Separately, it is necessary to note the new module called Gii , which is included in the distribution.

What used to be done with the yiic utility can now be easily done right in the browser. This module provides the ability to generate code not from the command line, but in the browser, which of course is much more convenient.

Gii initially included several generators (and their number can be expanded), each of which is responsible for generating the code of its type. For example, the controller generator generates the controller class code together with several view files, and the model generator creates the ActiveRecord class for a specific table in the database.

Typical actions when using the generator:

1. Enter the generator page.
2. Fill out the form with parameters for generation. For example, when using the module generator, to create a new module, you need to enter the name (identifier) ​​of the module.
3. Click the “Preview” button to see which files will be created and click on any of them to view their contents.
4. Click the Generate button to create the files directly.
5. Optionally, view the log file with a description of all actions performed during the generation of a new code.

Since the module creates new files with php-code, it should be used only on the developer's server.

For more information, as well as instructions for connecting the module, see the documentation .