Wiki Follow @yiiframework

Delploying anything using joomla's framework is quite difficult. The framework don't provide a good MVC structure and the documentation is very poor.

Authentication and Authorization is a good tutorial. Among other topics, it describes basic aspects of Yii's RBAC implementation. But however hard I read the tutorial, I couldn't understand how exactly the hierarchy works. I found how to define authorization hierarchy, how business rules are evaluated, how to configure authManager, but almost nothing about how I should build my hierarchy, in what sequence its nodes are checked, when the checking process stops and what would be the checking result.

This had me stumped for a while so I figured it would be nice to share here to avoid others the grief.

Checkboxes have two possible values, true and false, but some applications require that the user select one particular value before proceeding. Examples might be:

PHPIDS is a well known project that can be found in php-ids.org.

PHPIDS é conhecido projeto que pode ser visto em php-ids.org.

My favourite editor is Komodo Edit (free and crossplatform) and I use it for my everyday coding work. Just recently I found out how to make it help me to work with Yii. :) So follow these steps:

In Yii, we can define an action class and ask the controller to instantiate it. And we always create ourselves actions class in rootPath/protected/extensions, and the view file we called in the actions class always are located in rootPath/protected/views/ControllerNAME or rootPath/themes/ThemeNAME/ControllerNAME, then when we use the same actions class in different controllers, we have to copy it from one controller to the other controller, so we also need the "same" view file work for us, here is an example.

Normally when we want users to download a file, that file is put in a folder under the web application root and the web server does the rest.

hai teman yii... apa kabar.. kembali lagi bersama catatan saya..