[Apc-aa-coders] Changes in AA CVS - 2005/08/31

[Honza M. <hon...@ec...>]

Current CVS state: 
   Should be stable, but not tested on our production server, yet. 
   I will do it during next week.

Last Changes:
08/31/05 - fix of no item message - works correctly if you fill 0 in it (zero)
(honzam) - default inputform view for the slice now could be set not only
           from default Profile setting page, but also
           from "Slice Admin" -> "Design - Item Manager" -> "Use special view",
           which is easier to find for users. Both options are equal (stores it
           to the profile)
         - added more description text to discussion view selectbox on
           "Design - Fulltext" page
08/30/05 - new function {compare:<number1>:<number2>} for comparing numbers
(honzam)   (aka dates): Returns:    'L' if number1 is less than number2,
                                    'G' if number1 is greater than number2,
                                    'E' if the numbers are equal.
           Usage example:
            {switch({compare:{last_edit.......}:1125481998})L:less:G:more:equal}
         - user_id for users authenticated from Reader slice is changed
           from login to more logical and more powerfull item_id
         - fixes in Reader Management permissions combination with SQL
           (perm_sql) permissions
         - some cleanup of the permissions core
08/29/05 - Readers from Reader Management slice could became AA users (now also
(honzam)   on SQL permissions perm_sql.php3 - for LDAP permissions it worked
           from 02/16/04)
           Database structure for SQL permissions is slightly modified in order
           we can store Reader Slice permissions as well. You can run
           sql_update.php3 script or you just change definition of two columns
           in the database:
               membership.memberid change from INT(11) to CHAR(32)
               perms.userid        change from INT(11) to CHAR(32)
08/26/05 - uploaded images can now be resized also exactly to specified
(brazda)   size (e.g. square). Image is resized and croped if needed from
           the center of original image. It can be set-up in parameters of
           "Insert" function for the field on "Slice Admin" -> "Fields" page.
08/26/05 - new possibility to create "Computed field". It is good solution for
(honzam)   all values, which could be precomputed, since its evaluation
           on item-show-time would be slow. Any of your field could be changed
           to "computed" - you just change "Insert" function for the field
           on "Slice Admin" -> "Fields" page. In such case the other setting
           of the field (like Default, Input type, ...) are irrelevant,
           of course. Two prepared field templates (computed_num....
           and computed_txt....) was added to sql_update.php3. Yes, you can use
           any {view...}, {include...}, {switch...} in the computed string
           (in Parameter)
         - fixed /misc/charset/convert.php3 script (which is able to convert any
           text from one encoding to another one) - now works when called
           externaly

-- 
Honza Malik <hon...@ec...>
Econnect