Today

• 7 hours ago

  issue 669 (Error during validation model data) commented on by perepelitsyn   -   sorry! this trouble appears in yii-1.1. i does not know about more older versions

  sorry! this trouble appears in yii-1.1. i does not know about more older versions
• 7 hours ago

  issue 669 (Error during validation model data) reported by perepelitsyn   -   What steps will reproduce the problem? 1. set any model variable as object 2. try to validate it 3. get error during validation 00200: /* 00201: * Checks if the given value is empty. 00202: * A value is considered empty if it is null, an empty array, or the trimmed result is an empty string. 00203: * Note that this method is different from PHP empty(). It will return false when the value is 0. 00204: * @param mixed the value to be checked 00205: * @param boolean whether to perform trimming before checking if the string is empty. Defaults to false. 00206: * @return boolean whether the value is empty 00207: * @since 1.0.9 00208: */ 00209: protected function isEmpty($value,$trim=false) 00210: { 00211: return $value===null || $value===array() || $value==='' || $trim && !is_array($value) && trim($value)===''; 00212: } 00213: } as you see method isEmpty works incorrect when value is object

  What steps will reproduce the problem? 1. set any model variable as object 2. try to validate it 3. get error during validation 00200: /* 00201: * Checks if the given value is empty. 00202: * A value is considered empty if it is null, an empty array, or the trimmed result is an empty string. 00203: * Note that this method is different from PHP empty(). It will return false when the value is 0. 00204: * @param mixed the value to be checked 00205: * @param boolean whether to perform trimming before checking if the string is empty. Defaults to false. 00206: * @return boolean whether the value is empty 00207: * @since 1.0.9 00208: */ 00209: protected function isEmpty($value,$trim=false) 00210: { 00211: return $value===null || $value===array() || $value==='' || $trim && !is_array($value) && trim($value)===''; 00212: } 00213: } as you see method isEmpty works incorrect when value is object

Yesterday

• 24 hours ago

  issue 667 (requirment checker should say 'warning' instead of 'failed' ...) changed by poppitypop   -   This issue was closed by revision r1512.

  Status: Fixed

  This issue was closed by revision r1512.

  Status: Fixed
• 24 hours ago

  r1512 (fixes issue 667) committed by poppitypop   -   fixes issue 667

  fixes issue 667
• 24 hours ago

  issue 605 (ModelCommand modification request) Labels changed by qiang.xue   -  

  Labels: Milestone-1.0.11 −Milestone-1.0.10

  Labels: Milestone-1.0.11 −Milestone-1.0.10
• 24 hours ago

  issue 667 (requirment checker should say 'warning' instead of 'failed' ...) commented on by qiang.xue   -   Note, I'm setting this for 1.1 release.

  Note, I'm setting this for 1.1 release.
• 24 hours ago

  issue 667 (requirment checker should say 'warning' instead of 'failed' ...) Labels changed by qiang.xue   -   I agree. Could you take care of this issue? Thanks.

  Labels: Milestone-1.1rc −Milestone-1.0.11

  I agree. Could you take care of this issue? Thanks.

  Labels: Milestone-1.1rc −Milestone-1.0.11
• 24 hours ago

  issue 661 (PDO muti-select error) Status changed by qiang.xue   -   Which SQL statement is causing the problem? What if you only execute one statement? What if you directly insert the parameters into the SQL statements rather than using parameter binding? Anyway, the error message says it is SQL syntax error. So I'm giving these debugging tips. This should not be related with Yii.

  Status: Invalid

  Which SQL statement is causing the problem? What if you only execute one statement? What if you directly insert the parameters into the SQL statements rather than using parameter binding? Anyway, the error message says it is SQL syntax error. So I'm giving these debugging tips. This should not be related with Yii.

  Status: Invalid
• 34 hours ago

  issue 668 (Suggested change for CForms with subforms) changed by qiang.xue   -  

  Status: Accepted

  Labels: Milestone-1.1rc −Milestone-1.0.11

  Status: Accepted

  Labels: Milestone-1.1rc −Milestone-1.0.11
• 36 hours ago

  issue 668 (Suggested change for CForms with subforms) reported by marlinf   -   When creating a CForm with subforms, the subforms are created as fieldsets, without any attributes. This makes targetting the block of information difficult with CSS or jQuery. I propose that the HTML attributes from the CForm element be transferred to the fieldset element, when created as a subform. Thus, if my subform has an id = 'company', the fieldset in the parent form will have that id, and can now be targetted. Patch attached.

  When creating a CForm with subforms, the subforms are created as fieldsets, without any attributes. This makes targetting the block of information difficult with CSS or jQuery. I propose that the HTML attributes from the CForm element be transferred to the fieldset element, when created as a subform. Thus, if my subform has an id = 'company', the fieldset in the parent form will have that id, and can now be targetted. Patch attached.
• 40 hours ago

  issue 667 (requirment checker should say 'warning' instead of 'failed' ...) reported by poppitypop   -   I think the requirement checker should say 'warning' instead of 'failed' for extensions that are not required but not installed either. It confuses me every time.. what do you guys think? right now, only the colors differ from the warnings and the failures.

  I think the requirement checker should say 'warning' instead of 'failed' for extensions that are not required but not installed either. It confuses me every time.. what do you guys think? right now, only the colors differ from the warnings and the failures.
• 47 hours ago

  issue 666 (Logging facility causing memory issues and lacks flexibility) reported by jerryab...@gmail.com   -   I've been debugging this issue all day and it turns out I'm running out of memory because the framework is storing all logs in memory. My issue is that I'm running a long process and trying to dump as much trace information as possible to watch the progress. About half way through my process it dies inexplicably with no log output. That's not good. I spent about an hour going through the logging subsystem and basically found that there is NO way to flush the logs that are already in memory, nor is there an EASY way to recreate the CLogger's for each route. My suggestion is that you write logs directly to disk without caching them in memory. I can understand why that might be useful for someone, but I've never in my life needed to query in memory logs of my session. It just seems like a complete waste of bits. So why not let me have the option of turning it on/off? If not, at least let me "flush()" the in memory logs to disk freeing up that space? As it stands now, I have to turn off TRACE level just to walk through my entire program. That's not cool. Qiang, on a related note here. Please start using "protected" in your classes instead of "private" for non-final classes. If you don't want extension, then make it private and mark the class final. Having "private" members makes it extremely difficult to extend functionality (i.e. CLogger) without modifying your awesome framework. Just my $0.02USD. Hugs baby! I

  I've been debugging this issue all day and it turns out I'm running out of memory because the framework is storing all logs in memory. My issue is that I'm running a long process and trying to dump as much trace information as possible to watch the progress. About half way through my process it dies inexplicably with no log output. That's not good. I spent about an hour going through the logging subsystem and basically found that there is NO way to flush the logs that are already in memory, nor is there an EASY way to recreate the CLogger's for each route. My suggestion is that you write logs directly to disk without caching them in memory. I can understand why that might be useful for someone, but I've never in my life needed to query in memory logs of my session. It just seems like a complete waste of bits. So why not let me have the option of turning it on/off? If not, at least let me "flush()" the in memory logs to disk freeing up that space? As it stands now, I have to turn off TRACE level just to walk through my entire program. That's not cool. Qiang, on a related note here. Please start using "protected" in your classes instead of "private" for non-final classes. If you don't want extension, then make it private and mark the class final. Having "private" members makes it extremely difficult to extend functionality (i.e. CLogger) without modifying your awesome framework. Just my $0.02USD. Hugs baby! I

Last 7 days

• Nov 05, 2009

  issue 649 (Scopes not working with deleteByPk) commented on by andy.damevin   -   I have the same problem but with deleteAll... In your example: User::model()->active()->deleteAll() Expected action is deleting all active users. But Yii delete all users, this is really not expected! Thank you for your help.

  I have the same problem but with deleteAll... In your example: User::model()->active()->deleteAll() Expected action is deleting all active users. But Yii delete all users, this is really not expected! Thank you for your help.
• Nov 05, 2009

  issue 605 (ModelCommand modification request) commented on by qiang.xue   -   Will take a look later. Thanks.

  Will take a look later. Thanks.
• Nov 05, 2009

  issue 605 (ModelCommand modification request) Status changed by qiang.xue   -  

  Status: Accepted

  Status: Accepted
• Nov 05, 2009

  issue 605 (ModelCommand modification request) commented on by mazan.robert   -   I've made some modifications that you can see in the attached patch. These modifications doesn't only involve the ModelCommand class, but the CDbSchema, CMssqlSchema, CMysqlSchema, COciSchema and CPgsqlSchema as well, because I've tried to generalize default schema handling a bit. With these modifications I could simply extend ModelCommand to handle a command line parameter that can contain a schema name we want to generate models from. Please, take a look at these modifications, and let me know if I should do something differently. Thanks in advance!

  I've made some modifications that you can see in the attached patch. These modifications doesn't only involve the ModelCommand class, but the CDbSchema, CMssqlSchema, CMysqlSchema, COciSchema and CPgsqlSchema as well, because I've tried to generalize default schema handling a bit. With these modifications I could simply extend ModelCommand to handle a command line parameter that can contain a schema name we want to generate models from. Please, take a look at these modifications, and let me know if I should do something differently. Thanks in advance!
• Nov 05, 2009

  issue 665 (CStarRating and tabular input) reported by francesc...@mac.com   -   What steps will reproduce the problem? 1. tabular input with CStarRating 2. 3. What is the expected output? What do you see instead? error on line 160 of CStarRating class What version of the product are you using? On what operating system? trunk Please provide any additional information below. if you do the resolveName before the line 160 it works: protected function renderStars($id,$name) { $inputCount=(int)(($this->maxRating-$this->minRating)/$this->ratingStepSize+1); $starSplit=(int)($inputCount/$this->starCount); $attr=$this->attribute; CHtml::resolveName($this->model,$attr); $selection=$this->hasModel() ? $this->model->{$attr} : $this->value; $options=$starSplit>1 ? array('class'=>"{split:{$starSplit}}") : array(); for($value=$this->minRating, $i=0;$i<$inputCount; ++$i, $value+=$this->ratingStepSize) { $options['id']=$id.'_'.$i; $options['value']=$value; if(isset($this->titles[$value])) $options['title']=$this->titles[$value]; else unset($options['title']); echo CHtml::radioButton($name,!strcmp($value,$selection),$options) . "\n"; } }

  What steps will reproduce the problem? 1. tabular input with CStarRating 2. 3. What is the expected output? What do you see instead? error on line 160 of CStarRating class What version of the product are you using? On what operating system? trunk Please provide any additional information below. if you do the resolveName before the line 160 it works: protected function renderStars($id,$name) { $inputCount=(int)(($this->maxRating-$this->minRating)/$this->ratingStepSize+1); $starSplit=(int)($inputCount/$this->starCount); $attr=$this->attribute; CHtml::resolveName($this->model,$attr); $selection=$this->hasModel() ? $this->model->{$attr} : $this->value; $options=$starSplit>1 ? array('class'=>"{split:{$starSplit}}") : array(); for($value=$this->minRating, $i=0;$i<$inputCount; ++$i, $value+=$this->ratingStepSize) { $options['id']=$id.'_'.$i; $options['value']=$value; if(isset($this->titles[$value])) $options['title']=$this->titles[$value]; else unset($options['title']); echo CHtml::radioButton($name,!strcmp($value,$selection),$options) . "\n"; } }
• Nov 04, 2009

  r1511 ([No log message]) committed by qiang.xue   -   [No log message]

  [No log message]
• Nov 04, 2009

  r1510 ([No log message]) committed by qiang.xue   -   [No log message]

  [No log message]
• Nov 04, 2009

  issue 664 (CFileCache::offsetExists() is slow) Status changed by qiang.xue   -   Yes, perhaps extending and customizing the default implementation is the better solution, if you are sure you don't need dependency feature. I will set this ticket as "wont fix". Please let me know if you could think of a better generic solution. Thanks.

  Status: WontFix

  Yes, perhaps extending and customizing the default implementation is the better solution, if you are sure you don't need dependency feature. I will set this ticket as "wont fix". Please let me know if you could think of a better generic solution. Thanks.

  Status: WontFix
• Nov 04, 2009

  issue 664 (CFileCache::offsetExists() is slow) commented on by eliovir   -   You're right. Unserializing is the problem. I'm looking for other implementation, for example setting special cache key to know if this data is cached, but it is not elegant. Or I can use this method into a derived CFileCache, knowing the problem, so without using dependencies for this special cache value, and maybe without serializing the value.

  You're right. Unserializing is the problem. I'm looking for other implementation, for example setting special cache key to know if this data is cached, but it is not elegant. Or I can use this method into a derived CFileCache, knowing the problem, so without using dependencies for this special cache value, and maybe without serializing the value.
• Nov 04, 2009

  issue 664 (CFileCache::offsetExists() is slow) commented on by qiang.xue   -   Could you please find out where the bottleneck is? Based on your description, it seems to me the bottleneck may be in unserializing the cached data. Unfortunately, your fix is incomplete because it doesn't consider the case when there is a cache dependency which evaluates to false. I couldn't think of a better way to fix this issue.

  Could you please find out where the bottleneck is? Based on your description, it seems to me the bottleneck may be in unserializing the cached data. Unfortunately, your fix is incomplete because it doesn't consider the case when there is a cache dependency which evaluates to false. I couldn't think of a better way to fix this issue.
• Nov 04, 2009

  issue 664 (CFileCache::offsetExists() is slow) Status changed by qiang.xue   -  

  Status: Accepted

  Status: Accepted
• Nov 04, 2009

  issue 664 (CFileCache::offsetExists() is slow) reported by eliovir   -   What steps will reproduce the problem? 1. create big cache data 2. save 3. test cache->offsetExists($id) What is the expected output? What do you see instead? I expect instant response. This function lasts 8s. What version of the product are you using? On what operating system? 1.0.10 on Linux. Please provide any additional information below. this is an override method, which corrects the issue. /** * Returns whether there is a cache entry with a specified key. * This method is required by the interface ArrayAccess. * @param string a key identifying the cached value * @return boolean */ public function offsetExists($id) { $key=$this->generateUniqueKey($id); $cacheFile=$this->getCacheFile($key); return file_exists($cacheFile) && filemtime($cacheFile) > time(); }

  What steps will reproduce the problem? 1. create big cache data 2. save 3. test cache->offsetExists($id) What is the expected output? What do you see instead? I expect instant response. This function lasts 8s. What version of the product are you using? On what operating system? 1.0.10 on Linux. Please provide any additional information below. this is an override method, which corrects the issue. /** * Returns whether there is a cache entry with a specified key. * This method is required by the interface ArrayAccess. * @param string a key identifying the cached value * @return boolean */ public function offsetExists($id) { $key=$this->generateUniqueKey($id); $cacheFile=$this->getCacheFile($key); return file_exists($cacheFile) && filemtime($cacheFile) > time(); }
• Nov 03, 2009

  issue 663 ([Enhancement] Use more modern encryption/hashing algorithms) changed by qiang.xue   -  

  Status: Accepted

  Labels: Milestone-1.1.0 −Milestone-1.0.11

  Status: Accepted

  Labels: Milestone-1.1.0 −Milestone-1.0.11
• Nov 03, 2009

  issue 663 ([Enhancement] Use more modern encryption/hashing algorithms) commented on by ekerazha   -   With PHP 5.1.2 you could also use hash_hmac() for hmac computation. It seems like PHP 5.1.2 got many security oriented enhancements.

  With PHP 5.1.2 you could also use hash_hmac() for hmac computation. It seems like PHP 5.1.2 got many security oriented enhancements.
• Nov 03, 2009

  issue 663 ([Enhancement] Use more modern encryption/hashing algorithms) reported by ekerazha   -   Current CSecurityManager implementation use 3DES for encryption and SHA1/MD5 for hashing. MD5 collisions have already been found. SHA1 and 3DES are still acceptable, but they have been replaced by newer algorithms. I think you should add support for more modern algorithms such as AES (MCRYPT_RIJNDAEL_128, MCRYPT_RIJNDAEL_192, MCRYPT_RIJNDAEL_256) for encryption and SHA256, SHA384, SHA512 and WHIRLPOOL for hashing... or just make them customizable. Notes: 1) MCRYPT_RIJNDAEL_ needs libmcrypt > 2.4.x 2) hash() needs PHP 5 >= 5.1.2 (maybe you could increase the PHP requirement from 5.1.0 to 5.1.2 for Yii 1.1).

  Current CSecurityManager implementation use 3DES for encryption and SHA1/MD5 for hashing. MD5 collisions have already been found. SHA1 and 3DES are still acceptable, but they have been replaced by newer algorithms. I think you should add support for more modern algorithms such as AES (MCRYPT_RIJNDAEL_128, MCRYPT_RIJNDAEL_192, MCRYPT_RIJNDAEL_256) for encryption and SHA256, SHA384, SHA512 and WHIRLPOOL for hashing... or just make them customizable. Notes: 1) MCRYPT_RIJNDAEL_ needs libmcrypt > 2.4.x 2) hash() needs PHP 5 >= 5.1.2 (maybe you could increase the PHP requirement from 5.1.0 to 5.1.2 for Yii 1.1).
• Nov 03, 2009

  issue 662 (i18n, dateFormatter on English word start from capital lett...) reported by vuliad   -   Yii::app()->dateFormatter->format('EEEE',$time) in en_us return Tuesday in ru return вторник and as i see month names and other done in the same way. This have to be done in ONE SAME way.

  Yii::app()->dateFormatter->format('EEEE',$time) in en_us return Tuesday in ru return вторник and as i see month names and other done in the same way. This have to be done in ONE SAME way.
• Nov 02, 2009

  issue 661 (PDO muti-select error) reported by ukyo.pu   -   What steps will reproduce the problem? 1.I need select muti-times in one controller with PDO 2.I createCommand muti-times and bindParams 3.Then throw exception :Syntax error or access violation: 1064 You have an error in your SQL syntax; What is the expected output? What do you see instead? I hope it'll not throw exception,Can you help me? What version of the product are you using? On what operating system? Yii 1.1a Please provide any additional information below. $connection = Yii::app()->db; $query_m_list = "SELECT * from ciel_product where serial <> '' and dis_yes = 'Y' and create_date > :check_date order by create_date desc LIMIT :startRow_m_list,:maxRows_m_list"; $command=$connection->createCommand($query_m_list); $command->bindParam (":check_date",$check_date,PDO::PARAM_STR); $command->bindParam (":startRow_m_list",$startRow_m_list,PDO::PARAM_INT); $command->bindParam (":maxRows_m_list",$maxRows_m_list,PDO::PARAM_INT); $m_list=$command->queryAll(); $page_data['m_list']=$m_list; $query_m_list = "SELECT * from ciel_product_fd where serial <> '' and dis_yes = 'Y' and create_date > :check_date order by create_date desc LIMIT :startRow_m_list,:maxRows_m_list"; $command=$connection->createCommand($query_m_list); $command->bindParam (":check_date",$check_date,PDO::PARAM_STR); $command->bindParam (":startRow_m_list",$startRow_m_list,PDO::PARAM_INT); $command->bindParam (":maxRows_m_list",$maxRows_m_list,PDO::PARAM_INT); $fd_list=$command->queryAll(); $page_data['fd_list']=$fd_list;

  What steps will reproduce the problem? 1.I need select muti-times in one controller with PDO 2.I createCommand muti-times and bindParams 3.Then throw exception :Syntax error or access violation: 1064 You have an error in your SQL syntax; What is the expected output? What do you see instead? I hope it'll not throw exception,Can you help me? What version of the product are you using? On what operating system? Yii 1.1a Please provide any additional information below. $connection = Yii::app()->db; $query_m_list = "SELECT * from ciel_product where serial <> '' and dis_yes = 'Y' and create_date > :check_date order by create_date desc LIMIT :startRow_m_list,:maxRows_m_list"; $command=$connection->createCommand($query_m_list); $command->bindParam (":check_date",$check_date,PDO::PARAM_STR); $command->bindParam (":startRow_m_list",$startRow_m_list,PDO::PARAM_INT); $command->bindParam (":maxRows_m_list",$maxRows_m_list,PDO::PARAM_INT); $m_list=$command->queryAll(); $page_data['m_list']=$m_list; $query_m_list = "SELECT * from ciel_product_fd where serial <> '' and dis_yes = 'Y' and create_date > :check_date order by create_date desc LIMIT :startRow_m_list,:maxRows_m_list"; $command=$connection->createCommand($query_m_list); $command->bindParam (":check_date",$check_date,PDO::PARAM_STR); $command->bindParam (":startRow_m_list",$startRow_m_list,PDO::PARAM_INT); $command->bindParam (":maxRows_m_list",$maxRows_m_list,PDO::PARAM_INT); $fd_list=$command->queryAll(); $page_data['fd_list']=$fd_list;
• Nov 02, 2009

  issue 629 ([ENHANCEMENT] Allow user to configure additional command pat...) Labels changed by qiang.xue   -  

  Labels: Milestone-1.1rc −Milestone-1.0.11

  Labels: Milestone-1.1rc −Milestone-1.0.11
• Nov 02, 2009

  issue 660 (meta-tags) changed by qiang.xue   -   This issue was closed by revision r1509.

  Status: Fixed

  This issue was closed by revision r1509.

  Status: Fixed
• Nov 02, 2009

  r1509 ((Fixes issue 660)) committed by qiang.xue   -   (Fixes issue 660 )

  (Fixes issue 660 )
• Nov 02, 2009

  issue 660 (meta-tags) Status changed by qiang.xue   -   I see. Will fix it. Thanks.

  Status: Started

  I see. Will fix it. Thanks.

  Status: Started
• Nov 02, 2009

  issue 660 (meta-tags) commented on by jurica.romic   -   Yii::app()->clientScript->registerMetaTag("xyz", 'description', null, array("lang" => "de")); Yii::app()->clientScript->registerMetaTag( $sLanguage, "Content-language"); $this->setPageTitle( $pageTitle. $pageWord ); Output <meta lang="de" name="description" content="xyz" /><meta name="Content-language" content="de" /><title>xyz TITLE</title>

  Yii::app()->clientScript->registerMetaTag("xyz", 'description', null, array("lang" => "de")); Yii::app()->clientScript->registerMetaTag( $sLanguage, "Content-language"); $this->setPageTitle( $pageTitle. $pageWord ); Output <meta lang="de" name="description" content="xyz" /><meta name="Content-language" content="de" /><title>xyz TITLE</title>
• Nov 02, 2009

  issue 660 (meta-tags) commented on by jurica.romic   -   Yii::app()->clientScript->registerMetaTag("xyz", 'description', null, array("lang" => "de")); Yii::app()->clientScript->registerMetaTag( $sLanguage, "Content-language"); $this->setPageTitle( $pageTitle. $pageWord ); Output <meta lang="de" name="description" content="xyz" /><meta name="Content-language" content="de" /><title>xyz TITLE</title>

  Yii::app()->clientScript->registerMetaTag("xyz", 'description', null, array("lang" => "de")); Yii::app()->clientScript->registerMetaTag( $sLanguage, "Content-language"); $this->setPageTitle( $pageTitle. $pageWord ); Output <meta lang="de" name="description" content="xyz" /><meta name="Content-language" content="de" /><title>xyz TITLE</title>
• Nov 02, 2009

  r1508 (merge from 1.0) committed by qiang.xue   -   merge from 1.0

  merge from 1.0
• Nov 02, 2009

  r1507 (fixed bugs introduced by r1480) committed by qiang.xue   -   fixed bugs introduced by r1480

  fixed bugs introduced by r1480
• Nov 01, 2009

  issue 660 (meta-tags) Status changed by qiang.xue   -   You need to leave an empty line between PHP tags.

  Status: Invalid

  You need to leave an empty line between PHP tags.

  Status: Invalid
• Nov 01, 2009

  issue 660 (meta-tags) reported by jurica.romic   -   What steps will reproduce the problem? 1. Meta-Tags not divided through Newlines What is the expected output? What do you see instead? Different Meta Tags are all in one Line Please put a New-Line between every Meta Tag What version of the product are you using? On what operating system? 1.0.10 Please provide any additional information below.

  What steps will reproduce the problem? 1. Meta-Tags not divided through Newlines What is the expected output? What do you see instead? Different Meta Tags are all in one Line Please put a New-Line between every Meta Tag What version of the product are you using? On what operating system? 1.0.10 Please provide any additional information below.
• Nov 01, 2009

  yii-docs-1.1b.r1504.zip (Yii 1.1 beta documentation) file uploaded by qiang.xue   -  

  Labels: Type-Docs OpSys-All Not-Stable

  Labels: Type-Docs OpSys-All Not-Stable
• Nov 01, 2009

  yii-docs-1.1b.r1504.tar.gz (Yii 1.1 beta documentation) file uploaded by qiang.xue   -  

  Labels: Type-Docs OpSys-All Not-Stable

  Labels: Type-Docs OpSys-All Not-Stable
• Nov 01, 2009

  yii-1.1b.r1504.zip (Yii 1.1 beta source code) file uploaded by qiang.xue   -  

  Labels: Featured Type-Source OpSys-All Not-Stable

  Labels: Featured Type-Source OpSys-All Not-Stable
• Nov 01, 2009

  yii-1.1b.r1504.tar.gz (Yii 1.1 beta source code) file uploaded by qiang.xue   -  

  Labels: Featured Type-Source OpSys-All Not-Stable

  Labels: Featured Type-Source OpSys-All Not-Stable
• Nov 01, 2009

  r1506 ([No log message]) committed by qiang.xue   -   [No log message]

  [No log message]
• Nov 01, 2009

  issue 400 (Enhance web log route) Status changed by qiang.xue   -  

  Status: WontFix

  Status: WontFix
• Nov 01, 2009

  issue 382 (Layout resolution should be better designed) Labels changed by qiang.xue   -  

  Labels: Milestone-1.1rc −Milestone-1.1b

  Labels: Milestone-1.1rc −Milestone-1.1b
• Nov 01, 2009

  r1505 (prepare for next release.) committed by qiang.xue   -   prepare for next release.

  prepare for next release.
• Nov 01, 2009

  r1504 (1.1 beta release.) committed by qiang.xue   -   1.1 beta release.

  1.1 beta release.
• Nov 01, 2009

  r1503 (prepare for 1.1b release.) committed by qiang.xue   -   prepare for 1.1b release.

  prepare for 1.1b release.
• Nov 01, 2009

  r1502 (merge yiidoc.) committed by qiang.xue   -   merge yiidoc.

  merge yiidoc.