Quick links: Content - sections - sub sections
EN

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
en:changelog:1.0beta3 [2007/10/03 09:13] – laurenten:changelog:1.0beta3 [2007/10/19 11:16] – laurent
Line 115: Line 115:
 ==== Bug fixes ==== ==== Bug fixes ====
  
-    * jDb, driver pdo: the driver pdo returned a table instead of an object during the use of the resultSet as a iterator (because of a bug in PDO). (ticket #180)+    * jDb, driver pdo: the PDO driver returned a table instead of an object during the use of the resultSet as a iterator (because of a bug in PDO). (ticket #180)
     * jDao:     * jDao:
-       * an attribute “been worth” vacuum was not authorized (ticket #191)+       * an empty "value" attribute was not authorized (ticket #191)
        * bad formatting for the method.limit.forbidden error        * bad formatting for the method.limit.forbidden error
-       * removal of a “note” in jDaoRecordBase:: setPk () +       * removal of a notice in jDaoRecordBase:: setPk () 
-       * bad generation of the conditions on the level of operators IN/NOT IN (bug #203). +       * bad generation of the conditions with the use of operators IN/NOT IN (bug #203). 
-       * the names of the tables and the fields between quotes in the request are now generated, in order to be able to correctly use these names in Postgresql and mysql. (bug #98)+       * the names of the tables and the fields in the queries are now generated between quotes, in order to be able to correctly use these names in Postgresql and mysql. (bug #98)
        * for the optional properties, the methods did not check if the corresponding dynamic values were null, and if thus a IS NULL had to be generated or not during their use in clauses WHERE. (ticket #228)        * for the optional properties, the methods did not check if the corresponding dynamic values were null, and if thus a IS NULL had to be generated or not during their use in clauses WHERE. (ticket #228)
-       * correction of bugs on the properties of the type autoincrement+       * fixed bugs on the "autoincrement" properties
     * jTpl:     * jTpl:
-       * (regression) the use of the key words true, false and null was not possible any more bus php sees them like constants +       * (regression) the use of the keywords "true", "false" and "null" was not possible any more because php sees them like constants 
-       * certain operators were usable in the tags of posting. They are not it any more.+       * some operators were usable in some template tags. It is not usable any more.
        * the same compiled file of template was used during the use of the template in answers of the different type (bug #225)        * the same compiled file of template was used during the use of the template in answers of the different type (bug #225)
-       * it was possible to include tags PHP in a template, which is a potential hole of safety for the templates which are not “confidences” (uploadé by one to use by ex). +       * it was possible to include PHP tags in a template, which is a potential security hole for the templates which are not trusted (uploaded by a user for example). 
-       * It was not possible to put in comment tags jtpl (bug #106) +       * It was not possible to put jtpl tags in comment  (bug #106) 
-    * answers: +    * jResponses: 
-       * headings HTTP were not well managed in certain answers: one could not modify them (ticket #198).+       * HTTP headers were not well managed in some response objects : we could not modify them (ticket #198).
        * jResponseBinary: the property mimeType was not declared (ticket #188)        * jResponseBinary: the property mimeType was not declared (ticket #188)
-       * jResponseXmlRpc and jXmlRpc: bug during the analysis of the data of the type struct (ticket #190 et#192) and to the level of the name of the method (ticket #245 and #243). +       * jResponseXmlRpc and jXmlRpc: bug during the analysis of the data of the type struct (ticket #190 et#192) and of the name of the method (ticket #245 and #243). 
-       * rss and atom: the code language was badly generated (ticket #247)+       * rss and atom: the language code was badly generated (ticket #247)
     * jUrl, engine of significant URL: in the file xml, parameter of the type dates, the days “10” and “20” were not recognized (ticket #204)     * jUrl, engine of significant URL: in the file xml, parameter of the type dates, the days “10” and “20” were not recognized (ticket #204)
     * jAuth: bad operator in jauth.listener.php (bug #221).     * jAuth: bad operator in jauth.listener.php (bug #221).
-    * jControllerCmdLine: the signature of the method param () was not identical to that of its class mother+    * jControllerCmdLine: the signature of the method param () was not identical to that of its mother class
     * Problem of encoding with class JSON included in Jelix: update of this class (bug #321)     * Problem of encoding with class JSON included in Jelix: update of this class (bug #321)
     * Problem of encoding at the time of the sending of the emails     * Problem of encoding at the time of the sending of the emails
  
  
-===== Other versions ===== 
  
  
 +----
 +  * [[en:changelog:1.0beta3.1|Next version: 1.0beta3.1]]
 +  * [[en:changelog|Last improvements]]
  

en/changelog/1.0beta3.txt · Last modified: 2007/10/19 12:15 by 127.0.0.1

Recent changes RSS feed Creative Commons License