Several features which are critical for practical work

  1. Existing RFCs are defining email address letters as ANSI. There are highly experimental informational IETF letters but no RFC for it. If you need to validate international emails just checking for @ it’s easy to achieve using http://www.yiiframework.com/doc/api/1.1/CEmailValidator/#pattern-detail.

  2. Phone validation is tricky: all countries have different formats. Additionally some countries have multiple formats. Moreover, for some countries there is no standard. We’ve tried to validate US phones and the only result was confused users.

  3. Can you point to these places?

  4. For Yii 1.x we’ll not change it. Yii 2 will have spaces in this case.

  5. It’s not needed for all cases. Can be done easily with property overloading.

  6. There was extension doing it. Can’t remember the name.

  7. Gii? Or you mean API for doing it?

40, 41. Something similar is planned for Yii2.

  1. there are many such places

some contain several lines

other contain whole functions

I have not time to make a detailed research now

  1. yes, API
  1. regex pattern in CFileHelper::findFiles params options
  1. script for bootstrap installation of web-based products

it will be the same for ALL possible products

a) download zip file from product server

B) unpack it locally into temp folder

c) check whether it is possible to run PHP file after unpacking

if yes exit to custom installation url inside unpacked application

d) if not, check whether it is possible to access ftp:// by file functions,

if not fail completely

e) if yes, ask from user ftp login,pwd,url for the current server, and…

attention(!)…

upload files from this server into the same server by ftp

after that uploaded php files will be allowed for execution

f) exit to custom installation url inside unpacked and uploaded application

note, that all this is just common bootstrap functionality

real custom installation wizard starts after completion of bootstrap

  1. Please elaborate.

  2. Was mentioned before, I guess.

  1. it is difficult for me to elaborate something

I just need to write some things for myself during development, and those of them which may be considered as useful for many, are described in this topic

it is task for yii dev team to elaborate this :)

  1. earlier I mentioned installation wizard (it will be different for many people) or installation wizard builder (it may be considered as a standalone tool like Gii)

bootstrap will be the same for all by 99%

Kamil, I can’t even guess what “regex pattern in CFileHelper::findFiles params options” means.

  1. I mean this

pattern option

$files = CFileHelper::findFiles ("docs", array ("pattern" => "\\\\someFile([0-9]+)\.([a-z]+)"));

Aha, got it.

  1. CActiveForm should have validateOnBlur setting and clearing of error on focus

now even if user fixed an error client side validation does not run again and error is still seen

  1. $htmlOptions member of CActiveForm does not work

it is just not used anywhere where I supposed it should be used by the comments inside class

  1. if YII_DEBUG is on assets should be cleared on every request and republished on every request to the application
  1. in js code for CActiveForm getting container is done by

closest(‘div’)

search this code to see

it is definitely BUG

it should be parent(‘div’)

  1. one more BUG

moreover

in docs for CActiveForm you should write that each label+field should be wrapped by div to correctly reflect changes of css classes (on error for example)

when default CActiveForm is placed on JUI tabs widget it becomes buggy

  1. One more BUG

CModel::behaviors() return empty array

always!

  1. moreover this method should implemented ion CComponent in according with the whole architecture

but not in CModel

  1. Naming of members as

_e

_m

inside CComponent class does not add readability to the system

  1. don’t forget to remove empty behaviors() method from CController too

I guess that it probably was planned that implementation of this method should be done by programmer

but it is wrong - because attaching and detaching is done automatically by framework

so return of the list of behaviors should be done too

Is just my opinion but here the problem is that it’s very difficult to talk about one problem… when you are just posting more and more of them… some are not even problems or bugs…

Like the last one behaviors() - 48, 49 and 51 - why not write a separate post about this where someone can answer you… but please do not open 3 new threads for the same thing… like you posted here 3 new "bugs" for the same thing…

The behaviors() method is used to "set" what behaviors you want to apply to the model/controller… check again the documentation is clear enough… and check the init() method of that classes where you will see that the result of the method behaviors() is used as a parameter to attachBehaviors()… so this is just a helper method…